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, runcodex 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 forapixo-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/mcpand the transport is Streamable HTTP. -
Confirm that
apixo-mcpis 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:
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 withcodex : 无法将"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.

Confirm Codex is installed (Windows)
Run the executable by full path. A per-user Codex installation commonly uses%LOCALAPPDATA%\OpenAI\Codex\bin:

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


Migrating from the old local package
If your client still runs@apixo/mcp-server through npx, that package is no longer the recommended setup.
- Remove its entry from your client’s MCP configuration.
- Add the remote connection by following Installation.
- Update any saved prompts or scripts to use the remote tool names, such as
list_modelsinstead ofapixo_list_models. - 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.