Quantplay MCP server
One link connects Claude, ChatGPT or any MCP app to your accounts on 10+ Indian brokers. You sign in with OAuth; there’s no Quantplay API key to copy.
On this page
The Quantplay MCP server connects your AI app to your accounts at 10+ Indian brokers, using one URL.
- Works with ChatGPT, Claude, Grok, Hermes, OpenClaw, Muse, Cursor, Claude Code, Codex and other MCP apps.
- Account reading is free. Orders require your permission and PRO: ₹700 per broker account per month.
- PRO includes risk limits and a static IP. Limits run on Quantplay’s servers.
- No AI tool can change your kill switch.
What it is
MCP is a standard that lets AI apps use tools from another service. Quantplay exposes tools for connected broker accounts, so an assistant can request positions, orders or margins instead of interpreting a screenshot.
Before you start: add your broker
The agent works with the broker accounts you’ve added to Quantplay. Sign up, click Add account, pick your broker and enter its API details. Find your broker’s guide.
What you can do
- Read positions, holdings, orders, margins, live P&L and history.
- Look up option chains, expiries, instruments and market data.
- Place, modify and cancel orders, or square off positions, if you allow trading.
- Set stoploss, target and trailing stoploss, if you allow risk changes.
Authentication and permissions
No Quantplay API key is needed for the connector flow. Add the URL, pick OAuth if asked, then sign in and choose what the agent can do. Viewing is always on; trading and risk changes are off until you allow them.
https:/ / mcp.quantplay.tech/ mcpThere is one connector URL. The approval screen decides which actions are allowed; you do not choose a different server for trading.
| Approval label | What it allows |
|---|---|
| View your accounts | Read account information such as positions, holdings, orders, margins and P&L. |
| Place, modify and cancel orders | Send order actions to the connected broker accounts. |
| Change stoploss, target and trail | Change these account risk settings. |
Keep order and risk changes unticked if you want account answers only. Permission to trade does not give an AI permission to change your kill switch.
What to ask a connected AI
| What you want | Try asking |
|---|---|
| See your portfolio | Show my positions across all accounts and today’s P&L. |
| Check margins | How much free margin do I have left in each account? |
| Check orders | Did my orders fill? Show any rejection reasons. |
| Read the option chain | Show the NIFTY option chain for this expiry around the ATM strike. |
| Place an order | Buy 1 lot of NIFTY 24300 CE on my main account, with the expiry and limit price I specify. |
| Set risk limits | Set stoploss ₹5,000 and target ₹12,000 on my main account. |
| Review holdings | Analyse my holdings. Which positions make up the largest share? |
Begin with a result you can check in the broker app. If you later enable trading, specify the account, instrument, quantity, side, order type and price. Check the order book for the result.
Setup guides
For the broker details you need first, find your broker’s guide. The AI agent guides show the screens for each app.
Claude
- 1Copy the server URL above.
- 2Open Customize → Connectors → Add custom connector, name it Quantplay and paste the URL.
- 3Click Connect. Sign in to Quantplay, choose permissions and approve.
- 4Start a new chat and ask for your Quantplay accounts to check it works.
ChatGPT
ChatGPT Free works. Quantplay was connected on a Free account on 14 November 2026.
- 1Open Add custom MCP server in ChatGPT.
- 2Name it Quantplay, paste the server URL and choose OAuth.
- 3Create the connection, sign in to Quantplay, choose permissions and approve.
- 4Ask ChatGPT for your Quantplay accounts to check the connection.
Claude Code
Add the remote server:
claude mcp add --transport http quantplay https:/ / mcp.quantplay.tech/ mcpOptional: add --scope user for every project, or --scope project to share the server configuration through .mcp.json. Then run /mcp, pick Quantplay and complete authentication. See Claude Code’s MCP documentation.
Codex
For Codex, add the server and then run the login command:
codex mcp add quantplay --url https:/ / mcp.quantplay.tech/ mcpcodex mcp login quantplayApprove the sign-in in your browser. The Codex MCP guide explains remote servers and OAuth authentication.
Cursor
Add this to ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one:
{
"mcpServers": {
"quantplay": {
"url": "https://mcp.quantplay.tech/mcp"
}
}
}Approve the sign-in Cursor opens, then check that Quantplay’s tools appear in its MCP settings. See Cursor’s MCP configuration guide.
Grok
- 1Open Grok’s connectors and add a custom connector.
- 2Paste the same server URL, sign in to Quantplay, choose permissions and approve.
- 3Ask Grok for your Quantplay accounts.
Muse
Add a custom connector in Muse with the same URL. Sign in to Quantplay, choose permissions and approve.
Other MCP clients and scripts
Add the URL as a remote server using Streamable HTTP. Pick OAuth and approve the sign-in. For Hermes, OpenClaw and other clients, see the AI agent guides.
A script without a browser can send an API key from Settings → Developer as an X-Api-Key header. Use OAuth for interactive clients so you can choose their permissions on the approval screen. Keep API keys out of chat messages and shared configuration files.
Risk limits keep running outside the chat
Quantplay’s stoploss, target and trail run on its servers. They auto-exit intraday and F&O positions a few seconds after the limit is crossed. They do not block orders in advance, and an exit can land beyond the limit.
You can edit the kill switch only before 9:15 am or after 3:20 pm IST. An AI cannot edit it at any time, including when you have allowed changes to stoploss, target and trail.
If something’s off
- No accounts appear: check that the broker account has been added in Quantplay and that you completed sign-in.
- The AI cannot place an order: check the permission you approved and the account’s PRO access.
- Tools do not appear: confirm the URL, check configuration JSON for typos and finish the approval screen; restart a desktop client after changing its configuration.
You can also check the MCP server’s health endpoint.
Asked to sign in again and again
Finish the approval step in the Quantplay tab that opens. If it keeps happening, remove the connector, add it again and approve once more.
Using an old URL with a key in it
Replace URLs containing ?QUANTPLAY_API_KEY= with the plain server URL above, then sign in with OAuth.
Disconnecting an agent
In Quantplay, open Settings → AI Integration → Disconnect. The Privacy Policy explains access revocation and what is stored.
Still stuck?
For account help, use the support page or email hello@quantplay.tech. Data handling is covered in the Privacy Policy.




