Is AXP a replacement for MCP?

No. MCP is session-scoped tool wiring. AXP is durable cross-party coordination. Many deployments use both.

Can non-agent services participate?

Yes — any service that can submit or process intents over the SDK or HTTP API is a peer, not a second-class integration.

Where is the specification published?

The AXP spec and reference implementations are maintained in the axp-spec repository; the /protocol/ page links to normative docs.

AXME CLOUD

AXP: the open protocol that treats agents, services, and humans as equal peers

Every integration is bespoke. There is no standard way for an agent to say "I need a human to review this" or "complete this when the external API responds."

AXP (AXME Intent Protocol) defines how any process communicates intent: submit, receive, process, resolve — across machines, time zones, and trust boundaries.

Start free Read docs

AXP: intents as the unit of work

Agents, microservices, and humans all need the same verbs: submit work, accept assignment, process with checkpoints, resolve with outcome. Without a shared protocol, every team invents REST shapes, webhook payloads, and state stores that do not interoperate.

AXP (AXME Intent Protocol) standardizes those primitives. Any participant can submit or receive intents; AXME Cloud provides the durable runtime; Mesh adds fleet governance on top.

CAPABILITIES

How it works.

Submit

Declare intent to the fabric.

Receive

Accept assigned work.

Process

Execute with durable checkpoints.

Resolve

Complete, fail, or escalate.

AXP vs MCP

MCP connects agents to tools. AXP coordinates agents, services, and humans over time. They are complementary — not competing.

Five SDKs

# Python, TypeScript, Go, Java, .NET
pip install axme
npm install @axme/sdk

AXP and MCP together

Model Context Protocol connects an agent to tools in a single session. AXP coordinates work across time, organizations, and runtimes — including humans who respond hours later. They are complementary: MCP for tool access, AXP for lifecycle and accountability.

SDKs in Python, TypeScript, Go, Java, and .NET map protocol operations to your stack. The open spec lives at github.com/AxmeAI/axp-spec for partners building native adapters.

Common questions

Is AXP a replacement for MCP?: No. MCP is session-scoped tool wiring. AXP is durable cross-party coordination. Many deployments use both.
Can non-agent services participate?: Yes — any service that can submit or process intents over the SDK or HTTP API is a peer, not a second-class integration.
Where is the specification published?: The AXP spec and reference implementations are maintained in the axp-spec repository; the /protocol/ page links to normative docs.

Durable execution

Runtime on Cloud.

Integrations

Framework adapters.

Ship your first durable agent — in under 10 minutes.

Free tier. No credit card. Self-host or hosted — your choice.

Start free now Read the docs