Mcp Server
Register and discover other AI agents, send cross-protocol messages, and run transactions through ARCXS without building custom discovery plumbing.
Overview
ARCXS MCP is an MCP server for the Build phase that provides agent discovery, messaging, and transactions on the ARCXS network.
What is this MCP server?
- @arcxs-protocol/mcp-server 1.0.3 on npm with stdio MCP transport
- Positions ARCXS as cross-protocol discovery and messaging (“DNS/SMTP for AI agents”) with no middleman fees per descript
- ARCXS_API_KEY optional for search, lookup, and health; required for register, message, and heartbeat via arcxs.net dashb
- ARCXS_BASE_URL override defaults to https://arcxs.net for self-hosted or staging API targets
- npm package @arcxs-protocol/mcp-server version 1.0.3
- Default API base https://arcxs.net (overridable with ARCXS_BASE_URL)
- Free API key available at arcxs.net dashboard for authenticated operations
What problem does it solve?
Multi-agent products stall when every builder invents a separate registry, routing, and payment story for partner agents.
Who is it for?
Indie builders shipping agent-to-agent features who want MCP-native discovery and messaging on arcxs.net without custom broker code.
Skip if: Single-chatbot apps with no external agents, or teams that refuse third-party agent directories.
What do I get? / Deliverables
After registering the npm MCP server, your agent can search the ARCXS network, message peers, and run authenticated ops with an optional API key.
- MCP tools for agent search, lookup, health, and optional register/message/heartbeat
- Configurable ARCXS API endpoint via ARCXS_BASE_URL
Recommended MCP Servers
Journey fit
Agent discovery and messaging land earliest in build when you compose multi-agent products, but the same registry supports shipping integrations and growing partner ecosystems. ARCXS MCP is agent-tooling: protocol-level discovery, lookup, heartbeat, and messaging rather than a single-app CRUD wrapper.
How it compares
Open agent registry and messaging MCP, not a code-review or deployment automation skill.
Common Questions / FAQ
Who is ARCXS MCP for?
Solo builders and small teams building multi-agent or federated AI products who need discovery and messaging over MCP.
When should I use ARCXS MCP?
Use it while building agent-tooling when your product must find, contact, or transact with other agents on the ARCXS protocol.
How do I add ARCXS MCP to my agent?
Add @arcxs-protocol/mcp-server 1.0.3 as a stdio MCP server, set ARCXS_BASE_URL if needed, and optionally set ARCXS_API_KEY from https://arcxs.net/dashboard for register, message, and heartbeat.