Troubleshooting

The server doesn't appear in my client

• Confirm the config file is the right one for your client and that JSON is valid (a trailing comma breaks it silently).
• Fully restart the client after editing config. Most clients load MCP servers only at launch.
• Check your client's MCP/developer logs for a startup error from delta-exchange.

uvx: command not found

uv isn't installed or isn't on your PATH. Install it (instructions) and restart your terminal and your AI client so it inherits the updated PATH. Some GUI clients don't see shell PATH changes until a full restart (or a reboot on macOS).

uvx delta-exchange-mcp fails to resolve

Run it directly in a terminal to see the real error:

uvx delta-exchange-mcp --help

A network/proxy issue or an old uv are the usual causes. Update uv:

uv self update

Authentication / signature errors

• The key and DELTA_MCP_ENV must match: production key → india_prod, testnet key → india_testnet. A mismatch is the most common cause.
• Re-check DELTA_API_KEY / DELTA_API_SECRET for stray spaces or truncation.
• If you set an IP whitelist on the key, confirm your current IP is allowed.
• Confirm the key still exists and has Read Data permission.

Account tools return empty results

• You may have no open positions/orders. Try a market-data tool first to confirm the connection works.
• ~90-day default window: get_fills, get_wallet_transactions, and bulk_fills_export return only the last ~90 days unless you pass a start_time_us. If older trades are missing, state an explicit date range in your prompt.
• Pagination: history tools return a page at a time. Ask the model to follow meta.after cursors for the full set, or use bulk_fills_export for fills.
• Timestamps are in microseconds for fills/orders/wallet history. A wrong unit in a time filter silently returns nothing.

Market-data tools work but account tools don't

That means the server is running but the key isn't being read. Verify the env block is present in the config and that you restarted the client. Market data needs no key, so it works regardless.

Trading tools don't appear

The trading tools (place_order, cancel_order, …) register only when both DELTA_MCP_MODE=trade is set and valid credentials are present.

• Confirm DELTA_MCP_MODE=trade is in the env block and you fully restarted the client (the tool list changes only at launch).
• Confirm DELTA_API_KEY / DELTA_API_SECRET are set — trade mode without credentials still registers nothing.
• Ask the assistant to call get_trading_status; if it's missing, trade mode is off.

A trading tool returns a permission or IP error

• The API key must have Trading permission enabled in Delta API management. A Read Data key cannot trade even with DELTA_MCP_MODE=trade.
• The requesting IP must be whitelisted on the key. The error context names the IP Delta saw — add it to the key's whitelist.
• After a mutation signature error, don't retry blindly: mutations are never auto-retried because the first attempt may have reached the exchange. Check get_open_orders / get_positions before re-sending.

Where is the audit log?

In trade mode every mutation is written to ~/.delta-exchange-mcp/audit/. Ask the assistant "where is the audit log?" — get_trading_status returns the exact path. Disable it with DELTA_MCP_AUDIT=off or relocate with DELTA_MCP_AUDIT_FILE.

Rate limits / intermittent failures

Delta's API is rate-limited. Rapid-fire prompts across many symbols can trip limits; space requests out or narrow the query. Transient errors usually clear on retry.

Updating the server

uvx caches the package. To force the latest version:

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

Still stuck?

Open an issue on github.com/delta-exchange/delta-exchange-mcp with your client, OS, and the error from the logs.