app.nz is now an MCP server
Point Claude, Codex, or any MCP client at app.nz/mcp and your agent can run every gateway model — chat, images, embeddings — plus search the MCP directory, through one connector and one API key.
Last week we shipped a searchable directory of MCP servers. This week app.nz became one.
app.nz is now itself a Model Context Protocol server. Point Claude, Codex, Cursor, or any MCP client at a single endpoint and your agent can run every model on our gateway — chat across OpenAI, Anthropic, Google and xAI, generate images, create embeddings — and search the MCP directory, all through one connector with one API key.
The endpoint
POST https://app.nz/mcpIt speaks JSON-RPC 2.0 over Streamable HTTP, stateless — the modern remote-MCP transport. /v1/mcp is an alias, and a GET on the same path serves the human docs page. Authenticate with a Bearer key from app.nz/api-keys — the same key works for the OpenAI-compatible API.
Wiring it up
In Claude Code, one line:
claude mcp add --transport http app-nz https://app.nz/mcp \
--header "Authorization: Bearer YOUR_APP_NZ_API_KEY"For any client that reads a JSON config (Claude Desktop, Cursor, Windsurf):
{
"mcpServers": {
"app-nz": {
"type": "http",
"url": "https://app.nz/mcp",
"headers": { "Authorization": "Bearer YOUR_APP_NZ_API_KEY" }
}
}
}The tools
| Tool | What it does |
|---|---|
chat | Chat completion against any model id, or app/auto to let us route |
list_models | Discover routable models with provider, modality and context window |
generate_image | Text-to-image, returns hosted URLs |
embed | Embedding vectors for text |
search_mcp_servers | Semantic search over the app.nz MCP directory |
chat is the interesting one: pass app/auto and we classify the prompt and pick a tier for you, then walk a fallback chain if a provider is down — so your agent gets a working model without you hard-coding one.
How it's built
The MCP server doesn't reimplement anything. Each tool call is dispatched in-process to the same gateway handlers that serve /v1/chat/completions, /v1/images/generations and /v1/embeddings, through a sub-context that inherits your auth. That means model routing, bring-your-own-key selection, fallback, metering and billing are all reused unchanged — the MCP surface and the REST surface can never drift apart, because they're the same code. search_mcp_servers runs on the same local embedding index that powers the directory's search box.
That single abstraction is the whole point of MCP: one Gmail server works in Claude, Codex, and Cursor without per-app glue. Now the same is true for an entire model gateway. Get a key at app.nz/api-keys, and if you want somewhere to run the agents that use it, that's what the rest of app.nz is for — the cloud coding agent, schedulers, and instant deploys.