
ZRouter
io.github.nexusrunv1.11.7Updated Oct 9, 2026
Manage your ZRouter AI gateway account: usage, logs, model routers, API keys, budgets, and limits.
Overview
Lets an assistant manage a ZRouter AI gateway account: usage and spend, request logs, model routers, API keys, budgets, and rate limits.
- What it does
- A hosted remote MCP server for the management side of a ZRouter account. It exposes 24 tools covering account info and credit ledger, usage summaries and per-request logs, log search and error/latency stats, model and virtual router listing and editing, API key creation and deletion, and budget and rate limit management. Read-only tools are annotated as such, and deletes and resets are marked destructive so confirming clients ask first.
- When to use it
- Useful when you want to check spend, investigate failed or rate-limited requests, or adjust routing, keys, budgets, and limits in plain language instead of the dashboard. It is account administration only; it does not change which model your assistant uses or send model requests.
- Requirements
- Nothing to install: a remote Streamable HTTP endpoint. Sign-in is OAuth 2.1 with PKCE and dynamic client registration, or a bearer MCP token created in the dashboard under CLI and MCP access. A ZRouter account is required. Clients without MCP sign-in need the Authorization header with the MCP token.
Installation
In SourceWeft
- Open ZRouter in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"zrouter": {
"type": "http",
"url": "https://zrouter.si/mcp"
}
}
}README
ZRouter MCP Server
Manage your ZRouter account from any AI assistant. Check spend, search request logs, create virtual model routers, issue API keys, and set budgets and rate limits in plain language.
ZRouter is the Super Intelligence Router: one OpenAI-compatible API key for chat, images, audio, and video, routed to the right model and provider. This MCP server is the management side of your account. It runs as a hosted remote server, so there is nothing to install.
- Transport: Streamable HTTP
- Sign-in: OAuth 2.1 with PKCE and dynamic client registration, or a bearer token
- Scope: your own account only, with the same rules as the dashboard
- Tools: 24 (14 read-only, 4 write, 6 marked destructive)
Contents
- Quick start
- Connect a client
- Use a token instead of sign-in
- What you can ask
- Tools
- Security
- Authentication details
- Troubleshooting
- FAQ
- Links
Quick start
- Create a free account at zrouter.si.
- Add
https://zrouter.si/mcpas a remote MCP server in your client. - Approve access on the ZRouter page that opens.
- Ask: "How much did I spend this week, by model?"
Clients that support MCP sign-in only need the URL. There is no token to copy or renew.
Connect a client
Claude (claude.ai and Claude Desktop)
Settings → Connectors → Add custom connector. Paste https://zrouter.si/mcp, then select Connect and approve access.
ChatGPT
Settings → Apps & Connectors → create a connector with the URL https://zrouter.si/mcp and OAuth authentication. Custom connectors may require developer mode, depending on your plan.
Claude Code
Then run /mcp inside Claude Code and choose Authenticate.
Cursor
This repository is also a Cursor plugin (.cursor-plugin/plugin.json). Or add the server to ~/.cursor/mcp.json:
VS Code
Add the server to .vscode/mcp.json or your user configuration:
Other clients
Add a remote MCP server with the URL https://zrouter.si/mcp and the Streamable HTTP transport. Choose OAuth sign-in when the client asks.
Client configuration formats change between versions. If a snippet above does not match your client, follow its own MCP documentation and use the same URL.
Use a token instead of sign-in
For scripts and clients without MCP sign-in, use an MCP token.
- Open CLI and MCP access in your ZRouter dashboard.
- Name the token after your client and select Create MCP token.
- Copy it right away. It is shown once and expires after 30 days.
Send it as a bearer token:
Use an MCP token, not an account API key. API keys only send model requests and cannot manage your account, so a leaked API key cannot create keys or change budgets. Keep MCP tokens out of shared repository configuration, and revoke tokens you no longer use from the same dashboard page.
What you can ask
- "How much did I spend this week, by model?"
- "Show the requests that failed with 429 today."
- "Why did my last request to the support bot fail?"
- "Create a router called support-bot that splits traffic between two models."
- "Route easy prompts to a cheap model and hard ones to my strongest model."
- "Create an API key for staging and cap my spend at $10 a day."
- "Limit the staging user path to 60 requests a minute."
Connecting this server does not change your assistant's own model provider. To send model requests through ZRouter, set up an API key with one of the integration guides.
Tools
Every tool runs inside the authenticated account. Read-only tools are annotated readOnlyHint. Deletes and resets are annotated destructiveHint, so clients that confirm risky actions ask you first.
Account
Usage
Usage tools accept days (default 30), start_date and end_date (YYYY-MM-DD), user_path, model, and provider.
Logs
Models and routers
A router is a stable model name your app calls. The super_intelligence strategy scores each request by difficulty and sends it to simple_targets, standard_targets, or complex_targets.
API keys
Budgets
Rate limits
Budgets apply to a user_path or label. Rate limits apply to a user_path, provider, or model. Set per_child to apply a rule separately to each child user path.
Security
- Your account only. Each tool call goes through the same customer API as the dashboard, with your credential, so authentication, account scoping, and validation are identical.
- Separate credentials. MCP access uses OAuth tokens or MCP tokens. Account API keys cannot manage the account.
- Revocable. Disconnect apps under CLI and MCP access → Connected apps, and revoke MCP tokens on the same page.
- Bounded results. A single tool result is capped at 256 KB so a large log page cannot flood your assistant's context.
- Secrets in history. A new API key's secret appears in the
api_keys_createresult, and so in your assistant's conversation history. Treat that history accordingly, or create keys in the dashboard.
Authentication details
For client developers. The server follows the MCP authorization specification.
A request without a valid token gets 401 with:
Quick check with an MCP token:
Troubleshooting
FAQ
Is there anything to install or host?
No. ZRouter hosts the server at https://zrouter.si/mcp.
Does it cost anything? No. Account management through MCP is free. Model requests you send with your API keys draw from your prepaid credit as usual.
Can the assistant reach another account? No. Every tool runs inside the account that signed in.
Does connecting MCP change which model my assistant uses? No. It only adds account management tools.
Can I manage the account from a terminal instead? Yes, with the zctl CLI.
Links
- Website: https://zrouter.si
- MCP guide: https://zrouter.si/docs/mcp
- API guide: https://zrouter.si/docs/api
- Integrations: https://zrouter.si/docs/integrations
- zctl CLI: https://zrouter.si/cli
- Status: https://zrouter.si/status
- Smithery https://smithery.ai/badge/sali/zrouter [smithery badge]
License
The contents of this directory are available under the MIT License.
Source: README.md at commit f02a3b9
Tools
0Version history
1- v1.11.7LatestOct 9, 2026


