Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Unofficial community MCP for the Capital.com Open API. Guarded two-phase trades; demo-first.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
CAP_ENV_FILE, CAP_API_KEY, CAP_IDENTIFIER, CAP_API_PASSWORD, CAP_ENV, CAP_ALLOW_TRADING, CAP_ALLOWED_EPICSValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"capitalcom": {
"command": "uvx",
"args": [
"capitalcom-mcp"
],
"env": {
"CAP_ENV_FILE": "your-value",
"CAP_API_KEY": "your-value",
"CAP_IDENTIFIER": "your-value",
"CAP_API_PASSWORD": "your-value",
"CAP_ENV": "your-value",
"CAP_ALLOW_TRADING": "your-value",
"CAP_ALLOWED_EPICS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add capitalcom --env CAP_ENV_FILE=your-value --env CAP_API_KEY=your-value --env CAP_IDENTIFIER=your-value --env CAP_API_PASSWORD=your-value --env CAP_ENV=your-value --env CAP_ALLOW_TRADING=your-value --env CAP_ALLOWED_EPICS=your-value -- uvx capitalcom-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"capitalcom": {
"command": "uvx",
"args": [
"capitalcom-mcp"
],
"env": {
"CAP_ENV_FILE": "your-value",
"CAP_API_KEY": "your-value",
"CAP_IDENTIFIER": "your-value",
"CAP_API_PASSWORD": "your-value",
"CAP_ENV": "your-value",
"CAP_ALLOW_TRADING": "your-value",
"CAP_ALLOWED_EPICS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"capitalcom": {
"type": "stdio",
"command": "uvx",
"args": [
"capitalcom-mcp"
],
"env": {
"CAP_ENV_FILE": "your-value",
"CAP_API_KEY": "your-value",
"CAP_IDENTIFIER": "your-value",
"CAP_API_PASSWORD": "your-value",
"CAP_ENV": "your-value",
"CAP_ALLOW_TRADING": "your-value",
"CAP_ALLOWED_EPICS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
CAP_ENV_FILE envCAP_ENV envCAP_ALLOW_TRADING envCAP_ALLOWED_EPICS envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account SimonTarara62, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: CAP_API_KEY, CAP_IDENTIFIER, CAP_API_PASSWORD
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.3.4) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Microsoft Exchange Online MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Exchange Online admin for MSPs: forwarding audits, EWS posture and offboarding, no PowerShell
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Self-hosted Model Context Protocol (MCP) server for the Capital.com Open API, written in Python on FastMCP. It exposes 42 safe, guarded trading and market-data tools — two-phase execution, allowlists, demo-first — to any MCP client, over stdio or HTTP. Built on the tested capitalcom-cli broker engine (SDK).
Works with Claude Desktop · Claude Code · Cursor · VS Code (Copilot) · Windsurf · ChatGPT — any MCP client.
⚠️ Unofficial & educational. Not affiliated with Capital.com. Trading is
risky and this is not financial advice. Trading is disabled by default;
all trades are two-phase (preview → confirm → execute) with allowlists and
size/rate limits. Start on a demo account. Apache-2.0 licensed.
No clone required — uvx runs it in an isolated, throwaway environment and always fetches the latest tested release:
uvx capitalcom-mcp --help # smoke test
Or install a persistent command with pipx:
pipx install capitalcom-mcp
uvx capitalcom-mcp always runs the latest published release. That is fine for trying it out, but for production or real-money use, pin the exact version so an unexpected update can't change tool behavior under you:
{
"mcpServers": { "capitalcom": { "command": "uvx", "args": ["capitalcom-mcp==0.3.4"], "env": { "CAP_ENV_FILE": "/Users/you/.config/capital-mcp/.env" } } } }
The CLI form is uvx capitalcom-mcp==0.3.4 run …. Pin to a version you have reviewed, and bump deliberately after reading the CHANGELOG.
Get an API key in the Capital.com app: Settings → API integrations (make a demo key first). Then run the wizard — it writes a 0600 file and prints the exact client snippet:
uvx capitalcom-mcp init
This writes ~/.config/capital-mcp/.env. Verify any time (no secrets printed):
uvx capitalcom-mcp doctor
Inspect the full effective configuration (redacted, offline) or confirm your credentials actually authenticate:
uvx capitalcom-mcp config # effective settings + credential source
uvx capitalcom-mcp doctor --login # verify authentication against the API
Prefer a secret manager? Set CAP_API_KEY_CMD / CAP_IDENTIFIER_CMD / CAP_API_PASSWORD_CMD to a command that prints the secret (e.g. op read op://vault/..., pass ...). The secret is fetched at launch and never written to disk or to your client config.
Every client uses the same command/args/env shape. Pasting "CAP_ENV_FILE": " " keeps secrets out of the client file; or put CAP_API_KEY/CAP_IDENTIFIER/CAP_API_PASSWORD directly in env.
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) / %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": { "capitalcom": { "command": "uvx", "args": ["capitalcom-mcp"], "env": { "CAP_ENV_FILE": "/Users/you/.config/capital-mcp/.env" } } } }
claude mcp add --transport stdio \
--env CAP_ENV_FILE=/Users/you/.config/capital-mcp/.env \ capitalcom -- uvx capitalcom-mcp
~/.cursor/mcp.json (global) or .cursor/mcp.json (project):
{
"mcpServers": { "capitalcom": { "command": "uvx", "args": ["capitalcom-mcp"], "env": { "CAP_ENV_FILE": "/Users/you/.config/capital-mcp/.env" } } } }
.vscode/mcp.json — note the root key is servers and type: "stdio":
{
"servers": { "capitalcom": { "type": "stdio", "command": "uvx", "args": ["capitalcom-mcp"], "env": { "CAP_ENV_FILE": "/Users/you/.config/capital-mcp/.env" } } } }
~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": { "capitalcom": { "command": "uvx", "args": ["capitalcom-mcp"], "env": { "CAP_ENV_FILE": "/Users/you/.config/capital-mcp/.env" } } } }
ChatGPT requires a remote server (stdio is not supported) — see Remote / VPS hosting. Once your server is reachable over HTTPS, enable Developer Mode (Settings → Connectors → Advanced) and add the server URL ending in /mcp. ChatGPT Deep Research connectors call two read-only tools, search and fetch, which this server implements; full custom tools require Developer Mode.
Run with streamable-HTTP instead of stdio:
CAP_ENV_FILE=/home/you/.config/capital-mcp/.env \
capitalcom-mcp run --transport http --host 0.0.0.0 --port 8000
Or via env (handy in systemd): CAP_MCP_TRANSPORT=http, CAP_MCP_HOST, CAP_MCP_PORT. Put it behind a TLS-terminating reverse proxy for any public use.
This server exposes 42 tools, 4 resources, and 7 guided prompts. All tool names are prefixed cap_ except the two ChatGPT Deep Research adapters (search, fetch). Mutating tools require confirm=true; trades are two-phase. The full surface is a stable contract — see API stability.
| Tool | What it does |
|---|---|
cap_session_status | Current login/session state. |
cap_session_login | Authenticate (optionally force=true). |
cap_session_ping | Keep-alive / liveness check. |
cap_session_logout | End the session. |
cap_session_switch_account | Switch the active trading account. |
cap_account_list | List accounts and the active account id. |
cap_account_preferences_get | Read account preferences (e.g. hedging mode). |
cap_account_preferences_set | Update preferences (confirm required). |
cap_account_history_activity | Account activity history. |
cap_account_history_transactions | Transaction history. |
cap_account_demo_topup | Top up a demo balance (confirm required). |
| Tool | What it does |
|---|---|
cap_market_search | Search instruments by term. |
cap_market_get | Full market details + snapshot for an EPIC. |
cap_market_navigation_root | Top-level market navigation nodes. |
cap_market_navigation_node | Drill into a navigation node. |
cap_market_prices | Historical OHLC candles. |
cap_market_sentiment | Client long/short positioning. |
| Tool | What it does |
|---|---|
cap_trade_positions_list | Open positions. |
cap_trade_positions_get | One position by deal id. |
cap_trade_orders_list | Working (pending) orders. |
cap_trade_confirm_get | Fetch a deal confirmation by reference. |
cap_trade_confirm_wait | Poll until a deal confirms (or times out). |
cap_trade_preview_position | Phase 1: validate a market position (no execution). |
cap_trade_preview_working_order | Phase 1: validate a working order. |
cap_trade_execute_position | Phase 2: execute a previewed position (confirm). |
cap_trade_execute_working_order | Phase 2: place a previewed working order (confirm). |
cap_trade_positions_close | Close a position (confirm). |
cap_trade_orders_cancel | Cancel a working order (confirm). |
cap_trade_positions_amend | Amend stop/limit on a position (confirm). |
cap_trade_orders_amend | Amend a working order (confirm). |
| Tool | What it does |
|---|---|
cap_watchlists_list | List watchlists. |
cap_watchlists_get | Get one watchlist's markets. |
cap_watchlists_create | Create a watchlist (confirm). |
cap_watchlists_add_market | Add an EPIC (confirm). |
cap_watchlists_remove_market | Remove an EPIC (confirm). |
cap_watchlists_delete | Delete a watchlist (confirm). |
CAP_WS_ENABLED=true)| Tool | What it does |
|---|---|
cap_stream_prices | Live bid/ask updates for EPICs. |
cap_stream_candles | Live OHLC candle updates. |
cap_stream_alerts | Threshold price alerts. |
cap_stream_portfolio | Live position/P&L updates. |
| Tool | What it does |
|---|---|
search | Read-only instrument search (ChatGPT connector contract). |
fetch | Read-only instrument fetch by id (ChatGPT connector contract). |
| URI | What it returns |
|---|---|
cap://status | Session/connection status snapshot. |
cap://risk-policy | Active risk policy (trading flag, caps). |
cap://allowed-epics | The trading EPIC allowlist. |
cap://market-cache/{epic} | Cached market snapshot for an EPIC. |
Prompts are reusable workflows your client can launch by name. They emit step-by-step guidance that orchestrates the tools above — they never trade on their own.
| Prompt | Purpose |
|---|---|
market_scan | Scan a watchlist for opportunities (prices + sentiment). |
trade_proposal | Design a risk-sized trade and validate it via preview. |
execute_trade | Safely execute a previously previewed trade. |
position_review | Review open positions and working orders. |
live_price_monitor | Stream prices and flag threshold moves. |
real_time_alerts | Configure and watch live price alerts. |
live_portfolio_monitor | Stream live portfolio P&L with a threshold. |
CAP_ALLOW_TRADING=true and the EPIC is in CAP_ALLOWED_EPICS (or ALL).confirm=true required for mutations.CAP_DRY_RUN=true blocks all executions. A TIMEOUT confirmation is ambiguous — reconcile, don't blindly retry.make install # editable MCP + capitalcom-cli SDK from PyPI
make check # ruff + mypy + pytest (offline; no network/credentials)
End-to-end tests drive every tool through the MCP against the demo API (read, watchlists, account switch, preview/execute/amend/close/cancel, streaming). They place real demo orders and clean up after themselves, so use a demo .env with trading + streaming enabled:
# demo .env: CAP_ALLOW_TRADING=true, CAP_ALLOWED_EPICS=GOLD, CAP_WS_ENABLED=true
CAP_MCP_E2E=1 pytest -m e2e -v
Contributions are welcome — this is a community project. Start with CONTRIBUTING.md, browse good first issues, and see the roadmap for where it's heading. The architecture and a worked "add a tool" example are in docs/extending.md.
Apache-2.0. See LICENSE and NOTICE.