About Boba MCP
Boba MCP is a command line tool (Boba CLI) that connects Claude to the Boba decentralized trading backend. A local proxy forwards tool calls so Claude never sees the credentials, aimed at users who want agents to take part in onchain trading.
Key features
- 01Local proxy forwarding Claude tool calls
- 02Credentials stored in the OS keychain
- 03Supports Claude Desktop and Claude Code
- 04Interactive menu and non-interactive login
- 05Logs all tool calls for audit
Use cases
- 01Letting Claude execute decentralized trades through Boba
- 02Setting up a trading environment in Claude Code or Claude Desktop
- 03Reviewing audit records of agent-initiated tool calls
MCP support
The Boba CLI runs a local proxy, and the MCP bridge forwards Claude requests to the Boba backend trading API.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project README
Connect Claude to Boba trading in seconds.
Install · Quick Start · Commands · How It Works
Install
npm install -g @tradeboba/cli
Quick Start
npm install -g @tradeboba/cli
boba
That's it — the interactive menu walks you through everything.
Commands
| Command | Description |
|---|---|
boba login | Log in with your agent credentials |
boba install | Set up Claude to use Boba |
boba launch | Start trading with Claude |
boba start | Run the Boba proxy |
boba status | See if everything's working |
boba config | Change your settings |
boba auth | Test your connection |
boba logout | Sign out |
Command options
boba login --agent-id ID --secret S # Non-interactive login
boba start --port 4000 # Custom port
boba install --desktop-only # Claude Desktop only
boba install --code-only # Claude Code only
boba launch --iterm # Use iTerm instead of Terminal (macOS)
How It Works
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Claude │ ───▶ │ Boba CLI │ ───▶ │ Boba MCP │
│ (no creds) │ │ (proxy) │ │ (backend) │
└─────────────┘ └─────────────┘ └─────────────┘
localhost JWT auth trading API
- Claude never sees your credentials
- You control access — stop the proxy anytime
- Full audit trail — all tool calls logged
Upgrading to v0.3.0
Important
v0.3.0 is a full rewrite — the CLI is now a native Go binary shipped through npm. It's faster, has no Node.js runtime dependency, and includes an interactive TUI.
What changed:
boba initis nowboba login(boba initstill works as an alias)- Interactive menus — just run
bobato see all optionsboba launchnow lets you pick Claude Code or Claude Desktopboba launchnow lets you launch with layoutsboba loginnow has onboarding flow- Nice TUI changes using BubbleTea, LipGloss and HuH
To upgrade:
npm install -g @tradeboba/cli boba login
Security
| Credential Storage | Agent secret + auth tokens stored in OS Keychain |
| Proxy Auth | Per-session token — only the MCP bridge can call the proxy |
| Transport | HTTPS enforced for all backend communication |
| URL Allowlisting | Backend URLs restricted to known Boba hosts |
| No Debug Logging | No sensitive data written to logs |
| Access Control | Revoke anytime at agents.boba.xyz |
License
MIT
Warning
This software is experimental. Provided "as is" without warranty of any kind.
Use at your own risk. Boba assumes no liability for any losses or damages arising from use of this software.
Trading involves significant financial risk. Never trade more than you can afford to lose.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.