# Unbound MCP

Canonical production origin: https://unbound-me.com. This response is served by the production environment. Check /public/runtime for registration and demo-payment availability. Check deployment status before running examples; documentation is not an uptime guarantee.

Unbound MCP is a local stdio server for MCP-capable AI clients. It is not a remote HTTP MCP URL or OAuth integration. Requires Node.js 20+.

1. Download [unbound-mcp.mjs](https://unbound-me.com/mcp/unbound-mcp.mjs). Get its SHA-256 from [client metadata](https://unbound-me.com/public/mcp) and verify the bytes before running.
2. Configure the AI client with the absolute local path:

```json
{
  "mcpServers": {
    "unbound": {
      "command": "node",
      "args": [
        "/ABSOLUTE/PATH/unbound-mcp.mjs",
        "--server",
        "https://unbound-me.com"
      ]
    }
  }
}
```

3. Connect/restart the client's MCP integration. The local client starts a login request and opens the browser. If necessary call unbound_login_start.
4. The human signs in, reviews scopes and approves in the browser. Copy its five-character code into unbound_login_complete. Never ask for a password in agent chat. The code alone cannot authorize a different pairing client.
5. Call unbound_account_summary to inspect the account. Read scope is separate from keys:write and optional billing:write. Revoke access in Dashboard → Unbound MCP. Grants expire after seven days.

Supported actions include listing usage, creating/changing/deleting customer API keys, and optionally creating crypto deposit invoices. The MCP client does not receive company wallet withdrawal or root-administrator access. A deposit invoice does not pay itself. Account access is scoped; do not claim login succeeded until confirmed.