Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Manage your ZRouter AI gateway account: usage, logs, model routers, API keys, budgets, and limits.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://zrouter.si/mcpRun this in your terminal
claude mcp add --transport http zrouter https://zrouter.si/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"zrouter": {
"url": "https://zrouter.si/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"zrouter": {
"type": "http",
"url": "https://zrouter.si/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://zrouter.si/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account nexusrun, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.11.7) reached the registry 29 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Signoff
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
https://zrouter.si/mcp
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.
https://zrouter.si/mcp as a remote MCP server in your client.Clients that support MCP sign-in only need the URL. There is no token to copy or renew.
Settings → Connectors → Add custom connector. Paste https://zrouter.si/mcp, then select Connect and approve access.
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 mcp add --transport http zrouter https://zrouter.si/mcp
Then run /mcp inside Claude Code and choose Authenticate.
This repository is also a Cursor plugin (.cursor-plugin/plugin.json). Or add the server to ~/.cursor/mcp.json:
{
"mcpServers": { "zrouter": { "url": "https://zrouter.si/mcp" } } }
Add the server to .vscode/mcp.json or your user configuration:
{
"servers": { "zrouter": { "type": "http", "url": "https://zrouter.si/mcp" } } }
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.
For scripts and clients without MCP sign-in, use an MCP token.
Send it as a bearer token:
claude mcp add --transport http zrouter https://zrouter.si/mcp \
--header "Authorization: Bearer YOUR_MCP_TOKEN"
{
"mcpServers": { "zrouter": { "url": "https://zrouter.si/mcp", "headers": { "Authorization": "Bearer YOUR_MCP_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.
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.
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.
| Tool | What it does | Type |
|---|---|---|
account_info | The signed-in account and its credit balance | Read-only |
credit_ledger | Credit purchases and charges | Read-only |
| Tool | What it does | Type |
|---|---|---|
usage_summary | Total requests, tokens, and cost for a time window | Read-only |
usage_daily | Usage and cost over time, by day, week, or month | Read-only |
usage_by_model | Usage and cost grouped by model | Read-only |
usage_log | Per-request entries with tokens and cost | Read-only |
Usage tools accept days (default 30), start_date and end_date (YYYY-MM-DD), user_path, model, and provider.
| Tool | What it does | Type |
|---|---|---|
logs_search | Search request logs by status code, error type, or text | Read-only |
logs_get | Full detail of one log entry (log_id from logs_search) | Read-only |
logs_stats | Request counts, error rates, and latency | Read-only |
| Tool | What it does | Type |
|---|---|---|
models_list | Models this account can use | Read-only |
virtual_models_list | Your routers, the routing strategies, and your model name prefix | Read-only |
virtual_models_upsert | Create or update a router: up to 32 targets, weights, and a strategy such as round_robin or super_intelligence | Write |
virtual_models_delete | Delete a router | Destructive |
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.
| Tool | What it does | Type |
|---|---|---|
api_keys_list | List keys. Secrets are never returned. | Read-only |
api_keys_create | Create a key. The secret is returned once. | Write |
api_keys_delete | Delete a key. Requests using it stop working immediately. | Destructive |
| Tool | What it does | Type |
|---|---|---|
budgets_list | Budgets with current spend | Read-only |
budgets_upsert | Create or update a USD spend limit (hourly, daily, weekly, or monthly) | Write |
budgets_delete | Delete a budget | Destructive |
budgets_reset | Reset one budget's current spend to zero | Destructive |
| Tool | What it does | Type |
|---|---|---|
rate_limits_list | Rate limits with current counters | Read-only |
rate_limits_upsert | Create or update a request or token limit per minute, hour, or day | Write |
rate_limits_delete | Delete a rate limit | Destructive |
rate_limits_reset | Reset one rate limit's counters | Destructive |
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.
api_keys_create result, and so in your assistant's conversation history. Treat that history accordingly, or create keys in the dashboard.For client developers. The server follows the MCP authorization specification.
| MCP endpoint | https://zrouter.si/mcp (POST, Streamable HTTP, stateless, JSON responses) |
| Protected resource metadata | https://zrouter.si/.well-known/oauth-protected-resource/mcp (RFC 9728) |
| Authorization server metadata | https://zrouter.si/.well-known/oauth-authorization-server (RFC 8414) |
| Authorization endpoint | https://zrouter.si/oauth/authorize |
| Token endpoint | https://zrouter.si/oauth/token |
| Dynamic client registration | https://zrouter.si/oauth/register (RFC 7591) |
| Grant types | authorization_code, refresh_token |
| PKCE | Required, S256 |
| Client authentication | none (public clients) |
| Scope | account |
A request without a valid token gets 401 with:
WWW-Authenticate: Bearer resource_metadata="https://zrouter.si/.well-known/oauth-protected-resource/mcp", scope="account"
Quick check with an MCP token:
curl -s https://zrouter.si/mcp \
-H "Authorization: Bearer YOUR_MCP_TOKEN" \ -H "Content-Type: application/json" \ -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
| Problem | Fix |
|---|---|
401 with invalid_token | The token expired (MCP tokens last 30 days) or was revoked, or an account API key was sent instead of an MCP token. Sign in again or create a new MCP token. |
| The client cannot sign in | Make sure it supports remote MCP with OAuth. Otherwise use an MCP token. |
| A tool reports a validation error | The tool returns the same message as the dashboard. Fix the argument it names and retry. |
| The assistant uses the wrong account | Disconnect the app under Connected apps and sign in again with the right account. |
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.
The contents of this directory are available under the MIT License.