Static Client ID (no Dynamic Client Registration)
Aries MCP does not use Dynamic Client Registration (DCR). Per the MCP Authorization specification, when an authorization server does not support DCR, you use a static Client ID: you register an OAuth client yourself (in Client Center), get your Client ID, then provide that Client ID in your IDE or app config. Each platform has a simple way to set it (e.g. inmcp.json or in a prompt when you connect). Once the static Client ID is set, the usual OAuth flow (sign in, grant access) runs in the browser.
Common steps (all platforms)
The same Client Center and OAuth flow apply to every platform. Do this once; then follow your platform-specific guide below.Step 1: Create an OAuth client in Client Center (get your static Client ID)
You need an OAuth2 client with the OAuth redirect URI set at the time of API key generation. This redirect URI is used for authentication only — Aries sends you back to the MCP gateway after you approve on the OAuth screen. Where to add your client and redirect URI: Client Center → API- Open Client Center and go to the API section.
- Click Generate Key.
- Fill in:
- Client name — e.g. “Claude MCP” or “Cursor MCP”.
- Redirect URI — use this exact value (same for every platform). Set this when you generate the key; it is for authentication only:
- Scopes — choose what you want the AI to do (e.g. read account, place orders, market data). See OAuth2 Guide — Scopes.
- Save and copy your Client ID. Client ID is required — the MCP connection will not work without it. You will use only your Client ID in the platform connector.
Step 2: OAuth flow (same as normal API)
The authentication flow for MCP is the same as for the rest of the Aries API. When you connect from your platform (Claude, etc.), follow these steps:- Your platform opens the OAuth flow — After you add the connector or MCP server with your Client ID, the platform will send you to Aries to sign in and approve (using the same authorize URL and scopes as the rest of the API).
- Sign in on the Aries OAuth screen — Your browser (or in-app browser) opens the Aries OAuth screen (sign-in and consent page). Enter your Aries email and password and sign in.
-
Grant access — important, first time only — On the same screen you will see the permission / consent request (what the app is allowed to do). You must click Allow or Approve to grant access.
- This permission grant screen is shown only the first time you connect. If you close the page or navigate away without clicking Allow, it may not appear again for that connector.
- To avoid missing it: complete sign-in, read the permissions, then click Allow or Approve before closing the tab or window.
-
Callback — After you approve, Aries redirects to
https://mcp.aries.com/auth/callbackwith a one-time code. The MCP gateway exchanges that code for tokens. You’ll see a success message or return to your platform. - Connected — Your platform can then call the Aries API within the scopes you granted. No extra steps are required on your side beyond this OAuth flow (same as in the Quick Start or OAuth2 Guide).
Connect by platform
Our MCP server is available on multiple platforms. Choose your platform for step-by-step setup (Client ID, where to add it, and how to complete the OAuth screen).Claude.ai (Web)
Use Claude in the browser at claude.ai. Add custom connector with MCP URL and Client ID →
Claude Desktop
Trade and pull market data inside Claude. Install in Claude Desktop →
Claude Mobile
Trade hands-free using voice or text from your phone. Install in Claude Mobile →
Claude Code
Add Aries MCP server via CLI. HTTP transport and /mcp to authenticate →
Cursor
Add Aries MCP server in Cursor. Tools & MCP → streamable HTTP with MCP URL →
ChatGPT
Create app in ChatGPT (developer mode), OAuth + User-Defined Client ID, then Connect →
Perplexity
Account settings → Connectors → Custom connector (Remote). MCP URL + OAuth Client ID, then authorize →
Microsoft Copilot Studio
Tools → Add tool → MCP. Manual OAuth 2.0 with Aries URLs, Client ID, then create connection →
Quick reference
| Item | Value |
|---|---|
| Where to add client & redirect URI | Client Center → API |
| OAuth redirect URI (MCP) | https://mcp.aries.com/auth/callback |
| MCP server URL | https://mcp.aries.com/mcp (use in Claude Code, Cursor, etc.) |
| Client ID | Cursor: auth.CLIENT_ID in mcp.json. ChatGPT / Perplexity: In connector or app settings. Microsoft Copilot Studio: In Manual OAuth form; redirect URI comes from Copilot Studio (use it in Client Center). |
| Auth flow | Same as OAuth2 Guide (authorize → OAuth screen and consent → callback → token exchange) |
| MCP auth model | Static Client ID (no DCR); register in Client Center, then set Client ID in your platform. |
Next steps
Claude.ai (Web)
Step-by-step: add custom connector at claude.ai with MCP URL and Client ID.
Claude Desktop
Step-by-step: get Client ID, add MCP server in Claude Desktop, complete OAuth screen.
Claude Mobile
Step-by-step: connect Claude on your phone to Aries via MCP.
Claude Code
Step-by-step: add Aries MCP via CLI, then /mcp to authenticate.
Cursor
Step-by-step: add Aries MCP server in Cursor (Tools & MCP).
ChatGPT
Step-by-step: create app in ChatGPT, User-Defined OAuth, add Client ID, then Connect.
Perplexity
Step-by-step: connect Perplexity to Aries via MCP.
Microsoft Copilot Studio
Step-by-step: add MCP tool in Copilot Studio, Manual OAuth 2.0, then create connection.
OAuth2 Guide
Scopes, security, and troubleshooting.