MCP server

An MCP server implements the Model Context Protocol — an open standard introduced by Anthropic — to expose a typed set of tools and resources that any MCP-compatible AI agent (Claude, Cursor, Windsurf, Zed, custom agents) can discover and invoke. The agent calls the server over stdio or HTTP/SSE; the server runs the tool and returns a structured result.

Why MCP matters

• One protocol, many agents. A single MCP server works with every compatible client — no per-vendor integration.
• Typed tools. Each tool has a JSON schema for inputs and outputs, so the agent picks the right one and supplies valid arguments.
• Local trust. stdio-mode servers run in the agent’s process boundary, so credentials and key material never leave the user’s machine.
• Composable. Multiple servers can run side-by-side, each contributing tools to the same agent.

How Solobank uses MCP

Solobank ships @solobank/mcp — a stdio MCP server that exposes the agent wallet as 14 typed tools (solobank_balance, solobank_send, solobank_pay, solobank_swap, solobank_lend, and so on). Drop it into your Claude or Cursor config and the agent can read balances, pay MPP-protected endpoints, and earn yield without any glue code.

{
  "mcpServers": {
    "solobank": {
      "command": "npx",
      "args": ["-y", "@solobank/mcp"]
    }
  }
}