Model Context Protocol

MCP for AI agents: on the desktop and in the browser

vims-mcp exposes your local VIMS to Claude Code, Cursor, Codex, Devin, Antigravity, Kilo, Gemini CLI, Cline, and VS Code; in the browser, chat.vims.com offers its tools and your connectors to in-browser agents through WebMCP.

Inside VIMS Desktop · macOS · Windows · Linux · ChromeOS · Free

Claude Code Cursor Codex Devin Antigravity Kilo Gemini CLI Cline VS Code vims-mcptools/list · tools/callagentsbrowserflowskeysdatabaseknowledge

What it does

VIMS speaks MCP in both directions. As a client, it connects external servers (GitHub, Postgres, Playwright, Blender, …) for its own agents — on the desktop and on chat.vims.com’s Connectors page. As a server, vims-mcp gives any MCP client live control of the local platform, and a chat.vims.com tab offers its tools and every connector you added to agents in the browser through WebMCP.

01
vims-mcp (local, stdio)Proxies tool calls to the local daemon: status, settings, agents, A2A, flows, skills, database, knowledge, bookkeeper, channels, social, Nostr keys, component keys, HITL, browser CDP.
02
Browser MCP (WebMCP)chat.vims.com registers its tools with navigator.modelContext: spaces, knowledge base, flows, nodes, shop, flights, and every connector on its Connectors page. Changes wait for your approval; tokens stay in the tab.
03
Identity workflowsvims_nostr_generate_key, import, set_default, sign, set_handle, resolve_nip05 — with signing gated by the keys.vims.com vault.
04
MCP-of-MCPList, add, and call other MCP servers through VIMS itself.
05
Docs and SDK serversvims-docs and vims-sdk expose the documentation catalog and installed apps to agents.
06
Per-agent manifestsMarketplace agents publish /.well-known/mcp/manifest.json for discovery.

How it works

  1. Add vims-mcp to your desktop MCP client, or open chat.vims.com for agents in the browser
  2. Call tools/list to see what is available
  3. Call tools under VIMS permissions and approvals

Two MCP surfaces

Use the one that matches where the work lives. Neither hands a hosted service your private keys.

◆
vims-mcpLocal stdio MCP server. Proxies approved tool calls to the VIMS daemon on your machine: agents, browser, flows, databases, knowledge, Nostr identity, settings.
◆
Browser MCP (WebMCP)The browser MCP runs in your VIMS tabs: chat.vims.com registers its tools with WebMCP (navigator.modelContext) — spaces, knowledge base, flows, nodes, shop, flights, and every connector added on its Connectors page, run by the tab with that connector’s own token. Reads run when asked; anything that changes something waits for the person’s approval. No keys leave the browser.
◆
keys.vims.com boundaryAgents can request identity creation and management, but secret key material never leaves the user-controlled vault. Signing stays permissioned.

Connect your client

vims-mcp ships inside VIMS Desktop. Point any MCP client at it (stdio) for the local daemon. In the browser there is nothing to configure: open chat.vims.com in a browser with WebMCP.

◆
Claude Codeclaude mcp add vims -- vims-mcp — or paste the config into .mcp.json in your project.
◆
Codexcodex mcp add vims -- vims-mcp — or add it under [mcp_servers] in ~/.codex/config.toml.
◆
Gemini CLIgemini mcp add vims vims-mcp — or add it to mcpServers in ~/.gemini/settings.json.
◆
VS Codecode --add-mcp with the JSON below, or drop it in .vscode/mcp.json.
◆
CursorSettings → MCP → New Server, or add the JSON below to ~/.cursor/mcp.json.
◆
DevinAdd vims-mcp under MCP servers in your Devin settings, or the mcp.json for your repo.
◆
AntigravityAgent Manager → MCP Servers → add the JSON below.
◆
ClineMCP Servers panel → Configure MCP Servers → paste the JSON below.
◆
KiloSettings → MCP Servers → paste the JSON below.
{
  "mcpServers": {
    "vims": {
      "command": "vims-mcp",
      "env": { "VIMS_URL": "http://127.0.0.1:8089" }
    }
  }
}

FAQ

How do I connect Claude Code?

Point it at the vims-mcp binary (stdio) with VIMS_URL set to your local daemon.

Can a browser agent create identity keys?

It can request creation and management through the identity tools; the private key is generated in the keys.vims.com vault and signing stays user-authorized.

Does anything hold my keys?

No. Connector tokens stay in your vault and the browser tab; identity keys stay in keys.vims.com and signing stays user-authorized.

How does VIMS MCP connect to the rest of VIMS?

It shares your identity from keys.vims.com and is reachable by agents through MCP and Flow, so it works alongside every other VIMS app.

Related

MCP for AI agents: on the desktop and in the browser

VIMS speaks MCP in both directions. As a client, it connects external servers (GitHub, Postgres, Playwright, Blender, …) for its own agents — on the desktop and on chat.vims.com’s Connectors page. As a server, vims-mcp gives any MCP client live control of the local platform, and a chat.vims.com tab offers its tools and every connector you added to agents in the browser through WebMCP.