What you will accomplish
- Add the Quote.Trade remote MCP endpoint to Claude
- Enable the connector for a specific conversation
- Verify read-only tool calls with a safe prompt
- Review order and withdrawal tools before allowing them
Before you begin
- A current Claude Free, Pro, Max, Team, or Enterprise account
- Claude, Cowork, Claude Desktop, or another currently supported Claude client
- The hosted endpoint https://quote.trade/mcp
- No Quote.Trade trading credential for the first read-only test
Confirm the current plan and workspace permissions
Remote custom connectors are currently available on Claude Free, Pro, Max, Team, and Enterprise. Free accounts are limited to one custom connector. Team and Enterprise require an Owner or Primary Owner to add the connector before members can connect it.
Open the remote custom connector flow
For individual plans, use Customize → Connectors and Add custom connector. For Team or Enterprise, the owner first uses Organization settings → Connectors, Add, Custom, then Web. UI labels can change. The hosted Quote.Trade endpoint is not configured through claude_desktop_config.json; that file is a separate local-MCP mechanism.
Add the Quote.Trade endpoint
Enter the official Quote.Trade endpoint and identify it as Quote.Trade.
https://quote.trade/mcpClaude scans the remote server and presents discovered tools or an actionable connection error.
Review tools before enabling use
Enable only the public read-only tools needed for the first test. Before using an order or withdrawal tool, review every request and do not grant permanent approval.
Run a public status or ticker call
Ask Claude to call Quote.Trade status or a public ticker tool and name the tool used. Confirm the result came from the connector rather than general model knowledge.
Claude invokes a public tool and returns a sourced structured result.
Keep live actions behind Quote.Trade limits and approval
Quote.Trade exposes preview and live-action tools. The live tool may require humanApproved and exact approvalText fields, but those fields are friction only. Review each request in the authenticated client and rely on server-side credentials, symbol limits, notional limits, and the user’s actual confirmation for authorization.
Common problems and fixes
Claude cannot reach the connector
Confirm the endpoint is publicly reachable and not blocked for Anthropic cloud traffic. Re-add the connector after verifying the URL.
The connector is missing on Team or Enterprise
An organization Owner must add the custom web connector at the organization level before members can connect.
A tool requests broader access than expected
Cancel the action, disable that tool for the conversation, and review the connector’s scopes and server-side policy.
Answers before you continue
Which Claude plans support remote custom connectors?
Claude currently documents remote custom connectors for Free, Pro, Max, Team, and Enterprise plans. Free users are limited to one custom connector. Check the current official plan documentation because availability can change.
Who adds a connector for Team or Enterprise?
An organization Owner adds the custom web connector at the organization level; members then connect and enable it.
Should I let Claude place orders without confirmation?
No. Keep live trading gated by explicit review, server-side account, symbol, notional, and leverage controls, and the exact Quote.Trade approval requirement.
Can Claude request a Quote.Trade withdrawal?
Yes, when the withdrawal tools are enabled and the required account, credentials, server-side limits, and exact approval are present. The tool can withdraw only to the user’s login wallet, not to an address chosen by the agent.