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
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.
How it works
- Add vims-mcp to your desktop MCP client, or open chat.vims.com for agents in the browser
- Call tools/list to see what is available
- 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.
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.
{
"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.
mcp