Skip to main content

Troubleshooting Exness MCP

Start with three checks​

1
Check the setup

If you installed a plugin, confirm its publisher is Exness. If you connected by URL, use https://api.exness.com/mcp.

2
Check authorization

Sign in to your Exness Personal Area if prompted. Select your accounts and access, choose Authorise, then return to your AI assistant.

3
Check access

Check the Trading accounts selected during authorization. For Partnership, Read-only does not allow tools that change data; choose Full access to use those tools.

Find and connect Exness​

What you seeWhat to do
Exness does not appear in searchOpen the ChatGPT listing or Claude listing directly. Check that your account or workspace allows the plugin.
Claude shows Sign in to addSign in to Claude, then return to the Exness listing.
Codex does not show Exness under Sources → Use pluginsCheck that Exness is installed in the account you use for Codex. In a managed workspace, ask your administrator whether the plugin is available to you.
The option to add a custom MCP server or connector is missingCheck your assistant's account and workspace requirements. In a managed workspace, ask your administrator whether custom MCP connections are allowed. See the setup guide for ChatGPT, Codex, or Claude.
A direct MCP connection does not connectCheck that the URL is https://api.exness.com/mcp. In Codex, select Streamable HTTP. Save the connection and complete any Exness authorization step.
You opened the MCP URL in a browser or pasted it into a chatEnter https://api.exness.com/mcp in your assistant's MCP connection settings. Opening the URL or sending it as a chat message does not complete the setup. Follow the connection guide for your assistant.
Your AI assistant or platform cannot complete OAuth authorizationCheck that it supports remote HTTP MCP servers and OAuth authorization. See Other AI assistants and your platform's MCP setup instructions.
Claude stops at Finish connecting a connector?If you started the connection in Claude, select Continue connecting to proceed to Exness.
Exness shows a sign-in page instead of account and access optionsSign in to your Exness Personal Area as usual. You will then see the authorization page. Signing in to ChatGPT or Claude does not replace Exness sign-in.
Exness asks you to authorize accessSelect the Trading accounts you want to use and the Partnership access needed for your tasks, then select Authorise. Installing the plugin alone does not grant access to your account data.
You closed or declined the authorization flowReturn to your assistant and start the connection or authorization again. Complete Exness sign-in and the account and access selection, then return to your assistant.
Exness worked before, but now asks you to authenticate or reconnectYour authorization may have expired or been revoked. Open the Exness connection settings and select Authenticate for a custom MCP server or Reconnect for a plugin, where shown. Sign in to your Exness Personal Area if prompted, then select the Trading accounts and Partnership access you need and authorize the connection again.

Connect from the command line​

What you seeWhat to do
The terminal reports codex: command not found or claude: command not foundInstall the relevant CLI using its official setup instructions. If you just installed it, close and reopen Terminal or PowerShell, then try again. If the command is still not found, check the CLI's setup instructions for making it available in your terminal. Alternatively, use the desktop setup in the Codex or Claude guide.
Exness is listed, but authentication is still requiredIn Codex, run codex mcp login exness. In an interactive Claude Code session, enter /mcp, select exness, and follow the authentication prompt. Complete Exness sign-in and authorization in your browser. A server appearing in the list only confirms that it is configured.
Claude Code does not show the server you addedStart Claude Code in the same project directory where you ran claude mcp add. See the Claude Code setup steps.
The authorization browser window does not open in Claude CodeIf Claude Code provides an authorization URL, open it manually in your browser and follow the terminal prompts. See the Claude Code MCP guide.

Use the tools​

If you authorized Trading access, try asking: “Use Exness to show the account overview for trading account [account number].” Replace [account number] with a Trading account number you selected during authorization. Check that your assistant calls an Exness tool and returns data for that account. A general answer about Exness or its documentation does not confirm that account access works.

What you seeWhat to do
The assistant does not use ExnessAsk it to use Exness for the task. In Codex, select Exness under Sources → Use plugins when available.
A Trading or Partnership tool is missingCheck that the Exness connection is enabled and that you completed authorization with the accounts and access needed for your task. Ask which Exness tools are available. In a managed workspace, check whether your administrator restricts tools. If the tool is still unavailable, check whether your connection provides it.
The connection looks active, but account data is unavailableAsk your assistant to use an Exness tool that reads account data and report the result. A documentation answer alone does not confirm account authorization. If the account tool reports an authorization error, reconnect and complete Exness sign-in.
Data for a specific trading account is missingCheck whether that account was selected during Exness authorization. Reauthorize the connection and include the account if needed.
Partnership data or a supported change is blockedCheck the Partnership access selected during authorization: Read-only for viewing data or Full access for supported changes. Reauthorize with the access you need.
A tool returns an errorCheck the account, dates, and filters you requested. If the error persists, save the tool name and error message for Exness support. For API-specific fields and limits, see the Trading or Partnership guides.
Before repeating a change

If a tool may have changed data but returned an error, check the current state before asking the assistant to run it again.

When contacting support, include the assistant and connection method you used, the step that failed, and the error message. Include the tool name if a tool failed. Do not include passwords, API keys, tokens, or authorization callback URLs.

For setup steps, return to Connect Exness MCP.