@a2am/mcp-server

MCP server that exposes A2AM agent discovery as native Claude Code tools.

Quick Start

npx --package=@a2am/mcp-server a2am-mcp install

Then restart Claude Code. You can now use A2AM naturally:

• "Check A2AM status"
• "Find agents that can translate text"
• "Publish this project as an agent"

That's it! The MCP server connects to public A2AM gateways automatically.

Installation

One-Line Install

npx --package=@a2am/mcp-server a2am-mcp install

This configures Claude Code to use the A2AM MCP server, giving you access to these tools:

• a2am_status - Check gateway health and identity
• a2am_find - Find agents by capability or text search
• a2am_publish - Publish an agent to the network

Manual Installation

If you prefer to configure manually:

claude mcp add a2am -- npx -y @a2am/mcp-server

Uninstallation

npx --package=@a2am/mcp-server a2am-mcp uninstall

Or manually:

claude mcp remove a2am

Usage Examples

After installation, simply ask Claude to use the tools:

"Check the A2AM status"
→ Shows gateway health, your identity, and federation status

"Find me an agent that can book flights"
→ Searches for agents with travel/flights capability

"Find agents with MCP protocol support"
→ Filters by protocol

"Publish this project as an A2AM agent"
→ Auto-detects MCP servers and publishes to the network

Tools Reference

a2am_status

Check A2AM gateway health and local identity.

Arguments:
  detailed?: boolean  - Include gateway latency metrics

Example output:

A2AM Status: ✓ healthy

Identity: a1b2c3d4
Full Key: ed25519:...

Gateways (2/2 healthy):
  ✓ https://airy-radiance-production-ea90.up.railway.app
  ✓ https://resplendent-nourishment-production.up.railway.app

Federation: ✓ Active (3 gateways)

a2am_find

Discover agents on the A2AM network.

Arguments:
  query?: string       - Capability path (e.g., "travel/flights")
  text?: string        - Text search in names/descriptions
  protocols?: string[] - Filter by protocols
  limit?: number       - Max results (default: 20)

a2am_publish

Publish an agent or MCP server to the network.

Arguments:
  name?: string         - Agent name (auto-detects if not provided)
  description?: string  - Agent description
  capabilities?: string[] - Capabilities
  endpoint?: string     - Agent endpoint
  protocols?: string[]  - Supported protocols
  autoDetect?: boolean  - Auto-detect MCP servers (default: true)
  projectRoot?: string  - Project root for detection

Default Gateways

The MCP server connects to these public federated gateways by default:

• https://airy-radiance-production-ea90.up.railway.app - A2AM Gateway 1
• https://resplendent-nourishment-production.up.railway.app - A2AM Gateway 2

These gateways are federated - they automatically sync agents across the network.

Configuration

Environment Variables

• A2AM_GATEWAY_URL - Gateway URL(s), comma-separated
• A2AM_PROJECT_ROOT - Default project root for MCP detection

Config File

Create ~/.a2am/config.json:

{
  "gateways": ["https://my-gateway.example.com"],
  "projectRoot": "/path/to/project"
}

Running Your Own Gateway

Want to contribute to the network? Run your own gateway:

npx @a2am/gateway --port 9000

See @a2am/gateway for deployment options including Railway, Docker, and Fly.io.

Development

# Build
pnpm build

# Test
pnpm test

# Run locally
node dist/index.js

License

MIT