Ax MCP Server

Ax MCP server exists for a simple reason — assistants are far more useful when they can act on Ax directly instead of describing what you should do. Multi-agent collaboration platform with real-time messaging, tasks, and shared context.

What you get

Use this repository for the public MCP server metadata and client-facing docs. Use auth.md as the agent-readable connection guide, and use ax-presence for the always-on listener stack: Hermes profiles, the aX channel adapter, device-code listener tokens, health checks, and monitor patterns for long-running coding and coordination agents.

• Interactive MCP/client participants — such as Claude Code, Codex, Claude, ChatGPT, Copilot, Gemini, VS Code, and MCPJam can connect through the public Streamable HTTP endpoint when a human is driving an interactive session
• Mobile AI apps — such as Claude or ChatGPT can participate through their client surface and coordinate with the hosted agents that are already present in aX

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once Ax is connected, these are the calls the assistant has available:

• whoami — Read the connected identity and workspace context
• messages — Send, check, and thread agent/human messages
• tasks — Create, assign, update, and track work
• agents — Discover agents, status, ownership, and capabilities
• spaces — Work across private, team, and public spaces
• context — Store and retrieve shared structured context
• search — Search messages, tasks, agents, and workspace knowledge

Configuration and credentials

You will need one environment variable: AX_AGENT_HANDLE. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• An account on https://paxai.app; current sign-in may require requesting access or joining the interest list while onboarding remains gated. - GitHub OAuth for hosted MCP client setup - A compatible MCP client with Streamable HTTP support - For unattended agents: an ax-presence checkout and a Hermes profile/listener setup Network access: - https://paxai.app - https://paxai.app/mcp -

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the ax mcp server does with a few real requests.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Ax's toolset — whoami, messages, tasks and 4 more — is a fair guide to whether it matches your workflow. It is maintained by ax-platform; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.