Skip to main content
For the remote connection, add apixo-mcp at https://mcp.apixo.ai/mcp using Streamable HTTP, then sign in through apixo.ai browser OAuth. You do not need Node.js or an API key for this flow.

Browser OAuth did not open or finish

  • Start sign-in from your client’s MCP connection controls. In Claude Code, use /mcp; in Cursor, use Cursor Settings → MCP. In Codex versions with the login command, run codex mcp login apixo-mcp.
  • If the client displays a sign-in link, open it in your browser, sign in to APIXO, and approve the connection.
  • Return to the client after the browser confirms completion. Refresh its MCP connections if needed.
  • If sign-in expires or fails, start the client’s OAuth flow again.

The remote connection returns 401

Sign in again through the client’s OAuth controls for apixo-mcp. Confirm that the browser is signed in to the intended APIXO account. Do not paste an API key into the conversation to repair a remote OAuth connection.

No tools listed in the client

  • Confirm that the URL is exactly https://mcp.apixo.ai/mcp and the transport is Streamable HTTP.
  • Confirm that apixo-mcp is enabled and signed in. Your client must support remote MCP and OAuth.
  • Refresh the connection or restart the client after changing its configuration.
  • Inspect the client’s connection logs for network or authentication errors. Check that your network can reach the remote endpoint.
  • For Codex, inspect the registration with:
Once connected, verify with list_models, get_model_schema, and get_profile. These are free, read-only tools. See Installation.

A Chat or LLM model is missing

The MCP catalog contains generation task models and excludes Chat/LLM gateways. Use the Chat API or compatible SDKs, changing the base URL and configuring an APIXO API key in your application.

CLI not found on PATH

Symptom. Step 1 of Installation fails with codex : 无法将"codex"项识别为 cmdlet… on Windows, or command not found: codex (or claude) on macOS or Linux. The steps below use Codex on Windows as the example. For Claude Code, find its install folder, add it to PATH, and open a fresh terminal. Codex is not found in PowerShell

Confirm Codex is installed (Windows)

Run the executable by full path. A per-user Codex installation commonly uses %LOCALAPPDATA%\OpenAI\Codex\bin:
If this prints a version number, the binary is installed and only the PATH entry is missing. Check Codex by full path

Add the Codex bin folder to your user PATH (Windows)

Add the Codex bin folder to PATH Close the terminal, open a new one, and verify:
Verify Codex from a new terminal Then repeat Step 1.

Migrating from the old local package

If your client still runs @apixo/mcp-server through npx, that package is no longer the recommended setup.
  1. Remove its entry from your client’s MCP configuration.
  2. Add the remote connection by following Installation.
  3. Update any saved prompts or scripts to use the remote tool names, such as list_models instead of apixo_list_models.
  4. If you no longer need its key, revoke the MCP device key in Dashboard → API Keys. Deleting a local credential file does not revoke the key.
The remote connection does not include batch tools. Use the Batch API for batch workflows.

Still stuck?

Re-read Installation and confirm you can sign in to APIXO in your browser. Contact APIXO support with your client name, version, and relevant connection errors. Never include API keys, OAuth tokens, or credential file contents.