MCP server
The @banger/mcp server lets MCP-compatible clients (Claude Desktop, Cursor, Claude Code, etc.) read your strategy state. Write tools — placing orders, deploying strategies — are not exposed in v0; we want to ship the read surface first and add writes behind a separate API-key scope.
TL;DR: your agent can answer “how is my strategy doing?” but not “buy 100 of NO on this Polymarket contract.” That’s the v0 promise.
Install (Claude Desktop / Cursor / Claude Code)
Add to your MCP client config (e.g. ~/.config/claude/claude_desktop_config.json):
{
"mcpServers": {
"banger": {
"command": "npx",
"args": ["-y", "@banger/mcp"],
"env": {
"BANGER_API_KEY": "bk_live_..."
}
}
}
}Generate an API key with read scope from your Settings page. The MCP server only needs read.
Tools (v0)
list_strategies
Lists your deployments (one row per running/paper/stopped instance) with the strategy name, mode, and status. Filter by status.
{
"name": "list_strategies",
"arguments": { "status": "running" }
}get_strategy_performance
Returns a P&L time series + summary stats for a single strategy. Good for “how is X doing?”
{
"name": "get_strategy_performance",
"arguments": { "strategy_id": "...", "range": "24h" }
}list_open_positions
Current open positions across all running deployments. Optional venue filter.
{
"name": "list_open_positions",
"arguments": { "venue": "polymarket" }
}Roadmap
- v0.1: write tools (deploy, stop, place_order) behind a separate
deploy-scope key - v0.2: streaming subscriptions (live tick + fill notifications)
- v0.3: agentic strategy authoring — tool that takes natural language and emits a Strategy file