Axis

dev.useaxisPublished by useaxis.devOfficial publisherv1.14.2Updated Oct 28, 2026

Coding agents from Claude Code, Cursor and Codex claim jobs and lock files on one shared board.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Axis gives coding agents a shared job board and file locks so multiple agents on one project can claim work and avoid editing the same file.

What you can do
  • Post, claim, complete and list jobs on a shared board
  • Request, verify and release file locks before editing a file, and list current locks and agents
  • Finalize a session and read or update shared project context and the project "soul"
  • Search the codebase and docs for shared context
When to use it
Useful when several coding agents, run by different people or tools on different machines, work on the same repository and need to claim work and avoid conflicting edits. Less useful for a single agent working alone, where local-only mode adds little.
Requirements
Either the hosted remote endpoint or the local npm package run with npx (Node.js). OAuth authentication, or a Bearer API key from useaxis.dev; the local process reads AXIS_API_KEY, AXIS_API_SECRET and optionally AXIS_ORG_ID and AXIS_WORKSPACE_ROOT. Network access for cross-machine coordination.
Before you install
Requires a board credential and its paired secret (AXIS_API_SECRET); keep them out of shared configs. Agents can write shared state: jobs, locks and shared context are visible to teammates and other agents. Local-only mode without AXIS_API_KEY gives no cross-machine coordination.

Installation

In SourceWeft

  1. Open Axis in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.useaxis%2Faxis/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "axis": {
      "type": "http",
      "url": "https://useaxis.dev/api/mcp"
    }
  }
}

README

@virsanghavi/axis-server

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   ->  GRANTEDagent-B  propose_file_access src/auth.ts   ->  REQUIRES_ORCHESTRATION                                               held by agent-A: "adding refresh tokens"

Install

bash
npm install -g @virsanghavi/axis-server

Connect an agent

Claude Code:

bash
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:

json
{  "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.

Run it locally instead

The hosted board is what makes coordination work across people. If you want the server in your own process:

bash
axis-server
VariablePurpose
AXIS_API_KEYBoard credential, from useaxis.dev
AXIS_API_SECRETPaired secret for that key
AXIS_ORG_IDPin the board to one org, when you belong to several
AXIS_WORKSPACE_ROOTRepository 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.

What agents get

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.

Why not git worktrees

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.

Links

AGPL-3.0.

Source: packages/axis-server/README.md at commit 725537f

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.14.2LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts