AgentCash can run as a Model Context Protocol (MCP) server, giving your AI client direct tool access to all AgentCash capabilities: paid API calls, endpoint discovery, wallet management, and authenticated requests. MCP mode is one of three ways to use AgentCash, alongside the CLI and the agent skill.Documentation Index
Fetch the complete documentation index at: https://agentcash.dev/docs/llms.txt
Use this file to discover all available pages before exploring further.
When to use MCP mode
MCP mode is ideal when your AI client supports MCP and you want:- Tool-based access: the agent calls AgentCash tools directly
- Structured responses: tool responses come back as structured data the agent can parse
- Automatic integration: the tools are available in the agent’s context with no extra setup
Quick install
The guided installer detects your client:- Claude Code
- Cursor
- Claude Cowork
- Claude Desktop
- Other clients
Available tools
When running in MCP mode, AgentCash exposes these tools to your agent:| Tool | What it does |
|---|---|
fetch | HTTP request with automatic SIWX auth and payment |
fetch_with_auth | Deprecated alias for fetch |
get_balance | Total wallet balance across supported networks |
list_accounts | Per-network balances, addresses, and deposit links |
search | Find API providers by natural-language query |
check_endpoint_schema | Probe pricing and schema without paying |
discover_api_endpoints | Find all endpoints on an origin |
redeem_invite | Redeem an invite code for free USDC |
Verify installation
Start a session with your AI client and ask:What is my AgentCash balance?The agent should call the
get_balance tool and return your total balance. If you later need deposit links or network-specific addresses, the agent should call list_accounts.
Server options
You can pass flags to the MCP server process:| Flag | Description |
|---|---|
--verbose / -v | Enable debug output on stderr |
--quiet / -q | Suppress all stderr output |
--dev | Use development endpoints (localhost) |