What is Tychi Agent Finance MCP?

A Model Context Protocol server over stdio that plugs agent hosts into Tychi Agent Finance via @tychilabs/agent-finance. Built for agents that need to hold, pay, and act on-chain — not humans clicking a wallet UI.

Use it when your agent host (Cursor, Claude Desktop, OpenClaw, custom MCP client) needs self-custody wallets, policy on every spend, and local signing — not a human-facing wallet UI.

What is agent self-custody in Tychi?

Self-custody on MCP means the agent's identity seed and EVM private key live on the agent's device — local encrypted vault (~/.tyi unless TYI_DATA_DIR is set). This MCP server is a thin stdio bridge; custody and signing logic live in @tychilabs/agent-finance. Tychi orchestrates sessions and policy but never holds the private key. The LLM provider never receives it. Use tyi_resume_tx and tyi_resume_x402 to sign locally before anything moves on-chain or over x402.

What is the built-in x402 payment gateway for agents?

x402 is the built-in agentic payment gateway — autonomous HTTP payments for APIs and agent services, gated by your agent's policy. Tychi prepares the payment; the agent signs via tyi_resume_x402 after tyi_run returns pending: "x402". Same self-custody model as on-chain transactions — no handing spend keys to the API vendor. SDK detail: typescript/docs/x402.md.

What is ERC-8004 agent identity?

ERC-8004 is agentic on-chain identity — register the agent on-chain (profile, capabilities, trust signals) alongside its wallet. This MCP exposes it through tyi_onboard (wallet + session + policy + bind) and agent tasks via tyi_run. SDK detail: typescript/docs/erc8004.md.

| Built-in capability | MCP surface | | --- | --- | | Self-custody | tyi_onboard → local vault; tyi_resume_tx / tyi_resume_x402 sign locally | | x402 payment gateway | tyi_run → tyi_resume_x402 | | ERC-8004 identity | tyi_onboard + tyi_run (onboarding integration) |

Table of contents

• What is Tychi Agent Finance MCP?
• What is agent self-custody in Tychi?
• What is the built-in x402 payment gateway for agents?
• What is ERC-8004 agent identity?
• Who is this for?
• How is this different from a regular crypto wallet?
• Names and packages
• What it is not
• Related packages
• How do I install it?
• Quick flow
• How do I connect it in Cursor?
• How do I connect it in Claude Desktop?
• Environment variables
• Tools
• Trust boundary
• FAQ
• Agent procedure doc
• Development
• Security
• License

Who is this for?

Agent builders running autonomous workflows in Cursor, Claude Desktop, OpenClaw, Hermes, or any MCP host — when the agent needs its own money, not your personal wallet.

Operators who want policy on every agent spend — caps, allowed actions, read-only mode — while keys stay in agent custody.

Teams building agent-native products on Tychi who need a standard MCP plug-in instead of wiring the SDK by hand.

How is this different from a regular crypto wallet?

| | Human wallet (MetaMask, etc.) | Platform custody | Tychi Agent Finance MCP | | ------------- | ----------------------------- | ---------------------- | --------------------------------------------- | | Built for | People clicking approve | Apps holding user keys | Autonomous AI agents | | Custody | User | Platform | Agent self-custody (~/.tyi) | | Spend control | Manual approve each tx | App permissions | Policy on every spend | | Interface | Browser extension / app | Dashboard | MCP (Cursor, Claude, OpenClaw, Hermes, …) | | Signing | User clicks | Platform signs | Local sign for tx + x402 | | Identity | Wallet address | Account | Agent identity + ERC-8004 path via Tychi |

Names and packages

| Name | What it is | | ---------------------------------- | ------------------------------------------------------------------------------------- | | Tychi | Product — financial home for AI agents (ai.tychilabs.com) | | TYI | Backend API your MCP server calls (e.g. https://agents.tychilabs.com) | | @tychilabs/agent-finance-mcp | This npm package — MCP server | | agent-finance-mcp | CLI binary after install | | tychi-agent-finance | MCP server id in Cursor / Claude config | | @tychilabs/agent-finance | TypeScript SDK this MCP wraps |

What it is not

• Not a standalone wallet or RPC toolkit.
• Not Tychi itself running locally — it calls the TYI API you configure.
• Not a place to store secrets in repo files — passwords and LLM keys live in MCP host env, vault data on the agent's device in ~/.tyi.

Related packages

| Package | Role | | ------------------------------------------------------------------------------------ | ------------------------------------------- | | @tychilabs/agent-finance | TypeScript SDK — custody, sessions, signing | | @tychilabs/agent-finance-mcp (this package) | MCP stdio bridge for agent hosts | | agent-finance repo | Umbrella monorepo for both packages |

How do I install it?

npm install -g @tychilabs/agent-finance-mcp

Requirements:

• Node.js >= 20
• A Tychi agent API URL (default: https://agents.tychilabs.com)
• MCP host that supports stdio servers (Cursor, Claude Desktop, etc.)

After install, the binary is:

agent-finance-mcp

Quick flow

tyi_discover     → chains, LLM providers, money tools (no auth)
tyi_onboard      → wallet + auth + session + policy + bind (once per process)
tyi_run          → send a message to your agent
tyi_resume_tx    → if run returned pending on-chain tx
tyi_resume_x402  → if run returned pending x402 payment

flowchart LR
  A[tyi_discover] --> B[tyi_onboard]
  B --> C[tyi_run]
  C --> D{pending?}
  D -->|tx| E[tyi_resume_tx]
  D -->|x402| F[tyi_resume_x402]
  D -->|none| G[done]
  E --> C
  F --> C

Always call tyi_discover first, then tyi_onboard before any tyi_run. Tool responses include next_tool hints when the server expects a follow-up call.

Configure in Cursor

Add to .cursor/mcp.json (or project MCP settings):

{
  "mcpServers": {
    "tychi-agent-finance": {
      "command": "npx",
      "args": ["-y", "@tychilabs/agent-finance-mcp"],
      "env": {
        "TYI_API_BASE_URL": "https://agents.tychilabs.com",
        "TYI_VAULT_PASSWORD": "your-local-vault-password",
        "TYI_SESSION_PASSWORD": "your-session-password",
        "TYI_LLM_API_KEY": "sk-...",
        "TYI_LLM_PROVIDER": "openai",
        "TYI_CHAIN_ID": "10143"
      }
    }
  }
}

For local development from this monorepo, see .mcp.json.

Configure in Claude Desktop

{
  "mcpServers": {
    "tychi-agent-finance": {
      "command": "agent-finance-mcp",
      "env": {
        "TYI_API_BASE_URL": "https://agents.tychilabs.com",
        "TYI_VAULT_PASSWORD": "your-local-vault-password",
        "TYI_SESSION_PASSWORD": "your-session-password",
        "TYI_LLM_API_KEY": "sk-...",
        "TYI_LLM_PROVIDER": "openai",
        "TYI_CHAIN_ID": "10143"
      }
    }
  }
}

Environment variables

Set these in the MCP host env (not inside tool arguments for secrets).

| Variable | Required | Description | | ---------------------- | -------- | --------------------------------------------------------------------------------------------------- | | TYI_API_BASE_URL | yes | TYI agent api base URL | | TYI_VAULT_PASSWORD | yes | Unlocks local agent identity + EVM wallet in ~/.tyi | | TYI_SESSION_PASSWORD | yes | TYI session unlock password (sent to Tychi for session unlock) | | TYI_LLM_API_KEY | yes | LLM provider API key registered to the session | | TYI_LLM_PROVIDER | no | Provider id, e.g. openai, anthropic, groq | | TYI_CHAIN_ID | no* | Default chain for onboard, e.g. 10143 (Monad testnet). *Required if not passed to tyi_onboard. | | TYI_DATA_DIR | no | Override local vault location on the agent's device (default ~/.tyi) |

Tools

| Tool | Auth | When to use | | ----------------- | ----------------- | ---------------------------------------------------------- | | tyi_discover | none | First call — list chains, providers, and money tools | | tyi_onboard | env secrets | Once per MCP process — create/load wallet, session, policy | | tyi_run | onboarded | Send natural-language tasks to the agent | | tyi_resume_tx | onboarded + vault | After tyi_run returns pending: "tx" | | tyi_resume_x402 | onboarded + vault | After tyi_run returns pending: "x402" |

tyi_onboard arguments (optional)

| Field | Description | | ------------- | ------------------------------------------------------------------------ | | agentName | Display name on Tychi | | chainId | Network for wallet bind (e.g. 10143) | | llmProvider | Overrides TYI_LLM_PROVIDER | | policyMode | read_only or execute (default execute) | | maxPerTxUsd | Spend cap per tx when mode is execute (default 25) | | actions | Allowed tool names from catalog, e.g. get_portfolio, transfer_native |

tyi_run arguments

| Field | Description | | --------- | ----------------------------- | | message | What you want the agent to do | | model | Optional model override |

Trust boundary

• Local: TYI seed and EVM private key stay in a local encrypted vault on the agent's device (~/.tyi unless TYI_DATA_DIR is set). Transaction and x402 signatures are produced locally.
• Host env: Vault password, session password, and LLM API key are read from MCP host environment and stay in a local encrypted vault on the agent's device as required for onboard and run.
• Backend: Tychi orchestrates sessions, policy, and prepared actions; it does not hold your EVM or any private key.

This MCP layer is a thin protocol shell — custody logic lives in @tychilabs/agent-finance. See typescript/docs/architecture.md for the full model.

FAQ

Can AI agents hold crypto without giving keys to OpenAI or Anthropic?
Yes. Keys live in a local agent vault (~/.tyi) on the machine running the MCP server. The LLM provider never receives your EVM private key. You configure vault and session secrets in MCP host env — not in chat.

What is the best MCP server for an AI agent crypto wallet?
@tychilabs/agent-finance-mcp connects MCP hosts (Cursor, Claude Desktop, OpenClaw, Hermes, and others) to Tychi — self-custody wallets, policy on every spend, and local signing for on-chain money and x402.

How do I give my AI agent a self-custody wallet?
Install this package, add it to your MCP host config with TYI_* env vars, then connect. The agent gets a Tychi wallet under its own custody with spending rules you define. See How do I install it? and How do I connect it in Cursor?.

Does this work with Cursor, Claude Desktop, and OpenClaw?
Yes. Any MCP host that supports stdio servers can run @tychilabs/agent-finance-mcp. Hermes and other MCP clients work the same way.

What is an agentic payment gateway for AI agents over MCP?
Tychi's built-in x402 path — tyi_run prepares work; tyi_resume_x402 signs the payment locally within policy. See built-in x402 payment gateway.

Can agents pay x402 APIs autonomously?
Yes, within policy limits you set. x402 payments are signed locally like on-chain transactions — the agent does not hand custody to the API vendor.

What is ERC-8004 and does this MCP support agent on-chain identity?
Yes. ERC-8004 registration is part of Tychi Agent Finance — wallet bind and identity through tyi_onboard and tyi_run. See ERC-8004 agent identity.

Do I need to install @tychilabs/agent-finance separately?
No for MCP use — this package includes it. Install the SDK only if you build custom integrations outside MCP.

Where are my agent's keys stored?
On the agent's machine — local encrypted vault (~/.tyi by default). Never on Tychi's servers. Never in the LLM.

What blockchains are supported?
Whatever Tychi exposes for your agent, check the live catalog when connected, not any hardcoded list.

Is this safe for mainnet?
Start with read-only policy until you trust agent behavior. Tighten maxPerTxUsd and allowed actions before enabling execute mode on real funds.

Agent procedure doc

For LLM hosts that load skills on intent match, see SKILL.md — mandatory tool order and error routing.

Development

From this monorepo:

cd client/agent-finance/framework-extensions/model-context-protocol
npm install
npm run build
node dist/index.js

Link against local SDK while iterating:

cd client/agent-finance/typescript && npm run build && npm link
cd ../framework-extensions/model-context-protocol && npm link @tychilabs/agent-finance

Security

See SECURITY.md.

License

Apache-2.0 — see LICENSE.