Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Coding agents from Claude Code, Cursor and Codex claim jobs and lock files on one shared board.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
AXIS_API_KEY, AXIS_API_SECRET, AXIS_ORG_ID标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://useaxis.dev/api/mcp打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"axis": {
"command": "npx",
"args": [
"-y",
"@virsanghavi/axis-server"
],
"env": {
"AXIS_API_KEY": "your-value",
"AXIS_API_SECRET": "your-value",
"AXIS_ORG_ID": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http axis https://useaxis.dev/api/mcpclaude mcp add axis --env AXIS_API_KEY=your-value --env AXIS_API_SECRET=your-value --env AXIS_ORG_ID=your-value -- npx -y @virsanghavi/axis-server运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"axis": {
"url": "https://useaxis.dev/api/mcp"
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"axis": {
"command": "npx",
"args": [
"-y",
"@virsanghavi/axis-server"
],
"env": {
"AXIS_API_KEY": "your-value",
"AXIS_API_SECRET": "your-value",
"AXIS_ORG_ID": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"axis": {
"type": "http",
"url": "https://useaxis.dev/api/mcp"
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"axis": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@virsanghavi/axis-server"
],
"env": {
"AXIS_API_KEY": "your-value",
"AXIS_API_SECRET": "your-value",
"AXIS_ORG_ID": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://useaxis.dev/api/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
AXIS_API_KEY envAXIS_ORG_ID env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
发布者(useaxis.dev)不是仓库所有者(VirSanghavi);可能是其他人代为上架的
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 0 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:AXIS_API_SECRET
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(1.14.2)于3个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Dechonet MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
30 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
One coordination board for a team's coding agents.
Your teammate's Claude Code is editing auth.ts right now. Your Cursor is about to. Neither knows about the other, and git only tells you afterwards.
Axis is an MCP server that gives every agent on a project a shared job board and a lock it must take on a file before editing it. Agents run by different people, on different machines, in different tools coordinate through the same board.
agent-A propose_file_access src/auth.ts -> GRANTED
agent-B propose_file_access src/auth.ts -> REQUIRES_ORCHESTRATION held by agent-A: "adding refresh tokens"
npm install -g @virsanghavi/axis-server
Claude Code:
claude mcp add --scope project --transport http axis https://useaxis.dev/api/mcp
Cursor, Claude Desktop, Windsurf, and anything else that speaks MCP, in the client's config file:
{
"mcpServers": { "axis": { "url": "https://useaxis.dev/api/mcp" } } }
Authenticate with OAuth, so there is no key to manage. A Bearer API key from useaxis.dev works too. Tools land server side, so there is nothing to update on your machine when they change.
The hosted board is what makes coordination work across people. If you want the server in your own process:
axis-server
| Variable | Purpose |
|---|---|
AXIS_API_KEY | Board credential, from useaxis.dev |
AXIS_API_SECRET | Paired secret for that key |
AXIS_ORG_ID | Pin the board to one org, when you belong to several |
AXIS_WORKSPACE_ROOT | Repository root, if your agent host does not supply one |
Axis derives project identity from the active repository and rebinds itself when an agent moves to a different one, so jobs and locks do not leak between repos.
Coordination: post_job, claim_next_job, complete_job, list_jobs, propose_file_access, verify_file_lock, release_file_access, list_locks, list_agents, finalize_session.
Shared context: get_project_soul, update_project_soul, update_shared_context, read_context, search_codebase, search_docs.
Worktrees isolate files. They do not isolate intent. Two agents in two worktrees can both decide the auth refactor is next, both do it correctly, and produce zero merge conflicts. You paid twice and now you throw one away. Claiming the work before you start is the part worktrees cannot do.
AGPL-3.0.