delta-exchange-mcp 0.3.0

Official MCP server for Delta Exchange India — market data and account read for AI assistants.

delta-exchange-mcp

Official MCP (Model Context Protocol) server for Delta Exchange India. Lets AI assistants (Claude Desktop, Claude Code, Cursor, Zed, Codex) query Delta Exchange market data and your own account (read-only) through standardized tools.

Status: Beta. Functional and used internally, but the tool surface and configuration may still change. Please open an issue for bugs, missing tools, or rough edges. Early reports directly shape what ships next.

What you get: 9 public market-data tools + 12 authenticated read-only account tools (positions, orders, fills, wallet, stats, leverage, preferences, profile). No mutations. The server cannot place, edit, or cancel orders.

---

Quick start

Prerequisite: uv installed on your machine.

Sanity-check the install:

uvx delta-exchange-mcp --help

The server runs local stdio only: your MCP client launches it as a subprocess, and your API keys never leave your machine. uvx resolves the latest published version from PyPI on each launch. To pin a specific version, use uvx "delta-exchange-mcp==0.2.0".

Install in your MCP client

DELTA_API_KEY / DELTA_API_SECRET are optional in every snippet below — drop them for public-data-only mode. Set DELTA_MCP_ENV=india_testnet for testnet.

Claude Code

claude mcp add delta-exchange-mcp \
  --scope user \
  --env DELTA_MCP_ENV=india_prod \
  --env DELTA_API_KEY=your-api-key \
  --env DELTA_API_SECRET=your-api-secret \
  -- uvx delta-exchange-mcp

--scope user makes the server available across all projects. Verify with claude mcp list.

Cursor

Global: ~/.cursor/mcp.json (or %USERPROFILE%\.cursor\mcp.json on Windows). Project-scoped alternative: .cursor/mcp.json in the repo root.

{
  "mcpServers": {
    "delta-exchange-mcp": {
      "command": "uvx",
      "args": ["delta-exchange-mcp"],
      "env": {
        "DELTA_MCP_ENV": "india_prod",
        "DELTA_API_KEY": "your-api-key",
        "DELTA_API_SECRET": "your-api-secret"
      }
    }
  }
}

Restart Cursor or open Settings → Tools & MCP to refresh.

Codex

Add to ~/.codex/config.toml:

[mcp_servers.delta-exchange-mcp]
command = "uvx"
args = ["delta-exchange-mcp"]
env = { DELTA_MCP_ENV = "india_prod", DELTA_API_KEY = "your-api-key", DELTA_API_SECRET = "your-api-secret" }

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json (macOS / Linux) or %USERPROFILE%\.codeium\windsurf\mcp_config.json (Windows). UI route: Settings → Cascade → Plugins (MCP servers) → Manage Plugins → View raw config.

{
  "mcpServers": {
    "delta-exchange-mcp": {
      "command": "uvx",
      "args": ["delta-exchange-mcp"],
      "env": {
        "DELTA_MCP_ENV": "india_prod",
        "DELTA_API_KEY": "your-api-key",
        "DELTA_API_SECRET": "your-api-secret"
      }
    }
  }
}

Zed

Add to ~/.config/zed/settings.json (user-level) or .zed/settings.json (project-level). Zed uses the top-level key context_servers and nests command as an object — note the shape difference from other clients:

{
  "context_servers": {
    "delta-exchange-mcp": {
      "command": {
        "path": "uvx",
        "args": ["delta-exchange-mcp"],
        "env": {
          "DELTA_MCP_ENV": "india_prod",
          "DELTA_API_KEY": "your-api-key",
          "DELTA_API_SECRET": "your-api-secret"
        }
      }
    }
  }
}

VS Code (GitHub Copilot)

Add to .vscode/mcp.json in your workspace. The top-level key is servers and each entry needs an explicit "type": "stdio":

{
  "servers": {
    "delta-exchange-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": ["delta-exchange-mcp"],
      "env": {
        "DELTA_MCP_ENV": "india_prod",
        "DELTA_API_KEY": "your-api-key",
        "DELTA_API_SECRET": "your-api-secret"
      }
    }
  }
}

Claude Desktop

Open Settings → Developer → Edit config, or edit directly at:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "delta-exchange-mcp": {
      "command": "uvx",
      "args": ["delta-exchange-mcp"],
      "env": {
        "DELTA_MCP_ENV": "india_prod",
        "DELTA_API_KEY": "your-api-key",
        "DELTA_API_SECRET": "your-api-secret"
      }
    }
  }
}

Quit and relaunch Claude Desktop for changes to take effect.

Running a dev / unreleased branch

To test an unreleased commit, branch, or fork before it's on PyPI, swap uvx delta-exchange-mcp for uvx --from git+<repo-url>@<ref> delta-exchange-mcp. <ref> can be a branch, tag, or commit SHA.

CLI sanity check:

uvx --from git+https://github.com/delta-exchange/delta-exchange-mcp.git@develop delta-exchange-mcp --help

uv caches the git resolution, so to pick up new commits on the same branch:

uvx --refresh --from git+https://github.com/delta-exchange/delta-exchange-mcp.git@develop delta-exchange-mcp --help

In your MCP client config

Replace args in any snippet above with the git+ form. Three flavours:

Claude Code:

claude mcp add delta-exchange-mcp-dev \
  --scope user \
  --env DELTA_MCP_ENV=india_prod \
  -- uvx --from git+https://github.com/delta-exchange/delta-exchange-mcp.git@develop delta-exchange-mcp

Cursor / Windsurf / Claude Desktop (any mcpServers JSON):

{
  "mcpServers": {
    "delta-exchange-mcp-dev": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/delta-exchange/delta-exchange-mcp.git@develop",
        "delta-exchange-mcp"
      ],
      "env": {
        "DELTA_MCP_ENV": "india_prod"
      }
    }
  }
}

Zed (nested command object):

{
  "context_servers": {
    "delta-exchange-mcp-dev": {
      "command": {
        "path": "uvx",
        "args": [
          "--from",
          "git+https://github.com/delta-exchange/delta-exchange-mcp.git@develop",
          "delta-exchange-mcp"
        ],
        "env": {
          "DELTA_MCP_ENV": "india_prod"
        }
      }
    }
  }
}

Register the dev server under a separate name (e.g. delta-exchange-mcp-dev) so it doesn't collide with the PyPI install. The git+URL form rebuilds from source on each launch and is meant for testing unreleased changes — stick with uvx delta-exchange-mcp for everyday use.

Updating

uvx caches the resolved package, so a new PyPI release isn't picked up automatically. To move to the latest version:

1. If your config pins a version (uvx "delta-exchange-mcp==0.1.1"), bump the pin to the new version, or drop it to float to latest.

2. Refresh the uvx cache so it fetches the new build:

   uvx --refresh delta-exchange-mcp --help
   

3. Reload the server so your client respawns the process — in Claude Code, run /mcp and reconnect delta-exchange-mcp, or restart the client. Other clients: restart the app.

New tools appear only after the respawn. The MCP list_changed notification refreshes the tool list of an already-running server; it does not swap the underlying package version, which always requires a restart.

1. Create a key at delta.exchange/app/account/manageapikeys (testnet: demo.delta.exchange).
2. Both api_key and api_secret are shown once at creation. Save the secret immediately; it can't be re-derived.
3. Read Data permission is enough. Trading permission is not required and not used.
4. Recommended: whitelist your IP on the key. Delta blocks non-whitelisted IPs and surfaces your current IP in the error message if it fires.
5. Match the environment: prod keys with DELTA_MCP_ENV=india_prod, demo keys with DELTA_MCP_ENV=india_testnet. Mixing them returns InvalidApiKey.

Environment variables

Var	Default	Purpose
DELTA_MCP_ENV	india_prod	india_prod or india_testnet.
DELTA_API_KEY	(unset)	API key. Optional; when set with DELTA_API_SECRET, account tools register.
DELTA_API_SECRET	(unset)	API secret matching DELTA_API_KEY.
DELTA_MCP_DEBUG	(unset)	1/true/yes/on writes HTTP request URLs and response bodies to a log file (see Debugging).
DELTA_MCP_DEBUG_FILE	(auto)	Override the debug log path. Default: ~/.delta-exchange-mcp/logs/debug-<timestamp>-<pid>.log.

Debugging / reporting a bug

To capture exactly what the server sends and receives — useful when a tool returns something unexpected — set DELTA_MCP_DEBUG=1 in your MCP client config:

"delta-exchange": {
  "command": "uvx",
  "args": ["delta-exchange-mcp"],
  "env": {
    "DELTA_MCP_ENV": "india_prod",
    "DELTA_MCP_DEBUG": "1"
  }
}

Restart the client and re-run the action. Each HTTP call (request URL incl. filter params + response body + status) is logged to ~/.delta-exchange-mcp/logs/. The exact path is printed on startup and you can also just ask the assistant: "where is the debug log?" (the get_debug_status tool returns it).

The log never contains your API key, secret, or request signatures — but response bodies do contain your account data (balances, positions, transactions). Review before sharing.

Tools

Public market data (always available)

Tool	What it returns
list_products / get_product	Catalog of tradable instruments and per-product metadata.
list_tickers / get_ticker	Last price, 24h stats, mark price, OI.
get_options_chain	Option chain snapshot for a given underlying / expiry.
get_orderbook	Bid/ask depth for a symbol.
get_recent_trades	Last N public trades.
get_candles	OHLC candles by resolution.
get_reference_data	Assets + indices reference.

Account read-only (requires DELTA_API_KEY + DELTA_API_SECRET)

Tool	What it returns
get_positions / get_margined_positions	Open positions, sizes, entry, unrealized PnL.
get_wallet_balances / get_wallet_transactions	Per-asset balances + ledger.
get_open_orders / get_order_history / get_order_by_id	Active and historical orders.
get_fills	Trade fills (own).
get_product_leverage	Per-product leverage setting.
get_trading_stats / get_trading_preferences / get_profile	Account-level stats, preferences, profile.

Example prompts

Once connected, you can ask things like:

• "What's the current BTCUSD mark price and 24h range?"
• "Show the options chain for BTC expiring this Friday."
• "What positions do I have open and what's my total unrealized PnL?"
• "List my fills from the last 24 hours grouped by symbol."
• "How much USDT do I have free vs blocked in margin?"

The assistant picks the right tool based on the question. You don't need to name the tool.

Development

uv sync                       # install deps
uv run pytest                 # run tests (no network, respx-mocked)
uv run ruff check src tests   # lint
uv run delta-exchange-mcp     # run server (stdio)

Testing with MCP Inspector

# stdio CLI mode
bash scripts/inspect.sh --cli --method tools/list
bash scripts/inspect.sh --cli --method tools/call \
  --tool-name get_ticker --tool-arg symbol=BTCUSD

# with auth
DELTA_API_KEY=... DELTA_API_SECRET=... \
  bash scripts/inspect.sh --cli --method tools/call --tool-name get_wallet_balances

# web UI
bash scripts/inspect.sh        # → http://localhost:6274

Maintainers: see RELEASING.md for the release procedure.

Roadmap

• Now: 9 public market-data + 12 authenticated read-only account tools.
• Next: trading mutations (place / edit / cancel / close, leverage change) gated behind an explicit DELTA_MCP_MODE=trade flag, with an audit log and basic guardrails.

Feedback & issues

This is the first public cut and we want to make it better. Please file:

• Bugs (incorrect data, signing/auth errors, crashes)
• Missing tools or fields you'd want exposed
• Rough edges in setup, docs, or error messages
• Anything you'd build on top of this if a primitive existed

→ github.com/delta-exchange/delta-exchange-mcp/issues

Please redact api_key / api_secret from any logs or screenshots before attaching.

Safety

• No mutations. Every tool is GET. The server cannot place, edit, or cancel orders.
• Local stdio only. Per-user keys never leave your machine; no shared hosted endpoint.
• Read the code. It's a financial-tool MCP; treat it like one.