Remote MCP

Lets hosted AI clients — ChatGPT, Claude.ai, Claude mobile — talk to your OpenAlgo install over the internet so you can ask them to fetch quotes, summarise positions, or place orders in plain English.

Local stdio MCP (Claude Desktop / Cursor / Windsurf on the same machine as your install) keeps working unchanged. Remote MCP is a parallel, opt-in transport that shares the same 40 tools but reaches them over HTTPS.

You want to...	Use
Trade from your laptop using Claude Desktop, Cursor, or Windsurf	Local stdio (MCP setup guide)
Trade from ChatGPT.com, Claude.ai, or the Claude mobile app	Remote MCP (this guide)
Both	Enable both — they don't interfere

---

What you need

1. OpenAlgo on your own domain with HTTPS. Dashboard reachable at https://yourdomain.com, login + broker auth + orders all working through the web UI. If you're not there yet, start with one of the install scripts: install/install.sh, install/install-multi.sh, install/install-docker.sh, or install/install-docker-multi-custom-ssl.sh.

2. OpenAlgo 2.0.1.0 or later. Footer of the dashboard shows the version, or curl https://yourdomain.com/api/v1/openalgo-version. On older builds run install/update.sh first.

3. An OpenAlgo API key. Generate one at Profile → API Keys. The MCP server uses it server-side; hosted clients never see it — they get OAuth tokens instead.

4. A paid AI plan. ChatGPT Plus / Team / Enterprise, or Claude Pro / Team / Enterprise. Custom MCP servers aren't on the free tiers.

---

Turn it on

Native install (install.sh)

The installer asks at run time whether to enable Remote MCP. If you said yes, it's already on at https://yourdomain.com/mcp — skip to Connecting.

If you said no and want to flip it now, edit /var/python/openalgo/.env:

MCP_HTTP_ENABLED = 'True'
MCP_PUBLIC_URL = 'https://yourdomain.com'

Then sudo systemctl restart openalgo.

Multi-domain native (install-multi.sh)

Edit the per-deploy .env (typically /var/python/openalgo-flask/<deploy-name>/.env) with the same two keys, then sudo systemctl restart openalgo-<deploy-name>.

Docker (install-docker.sh / install-docker-multi-custom-ssl.sh)

cd /path/to/openalgo
sudo ./install/enable-remote-mcp-docker.sh

The helper picks the stack (or asks if you have several), backs up the bind-mounted .env, sets the keys, restarts the container, and probes the OAuth + healthz endpoints. Re-run for each instance.

Defaults the install applies

Key	Default	Effect
MCP_HTTP_ENABLED	True	Master switch
MCP_PUBLIC_URL	Your dashboard URL	Issuer for OAuth tokens
MCP_OAUTH_REQUIRE_APPROVAL	True	New clients land pending until you approve
MCP_OAUTH_WRITE_SCOPE_ENABLED	False	Read-only by default — order placement off until you opt in
MCP_HTTP_CORS_ORIGINS	https://claude.ai,https://chatgpt.com	Browsers that can complete OAuth

Read-only is the safe starting posture. Flip MCP_OAUTH_WRITE_SCOPE_ENABLED=True later, after you've watched a few read-only sessions in the audit log and decided you want order placement from AI clients.

---

Connecting & using ChatGPT and Claude

Once it's enabled, your MCP URL is:

https://yourdomain.com/mcp

The first connect is a six-step dance the AI client does mostly automatically. The one human step is approving the new client at /admin/remote-mcp — your server holds it there until you say so, which is what stops random people from registering against your domain.

---

Adding OpenAlgo to ChatGPT

Heads up — ChatGPT recently renamed Connectors → Apps. Same feature, new menu name. The in-chat menu still says Connectors, so don't be confused.

Step 1 — Open Apps settings

1. Avatar (bottom left) → Settings

2. Sidebar → Apps

3. Top right → Add more → opens New App BETA

Step 2 — Fill in the form

Field	Value
Name	OpenAlgo
Description	OpenAlgo trading server (optional)
MCP Server URL	https://yourdomain.com/mcp
Authentication	OAuth

Step 3 — Advanced OAuth settings

Expand Advanced OAuth settings → Registration method → Dynamic Client Registration (DCR).

The notice "CIMD is unavailable…" is expected — OpenAlgo advertises DCR. DCR is the right pick.

Default scopes ChatGPT requests are read:market read:account. Add write:orders only if you've turned MCP_OAUTH_WRITE_SCOPE_ENABLED=True on the server and you want this connector to place orders.

Step 4 — Acknowledge and create

Tick "I understand and want to continue" under the orange warning, then Create.

Step 5 — Expected error

ChatGPT will show:

OAuth authorization failed: unauthorized_client

This is normal. Your server saw the registration but is holding it until you approve. Don't dismiss the modal.

Step 6 — Approve in OpenAlgo

1. New tab → https://yourdomain.com/admin/remote-mcp

2. Sign in (TOTP if MCP 2FA is on)

3. Pending approvals → verify name + timestamp match → Approve

Step 7 — Complete OAuth

1. Back in ChatGPT → Reconnect

2. A tab pops to https://yourdomain.com/oauth/authorize?...

3. Sign in if needed → consent screen lists scopes (verify the redirect URI is a chatgpt.com URL) → Authorize

4. App moves from Drafts to Enabled

Step 8 — Use it

In any new chat, click + below the message box → Connectors → toggle OpenAlgo ON.

Try:

"Using OpenAlgo, give me the LTP of RELIANCE on NSE."

ChatGPT calls get_quote and shows the price. With read:account granted, also try:

"What's my account balance and current open positions?"

What works on ChatGPT

• All read-only tools work cleanly: quotes, depth, holdings, positions, funds, history, orderbook

• modify_order, cancel_order, cancel_all_orders usually go through

• place_order is often blocked by ChatGPT's own safety policy even when write:orders was granted. If you need order placement from a hosted client, use Claude.ai

Useful ChatGPT prompts

• "Get me the bid-ask spread for INFY and HDFCBANK"

• "Summarise my holdings and tell me which are in profit"

• "Pull 1-day candles for SBIN for the last 30 days and tell me the trend"

• "List my orders from today and show fills vs rejects"

---

Adding OpenAlgo to Claude.ai

Step 1 — Connectors page

claude.ai → name (bottom left) → Settings → Connectors.

Step 2 — Add custom

Top right + → Add custom connector.

Step 3 — Fill in

Field	Value
Name	OpenAlgo
Remote MCP server URL	https://yourdomain.com/mcp

Leave Advanced settings alone — OAuth is detected automatically. Click Add.

Step 4 — Expected error

Same as ChatGPT — first attempt fails with a pending-approval error. Keep the page open.

Step 5 — Approve in OpenAlgo

https://yourdomain.com/admin/remote-mcp → Pending approvals → Approve.

Step 6 — Complete OAuth

Back in claude.ai → Connect on the connector card → sign in to OpenAlgo (+ TOTP if on) → consent screen (verify redirect URI is claude.ai) → Authorize. Card switches to Disconnect when you're live.

Step 7 — Tool permissions

Click your OpenAlgo connector to expand permissions:

Group	Recommendation
Interactive tools (place_order, modify_order, cancel_order, ...)	Ask me at first; Always allow once you trust the prompts
Read-only tools	Always allow
App-only tools	Always allow

You can override individual tools — e.g. Always allow most things but force Ask me for cancel_all_orders.

Step 8 — Use it

In any chat, click the Tools icon below the message box → toggle OpenAlgo on.

"Show me the current LTP of NIFTY 50 and a quick view of my open positions."

Claude shows expandable tool-call cards. Ask me tools surface a permission prompt with Allow once / Always allow / Deny.

What works on Claude.ai

• All read-only tools work

• All write tools work — place_order, modify_order, cancel_order, cancel_all_orders

• The same OAuth tokens work in the Claude iOS / Android apps — chat-trade from your phone, no extra setup

Recommended posture for write tools

• Start in Sandbox / Analyzer mode (/analyzer) and dry-run prompts before turning live trading on

• Keep MCP 2FA on — every fresh authorization demands a TOTP code

• Set a tight MCP_RATE_LIMIT_WRITE (e.g. 5 per minute) so a runaway model can't fire a flurry of orders before you intervene

• Tail log/mcp.jsonl while testing — every call recorded with timestamp, scope, outcome, latency

• Keep the Kill switch at /admin/remote-mcp one click away

Useful Claude prompts

• "Place a limit BUY for 1 share of TCS at ₹3500 in CNC product on NSE"

• "Modify my last open INFY order — change the quantity to 5"

• "Cancel all my open orders"

• "What was my P&L today?"

For more example prompts per tool, see the Tool References — the same prompts work on Remote MCP.

---

Switching scopes after connecting

Already connected with read:market read:account and want to add write:orders?

1. Set MCP_OAUTH_WRITE_SCOPE_ENABLED=True in .env and restart

2. Disconnect the connector / app in ChatGPT or Claude

3. Re-add it with the broader scope set

4. Re-approve at /admin/remote-mcp

OAuth doesn't let an existing token widen its scope — re-consent is required. By design.

---

Daily operations

/admin/remote-mcp

Section	What it's for
Pending approvals	New clients land here. Approve only ones you recognise — the name is set by the hosted client itself
Approved clients	Currently authorised. Each row shows last-used time
Revoked clients	Historical — cannot re-authorize without admin re-approval
MCP tool call audit	Every tool call: timestamp, client, tool, scope, outcome, latency. Filter by tool or outcome
Kill switch	One click revokes every refresh token across every approved client. Use it the moment something looks wrong

Audit log

Same data as the admin page, written to log/mcp.jsonl as JSON Lines. Tail with:

tail -f log/mcp.jsonl

Tool arguments are hashed, not stored verbatim — the log itself is not a data leak.

2FA enforcement

Profile → TOTP → 2FA Enforcement lets you gate three independent purposes:

Purpose	What it gates
Dashboard sign-in	TOTP after password on every login
Remote MCP authorization	Fresh TOTP at /oauth/authorize for every write:orders grant
Password reset	Forces TOTP path (no email fallback)

All three default off so existing installs see no change. Saving requires a fresh TOTP code in the same request — proves you have authenticator access for both enabling and disabling.

---

Configuration reference

All keys live in .env (native) or the bind-mounted .env (Docker). The first five are set by the installer.

Key	Default	Purpose
MCP_HTTP_ENABLED	False	Master switch
MCP_PUBLIC_URL	required when enabled	Public HTTPS origin advertised in OAuth metadata
MCP_OAUTH_REQUIRE_APPROVAL	True	New clients land pending until admin approves
MCP_OAUTH_WRITE_SCOPE_ENABLED	False	Whether write:orders is grantable at all
MCP_HTTP_CORS_ORIGINS	https://claude.ai,https://chatgpt.com	Browser allowlist
MCP_HTTP_IP_ALLOWLIST	empty	Optional IP / CIDR allowlist on /mcp
MCP_OAUTH_ACCESS_TTL	900	Access-token TTL in seconds (max 3600)
MCP_OAUTH_REFRESH_TTL	2592000	Refresh-token TTL in seconds (30 days)
MCP_OAUTH_CODE_TTL	60	Authorization-code TTL (max 300)
MCP_RATE_LIMIT_READ	60 per minute	Per-token cap for read scopes
MCP_RATE_LIMIT_WRITE	50 per minute	Per-token cap for write:orders
MCP_LOOPBACK_URL	inherits HOST_SERVER	Override only for unusual topologies
MCP_OAUTH_KEYS_DIR	keys	Directory for RS256 signing keys

---

Security model

The defenses, in plain order:

1. Approval gate — random clients can register but cannot complete OAuth until you approve them at /admin/remote-mcp

2. Read-only by default — write:orders is invisible in OAuth discovery until you flip MCP_OAUTH_WRITE_SCOPE_ENABLED=True

3. Short access tokens — 15-minute TTL caps the damage window if a token is stolen

4. Rate limits — per-token, separately for reads and writes

5. PKCE + JWT — all the standard OAuth 2.1 hardening (S256-only, exact redirect_uri, refresh token rotation with reuse detection)

6. Kill switch — one click revokes everything

The blast radius is real. A stolen access token can place orders the broker accepts — they originate from your registered server IP. The 15-minute TTL caps damage; the kill switch is your panic button. Never combine MCP_OAUTH_WRITE_SCOPE_ENABLED=True with MCP_OAUTH_REQUIRE_APPROVAL=False — that lets any internet client register, auto-approve, and start placing orders.

For the full threat model and per-defense rationale, see docs/prd/remote-mcp.md.

---

Troubleshooting

Symptom	Cause	Fix
unauthorized_client after Create / Add	DCR client not approved yet	Approve at /admin/remote-mcp
invalid_client on retry	Client revoked or DB reset; old client_id cached	Disconnect + re-add to force fresh DCR
"Server doesn't implement OAuth"	Old build	Update to 2.0.1.0+
"CIMD is unavailable" in ChatGPT	OpenAlgo advertises DCR, not CIMD	Expected — pick DCR
Tools missing from chat	Connector not toggled on for that chat	+ menu (ChatGPT) or Tools menu (Claude)
bad_arguments on a tool call	Hosted client guessed parameter names	Update OpenAlgo (newer builds expose strict tool schemas)
Sudden 401 on every call	Refresh token expired or kill switch fired	Reconnect on the connector
place_order blocked on ChatGPT	OpenAI's safety policy	Use Claude.ai for order placement
"Failed to connect to the server" on tool calls	Loopback misconfigured	Confirm HOST_SERVER in .env matches your dashboard URL; restart
Tokens issued but /mcp returns 401	MCP_PUBLIC_URL doesn't match the URL the client uses	Make them exactly equal — https://example.com ≠ https://www.example.com
Form submit blocked by CSP	Old build	Update to 2.0.1.0+
Container won't restart after enabler	Bad .env change	Run the rollback one-liner the enabler printed; restart; check log/errors.jsonl

---

Subdomain mode (advanced)

If you want MCP on a separate hostname (e.g. mcp.yourdomain.com) so its cookies, CORS, and TLS lifecycle are isolated from the dashboard, the manual recipe is in install/Remote-MCP-readme.md. Same nginx + certbot pattern as install-docker-multi-custom-ssl.sh. Most users don't need this — same-domain is what the installer automates.

---

Disabling

Native:

sudo sed -i "s|MCP_HTTP_ENABLED.*|MCP_HTTP_ENABLED = 'False'|" /var/python/openalgo/.env
sudo systemctl restart openalgo

(install-multi.sh users: substitute the per-deploy .env and service name.)

Docker:

sudo sed -i "s|MCP_HTTP_ENABLED.*|MCP_HTTP_ENABLED = 'False'|" /opt/openalgo/<domain>/.env
cd /opt/openalgo/<domain> && sudo docker compose restart

OAuth + MCP routes immediately stop responding. Existing tokens hit 404. Local stdio MCP is unaffected — it runs over stdin/stdout and doesn't touch the HTTP transport.

For a softer takedown that keeps Remote MCP enabled but boots every active session: visit /admin/remote-mcp → Kill switch. Hosted clients are forced through a fresh OAuth dance the next time they refresh.

---

Related

• MCP Server Setup Guide — local stdio integration with Claude Desktop / Cursor / Windsurf

• Tool References — every tool with parameters and example prompts (shared across both transports)

• OpenAlgo Symbol Format — how equity / future / option symbols are constructed

• install/Remote-MCP-readme.md — operator-focused install + threat model in the source tree

• docs/prd/remote-mcp.md — full architecture and threat model

---

---