Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Manage your ZRouter AI gateway account: usage, logs, model routers, API keys, budgets, and limits.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://zrouter.si/mcp在终端中运行这条命令
claude mcp add --transport http zrouter https://zrouter.si/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"zrouter": {
"url": "https://zrouter.si/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"zrouter": {
"type": "http",
"url": "https://zrouter.si/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://zrouter.si/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 nexusrun 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.11.7)于29天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Asset Notation
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
Read and maintain an Asset Notation file on disk: net worth, holdings, valuations, CSV import.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.