Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/virsanghavi/axis/llms.txt

Use this file to discover all available pages before exploring further.

Every AI coding agent that speaks MCP — Claude Code, Cursor, Codex, Windsurf, Antigravity, and more — can connect to Axis through a single hosted endpoint. There is nothing to install locally and nothing to update when new tools ship: all 28 coordination tools live server-side at https://useaxis.dev/api/mcp. Once connected, your agent automatically joins the shared job board, takes file locks before editing, and reads from the live notepad — whether you are working solo or coordinating across a whole team.

​
Hosted endpoint

https://useaxis.dev/api/mcp
Every client connects to this same URL regardless of auth method, operating system, or IDE.

​
Authentication modes

Axis supports two authentication modes on the same endpoint.

​
Zero-install, zero-update

New tools land server-side. When Axis ships a new coordination primitive, it is available the next time your agent connects — no package to upgrade, no config to touch. The only thing on your machine is a single URL in your MCP client’s config.

​
Project auto-detection

Axis derives the project name from your repo root — the nearest .git or package.json walking up the directory tree — so every local clone maps to its own Axis project automatically. You only need to override this when you want multiple teammates’ agents to share the same board. To do that, commit a .axis/axis.json file at the repo root:
{ "project": "your-repo-name", "org": "<orgId>" }
The org field is your org ID from useaxis.dev/team. Once committed, every teammate’s clone resolves to the same job board, file locks, and codebase index — no per-machine setup required.
Workspace switching is automatic at runtime. Every tool call re-resolves the active workspace from the AXIS_WORKSPACE_ROOT environment variable and from any absolute file path in the call’s arguments. When either points at a different repository, the server rebinds in-process and notes the switch in the tool response — no restart, no stale “default” board leaking across repos.

​
Agent protocol

When Axis MCP tools are available in an agent’s environment, the agent follows the coordination protocol automatically — no user instruction needed. The first action on any task is always get_project_soul, which loads the project’s goals, conventions, and current state. From there the agent checks the job board, locks files before editing, and calls finalize_session when done.

​
Supported clients

Claude Code

Add via CLI or config file. OAuth with one command; API key for scripted environments. Full session transcript capture included.

Cursor

One-click install link or .cursor/mcp.json. OAuth shows a Needs login prompt on the server entry.

Windsurf, VS Code, Gemini CLI, Codex CLI & more

Per-client instructions for Windsurf, VS Code GitHub Copilot, Gemini CLI, Codex CLI, Antigravity, Cline, Zed, JetBrains, and any stdio-only client via mcp-remote.

Any stdio-only client

Use mcp-remote as a bridge. Any client that supports command + args MCP config can connect to the hosted HTTP endpoint.

Build docs developers (and LLMs) love

Get started for freeTalk to us