# Keel MCP MCP Server > **Keel MCP MCP Server** is a hosted, multitenant Model Context Protocol (MCP) server run by **MewCP** (https://mewcp.com), giving AI agents managed access to Keel MCP. > > MewCP takes care of all MCP infrastructure for you — credential storage, OAuth flows, > token refresh, and production-grade auto-scaling — so your AI agents can connect to > third-party services and run freely without you managing any MCP server yourself. > > Server page: https://mewcp.com/mcp/usekeel-mcp > MewCP docs: https://docs.mewcp.com > Full catalog: https://mewcp.com/llms.txt --- ## About Keel helps traders build, edit, and backtest systematic crypto perpetual futures strategies on Hyperliquid. Analyze historical performance with fees and slippage, compare backtest results, explore verified strategies, and monitor live strategy performance without executing trades. --- ## Details - Server ID: `usekeel-mcp` - Version: 0.9.0 - Tools: 29 - Authentication: OAuth, managed by MewCP - Transport: http --- ## Access The gateway URL below serves your **entire MewCP toolset**, not this server on its own. Pasting a config snippet is not enough — Keel MCP has to be in the toolset first. In order: 1. Add Keel MCP to your toolset at https://mewcp.com/mcp/usekeel-mcp 2. Connect your Keel MCP account (OAuth); MewCP stores the credential and attaches it to each call 3. Copy your MewCP API key from the dashboard (Developer) 4. Configure your client with the snippet for it below Once connected, an agent does **not** see this server's tools as top-level tools. It sees four meta-tools and reaches everything through them: - `search(query)` — find tools by keyword across the toolset - `get_schema(tools)` — full description and arguments for the tools you picked - `list_accounts(provider)` — only when one app has several connected accounts - `call_tool(server_maskedId, tool_name, args)` — execute So the list below is what `search` can return for this server, not a set of callable tool names on their own. --- ## Tools (29) Descriptions are truncated to 160 characters; call `get_schema` for the full text and the argument schema. Where a tool is annotated, its type is shown — treat `destructive` as irreversible. - `keel_app_link` _(read)_ — Returns a link to view and manage this strategy in the Keel web app. A strategy id (`str_...`) links to the strategy editor, a backtest run id (`btr_...`) to… - `keel_backtest_compare` _(read)_ — Compare 2–8 completed backtests side by side — one run alone is `keel_backtest_summarize`. One table with deltas against the first id and each run's cost… - `keel_backtest_positions` _(read)_ — The positions of ONE completed backtest, entry to exit — what drove its result. Default: a summary (count, win rate, P&L by asset, five best, five worst).… - `keel_backtest_run` _(write)_ — Submit a NEW backtest run of a strategy — a finished run's result is `keel_backtest_summarize`, a running one's wait `keel_backtest_watch`. Runs server HEAD… - `keel_backtest_summarize` _(read)_ — Show ONE completed backtest run in full — several runs together are `keel_backtest_compare`, a still-running one `keel_backtest_watch`. The card carries… - `keel_backtest_watch` _(read)_ — Wait on a running backtest (started by `keel_backtest_run`) until it finishes or the timeout elapses — a finished run in full is `keel_backtest_summarize`. It… - `keel_components_get_many` _(read)_ — Fetch the full contract of SEVERAL components in one call — one component alone is `keel_components_get`. Each entry carries the parameter list, type… - `keel_components_get` _(read)_ — Fetch the full contract for ONE known pipeline component — several at once are `keel_components_get_many`. It carries the parameter list, type signature, slot… - `keel_components_search` _(read)_ — Search the Keel pipeline component catalog — the chosen candidates go to `keel_components_get_many`, which verifies their types and slots. It matches `keyword`… - `keel_connection_check` _(read)_ — Check this connection to Keel when a call fails for an environmental reason — identity and quota are `keel_account_status`. One pass over sign-in, API… - `keel_feedback` _(destructive)_ — Send feedback about Keel to the Keel team — friction, praise or a bug report in `goal`, `kind` and `text` — when the user asks or agrees; a failing connection… - `keel_library_list` _(read)_ — List the Keel Library — the verified, backtested strategy entries published in the product; the caller's own strategies are `keel_strategy_search`. Each row… - `keel_library_get` _(read)_ — Read one Keel Library entry's verified facts before a fork — forking it is `keel_library_fork`. They are its headline metrics, backtest window, data freshness… - `keel_library_fork` _(write)_ — Fork a verified Keel Library entry into the caller's org as an editable strategy — a copy of a Keel strategy or a share link is `keel_strategy_fork`. The fork… - `keel_live_monitor` _(read)_ — Read-only monitoring of the strategies running on the caller's account; acting on one happens in the Keel web app (`keel_app_link` returns the link). `view`… - `keel_strategy_readiness` _(read)_ — Report what evidence a saved strategy has and still lacks — a brief, a baseline backtest, named failure modes — and the one next step; a backtest is… - `keel_plan_usage` _(read)_ — Report the org's own Keel plan and its backtest usage this period — auth, identity and visible tools are `keel_account_status`. It returns the plan name, the… - `keel_share_create` _(destructive)_ — Publish a strategy (`str_*`) or a backtest (`btr_*`) at a public usekeel.io/share/ URL. The page shows the strategy's name, description, backtest metrics,… - `keel_account_status` _(read)_ — Report who is signed in to Keel, on which plan and with how much quota left — plan usage per unit is `keel_plan_usage`, a failing connection… - `keel_strategy_compose` _(write)_ — Save a strategy from Keel DSL source — new, or with `strategy_id` its next version; components come from `keel_components_search` and… - `keel_strategy_diff` _(read)_ — What changed between two strategies or two versions of one (versions: `keel_strategy_history`; several runs' results: `keel_backtest_compare`). Reports added,… - `keel_strategy_fork` _(write)_ — Copy a strategy into the caller's org as a separate strategy with its own history; the original's source and versions are unchanged (saving a new version of a… - `keel_strategy_get` _(read)_ — Render a saved strategy as its structure card — a version's commit id alone is `keel_strategy_history`, with no card. `version` (HEAD, tag, sequence number or… - `keel_strategy_history` _(read)_ — Show a strategy's commit history — each version's commit id, the ref `keel_backtest_run` pins and `keel_strategy_diff` compares. Each entry carries the… - `keel_strategy_notes_read` _(read)_ — Read the notes saved on one of the caller's strategies — the durable context that outlives one session; adding one is `keel_strategy_notes_add`. The result… - `keel_strategy_notes_add` _(write)_ — Add a note to a strategy's saved notes, kept with the strategy in the user's Keel account and returned by `keel_strategy_notes_read` in later sessions. Each… - `keel_strategy_restore` _(write)_ — Add a new version of a strategy equal to an earlier one — a restore; the history is `keel_strategy_history`, the current strategy `keel_strategy_get`. `ref` is… - `keel_strategy_search` _(read)_ — Search and list the org's strategies — the entry point for an EXISTING strategy, before `keel_strategy_get`. It matches `query` (name substring) and pages with… - `keel_help` _(read)_ — Fetch one Keel knowledge or DSL-reference document by topic — components are `keel_components_search`, one component's contract `keel_components_get`. With no… --- ## Connect Gateway URL: https://gateway.mewcp.com/personal/mcp Every request carries one header: Authorization: Bearer Replace `API_KEY` with your own key from the dashboard (Developer). ## Apps ### Claude Desktop Mac & Windows app - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json` - Windows: `%APPDATA%\Claude\claude_desktop_config.json` ```json { "mcpServers": { "mewcp": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "https://gateway.mewcp.com/personal/mcp", "--header", "Authorization:${AUTH_HEADER}" ], "env": { "AUTH_HEADER": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open Claude Desktop → Settings → Developer → "Edit Config" 2. Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one) 3. Save the file, then quit Claude Desktop completely and reopen it 4. Start a new conversation — your tool will be available ### VS Code Copilot / Cline - Command Palette → "MCP: Open User Configuration" (opens mcp.json). For one project only, use .vscode/mcp.json instead. ```json { "mcp.servers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have a "servers" section in your mcp.json? Just add the server entry inside it. 1. Open VS Code → Command Palette (Cmd+Shift+P / Ctrl+Shift+P) 2. Run "MCP: Open User Configuration" to open your mcp.json 3. Paste the snippet and save 4. Start the server when prompted (or from the MCP servers view) and use it in Copilot Chat ### Cursor AI-first editor - macOS: `~/.cursor/mcp.json` - Windows: `%USERPROFILE%\.cursor\mcp.json` ```json { "mcpServers": { "mewcp": { "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your mcp.json? Just add the server entry inside it. 1. Open Cursor → Settings → Cursor Settings → MCP 2. Click "Add new global MCP server" 3. Paste the snippet and save 4. Restart Cursor ### Codex OpenAI's CLI agent - Add the snippet to your Codex MCP config or your standard MCP config file for the CLI tool you use. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Codex generally reads a standard MCP server block, so you can add this alongside your other configured servers. 1. Open your Codex MCP config or project-level config file 2. Paste the MewCP server block inside the config JSON/TOML structure your tool expects 3. Save the file and restart Codex 4. Verify the tool is available inside a fresh session ### Claude Code Anthropic's CLI agent - ~/.claude.json (user scope) or .mcp.json in your project root — create it if it doesn't exist. Or skip the file and use the CLI command below. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open ~/.claude.json (or .mcp.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file and start (or restart) Claude Code 4. Or skip the file entirely and run the CLI command below instead ### OpenCode Open-source terminal agent - ~/.config/opencode/opencode.json (global) or opencode.json in your project root — create it if it doesn't exist. ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "mewcp": { "type": "remote", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcp" section in your opencode.json? Just add the server entry inside it. 1. Open ~/.config/opencode/opencode.json (or opencode.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and start (or restart) OpenCode ### OpenClaw Self-hosted agent gateway - ~/.openclaw/openclaw.json — create it if it doesn't exist. ```json { "mcp": { "servers": { "mewcp": { "transport": "streamable-http", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } } ``` Already have an "mcp" section in your openclaw.json? Just add the server entry inside "servers". 1. Open ~/.openclaw/openclaw.json in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and restart OpenClaw ### Antigravity Google's agentic IDE - ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (workspace-local) — create it if it doesn't exist. ```json { "mcpServers": { "mewcp": { "serverUrl": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. Remote servers must use the "serverUrl" field — the legacy "url"/"httpUrl" fields aren't supported. 1. In the editor's agent side panel, click "…" → "MCP Servers" → "Manage MCP Servers" → "View raw config" (Antigravity CLI: type /mcp instead to open the Interactive MCP Manager) 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file — the server connects automatically ### Hermes Nous Research's CLI agent - config.yaml in your Hermes config directory (~/.hermes) — add this under a top-level "mcp_servers:" key. ```yaml mcp_servers: mewcp: url: "https://gateway.mewcp.com/personal/mcp" headers: Authorization: "Bearer API_KEY" ``` Already have an "mcp_servers" section in your config.yaml? Just add the server entry inside it. 1. Open config.yaml in your Hermes config directory 2. Paste the snippet under the top-level "mcp_servers:" key (merge with existing entries if you have any) 3. Save the file, then run /reload-mcp in Hermes (or start a fresh session) 4. Ask Hermes "Tell me which MCP-backed tools are available right now" to confirm it connected ### DeepSeek Harness DeepSeek's agent harness - cordis.yml in your DSH project — or the patch file you mount plugins from. ```yaml - id: mcp-mewcp name: '@deepseek-ai/dsh-mcp-client' config: serverName: mewcp transport: streamable-http url: https://gateway.mewcp.com/personal/mcp headers: Authorization: "Bearer API_KEY" ``` One plugin instance = one MCP server. Add this entry to your plugin list; don't nest it inside another entry. 1. Open cordis.yml (or your patch file) in your DSH project 2. Paste the entry into your plugin list, keeping the leading dash and indentation 3. Restart DSH (or let HMR reload) — tools register as mcp__mewcp__ 4. Verify with: dsh web --dump-config | grep -A3 mcp ## SDKs ### Python fastmcp client ```python import asyncio from fastmcp import Client from fastmcp.client.transports import StreamableHttpTransport SERVER_URL = "https://gateway.mewcp.com/personal/mcp" API_KEY = "API_KEY" transport = StreamableHttpTransport( url=SERVER_URL, headers={ "Authorization": f"Bearer {API_KEY}", } ) async def main(): client = Client(transport) async with client: tools = await client.list_tools() print(tools) asyncio.run(main()) ``` 1. Install fastmcp: pip install fastmcp 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run your script ### TypeScript MCP SDK ```typescript import { Client } from "@modelcontextprotocol/sdk/client/index.js"; import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js"; const SERVER_URL = "https://gateway.mewcp.com/personal/mcp"; const API_KEY = "API_KEY"; const transport = new StreamableHTTPClientTransport(new URL(SERVER_URL), { requestInit: { headers: { Authorization: `Bearer ${API_KEY}`, }, }, }); const client = new Client({ name: "mewcp-client", version: "1.0.0" }); await client.connect(transport); const tools = await client.listTools(); console.log(tools.tools.map((t) => t.name)); ``` 1. Install: npm install @modelcontextprotocol/sdk 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run with Node 18+ as an ES module (e.g. npx tsx script.ts)