Skip to main content

​
MCP Server

The Agent Wallet MCP server is the primary integration point for AI agents. It exposes wallet capabilities as tools that any MCP-compatible client can discover and use — Claude Desktop, Cursor, Windsurf, n8n, or your own custom agent. The server is remote and hosted at https://mcp.fd.xyz. There’s nothing to install, no local processes to run, and no infrastructure to manage.

​
What is MCP?

MCP (Model Context Protocol) is an open standard by Anthropic for connecting AI assistants to external tools and data sources. Think of it as a universal adapter — any MCP-compatible client can connect to any MCP server and discover what it can do. Agent Wallet publishes wallet operations as MCP tools. When your AI agent connects, it automatically discovers all available capabilities and can use them through natural language.

​
Connection Details

PropertyValue
Server URLhttps://mcp.fd.xyz
TransportStreamable HTTP
AuthenticationOAuth Authorization Code Flow with PKCE
No API keys or bearer tokens to manage. When your MCP client connects for the first time, it triggers an OAuth flow that opens a browser for you to authenticate with your District Pass.

​
Setup

Add the Agent Wallet MCP server to your client’s configuration:
Edit your config file:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "finance-district": {
      "type": "streamable-http",
      "url": "https://mcp.fd.xyz"
    }
  }
}
Restart Claude Desktop. A browser window will open for authentication on first connect.
For more clients, see MCP Compatible Clients.

​
Verify the Connection

After configuring your client, verify the agent can reach the wallet:
“What Finance District tools do you have?”
The agent should list the available wallet capabilities. Then try:
“What’s my wallet balance?”
If you see your balance (even if it’s zero), the connection is working.

​
Capabilities

The MCP server exposes wallet operations as tools that your agent discovers automatically. Rather than documenting specific tool names (which may evolve), here’s what your agent can do once connected:

​
Query Operations

  • Check balances — view holdings across all tokens and chains
  • Get wallet info — wallet addresses, supported chains, configuration
  • View transaction history — recent transactions with details
  • Check swap quotes — preview exchange rates before committing

​
Transaction Operations

  • Transfer tokens — send to any address on any supported chain
  • Swap tokens — exchange between token pairs with best-rate routing
  • Commerce payments — pay Prism-enabled merchants via x402
  • Yield operations — explore and deploy funds to yield opportunities
Your agent discovers these capabilities automatically through MCP’s standard tool discovery. You don’t need to configure which operations are available — the full set is exposed when you connect.
The agent discovers all available tools dynamically. As new capabilities are added to the MCP server, your agent gets access to them automatically — no config changes needed.

​
Authentication

Authentication uses OAuth Authorization Code Flow with PKCE — the same standard used by major web applications:
  1. Your MCP client connects to https://mcp.fd.xyz
  2. The server responds with an OAuth authorization URL
  3. Your client opens a browser window
  4. You log in with your District Pass (email + confirmation code)
  5. The OAuth flow completes and your client receives a token
  6. Subsequent requests use this token automatically
Token refresh is handled automatically by the OAuth flow. You shouldn’t need to re-authenticate unless you explicitly revoke access. Revoking access — if you want to disconnect a specific MCP client, you can revoke its OAuth token through the Signer Service web interface. Client registration — popular MCP clients (Claude Desktop, Cursor, Windsurf, Claude Code, n8n) are pre-registered and work out of the box. If you’re building a custom MCP client, see Client Registration for supported registration methods.

​
Error Handling

Common scenarios your agent may encounter:
ErrorMeaningResolution
Authentication failedOAuth token expired or revokedRe-authenticate through browser flow
Insufficient balanceWallet doesn’t have enough tokens for the operationFund the wallet with more tokens
Transaction failedOn-chain error (gas, nonce, network issue)Retry — transient errors resolve on retry
Unsupported chain/tokenRequested operation on an unsupported chain or tokenCheck Supported Networks
MCP clients typically display tool errors in the conversation. The agent can often explain what went wrong and suggest a fix.