Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Coding agents from Claude Code, Cursor and Codex claim jobs and lock files on one shared board.
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.
AXIS_API_KEY, AXIS_API_SECRET, AXIS_ORG_IDValues marked secret are keys to your account. Never share them or paste them into a chat.
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://useaxis.dev/api/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into 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"
}
}
}
}Run this in your terminal
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-serverFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"axis": {
"url": "https://useaxis.dev/api/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.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"
}
}
}
}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": {
"axis": {
"type": "http",
"url": "https://useaxis.dev/api/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"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"
}
}
}
}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://useaxis.dev/api/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
AXIS_API_KEY envAXIS_ORG_ID envThese 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 6, 2026
The publisher (useaxis.dev) is not the repo owner (VirSanghavi); someone else may have listed it
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 0 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.
You need to fill in: AXIS_API_SECRET
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (1.14.2) reached the registry 3 months 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, Parano1d node
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.
Local Parano1d node over MCP. Read-only by default; sending needs the opt-in, capped wallet mode.
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.
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.