Boba MCP

What is Boba MCP?

Boba MCP is a CLI tool that connects Claude to Boba trading. It acts as a local proxy, handling JWT authentication so Claude never sees your credentials. It is designed for traders who want to use Claude with Boba’s trading API.

How to use Boba MCP?

Install globally with npm install -g @tradeboba/cli, then run boba to start the interactive menu. Key commands include boba login for credentials, boba install to set up Claude, and boba launch to begin trading. Options like --agent-id and --secret allow non-interactive login.

Key features of Boba MCP

• Claude never sees your credentials
• Full audit trail of all tool calls
• Interactive TUI using BubbleTea and LipGloss
• Proxy allows you to stop access anytime
• Credentials stored in OS Keychain
• HTTPS enforced for all backend communication

Use cases of Boba MCP

• Launch Claude Code or Claude Desktop with Boba trading tools
• Revoke proxy access remotely at agents.boba.xyz
• Run trading commands without exposing API secrets to Claude
• Use non-interactive login for automated setups

FAQ from Boba MCP

What changed in v0.3.0?

v0.3.0 is a full rewrite as a native Go binary shipped through npm. New commands: boba login replaces boba init, and boba launch now lets you choose Claude Code or Claude Desktop.

What runtime is required?

No Node.js runtime is needed. The CLI is a native Go binary distributed via npm, making it faster and self-contained.

How are credentials stored?

Your agent secret and auth tokens are stored in the OS Keychain. A per-session token is used for proxy authentication, and only the MCP bridge can call the proxy.

Is HTTPS enforced?

Yes, HTTPS is enforced for all backend communication. Backend URLs are restricted to known Boba hosts, and no sensitive data is written to debug logs.

What are the known limitations?

This software is experimental and provided “as is” without warranty. Trading involves significant financial risk. Use at your own risk, and never trade more than you can afford to lose.