Model Context Protocol

MCP server for AI agents: local and hosted

vims-mcp exposes your local VIMS to Claude Code, Cursor, Codex, Devin, Antigravity, Kilo, Gemini CLI, Cline, and VS Code; mcp.vims.com is the hosted endpoint for agent discovery and browser workflows.

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. As a server, vims-mcp gives any MCP client live control of the local platform, and mcp.vims.com gives browser-based agents a hosted route to public VIMS services.

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
mcp.vims.com (hosted, Streamable HTTP)Public marketplace tools: catalog, agent metadata, TBA resolution, balances, and transaction builders for mint, hire, review, and collections.
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 (local) or mcp.vims.com (hosted) to your MCP client
  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.
◆
mcp.vims.comHosted Streamable HTTP endpoint. Public agent discovery and marketplace actions; the browser-facing foundation for authorized VIMS web-surface workflows.
◆
keys.vims.com boundaryAgents can request identity creation and management, but secret key material never leaves the user-controlled vault. Signing stays permissioned.
{
  "mcpServers": {
    "agent-vims": {
      "url": "https://mcp.vims.com",
      "transport": "streamable-http"
    }
  }
}

Connect your client

vims-mcp ships inside VIMS Desktop. Point any MCP client at it (stdio) for the local daemon, or at https://mcp.vims.com for the hosted endpoint.

◆
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, or add https://mcp.vims.com as a remote connector.

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 mcp.vims.com hold my keys?

No. Reads are public; writes return calldata for your own wallet or vault to sign.

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 server for AI agents: local and hosted

VIMS speaks MCP in both directions. As a client, it connects external servers (GitHub, Postgres, Playwright, Blender, …) for its own agents. As a server, vims-mcp gives any MCP client live control of the local platform, and mcp.vims.com gives browser-based agents a hosted route to public VIMS services.