Skip to main content
APIXO MCP is a local Model Context Protocol server that plugs APIXO into any MCP-compatible AI client. It exposes APIXO’s model catalog and parameter schemas to your agent, so when you ask “add APIXO to my project”, the agent can write correct integration code without you reading docs or guessing field names. It works in any client that speaks MCP. Common ones:
  • Cursor (config file: ~/.cursor/mcp.json)
  • Claude Code (CLI: claude mcp add ...)
  • Codex CLI (CLI: codex mcp add ...)
  • Claude Desktop, Windsurf, Cline, Continue, Zed, and other MCP clients (any client that loads stdio MCP servers from JSON config)
The server ships as the @apixo/mcp-server npm package and runs locally on your machine. For normal local use, connect it through the browser: install the server, call apixo_setup, sign in and approve the device in the browser, then call apixo_finish_setup. The server keeps the resulting credential in its private local credential store and never returns it in a tool response.
Browser setup is the default path. APIXO_API_KEY is an advanced override for CI, a browserless environment, or local development debugging—not a prerequisite for a normal desktop installation.

​
What you can do

Scaffold APIXO into your codebase

Ask your agent to add a model to your project. It reads the model schema through MCP and writes parameter-accurate calls into your existing files.

Discover models and schemas

Your agent can browse APIXO’s model catalog and fetch any model’s full input schema on demand—no copy-pasting from the docs.

Run and inspect tasks from chat

The same tools also let the agent submit ad-hoc generation tasks, inspect results, and check your account balance from the conversation.
Most of the value is in the first capability: APIXO has many models with very different input parameters, and MCP gives the agent a reliable source of truth so the code it writes against APIXO compiles and runs correctly.

​
Tools exposed by the server

@apixo/mcp-server registers the following tools. Most clients show them under an apixo namespace. The server also exposes published admin-contract and MCP-management tools to callers with separately configured permissions. They are not required for model discovery, generation, or the normal browser setup flow.
After setup, apixo_list_models + apixo_get_model_schema + apixo_generate_task + apixo_get_task_status cover the full Generation task flow described in How APIXO Works. Use apixo_get_batch_integration_guide before building a batch flow.

​
When to use MCP

​
Get started

Install and connect APIXO MCP

Install the server, approve it in the browser, and start using APIXO tools.

Batch Integration

Learn the batch and signed-webhook lifecycle before calling the batch tools.

Troubleshooting

Fix browser setup, codex PATH, npx, and client-tool connection issues.