Skip to main content
Glama
brightseth

airc-mcp

by brightseth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to airc-mcp

No user-submitted related servers found.

    Related Servers

    • claude-peers

      louislva
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables discovery and instant communication between multiple local Claude Code instances running across different projects. It allows agents to list active peers, share work summaries, and send messages through a local broker daemon.
      17 npm
      2,205
      MIT

    • a2a-bridge

      joltedbot
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables bidirectional A2A communication between AI coding agents, allowing Claude Code to reach out to and be reached by other A2A agents via an MCP bridge and an HTTP server.
      3 npm
      MIT

    • claude-peers

      conradium-gif
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets Claude Code instances discover and message each other across sessions, with reliable delivery via hooks instead of experimental channels.
      17 npm
      MIT

    • AgentMesh

      microinginer
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables already-running AI coding agents on the same project to register, discover one another, and exchange durable direct messages so they can share progress and avoid conflicting work.
      Apache 2.0

    • A2A MCP Server

      a2anet
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to connect and interact with A2A Protocol agents, allowing discovery of agent capabilities, sending messages to remote agents, managing multi-turn conversations, and viewing artifacts returned by agents.
      16
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: registration, presence, messaging, consent, key management, discovery, and capability inspection. There is no overlap or ambiguity.

    Naming Consistency5/5

    All tools follow a consistent 'airc_' prefix with a descriptive verb or noun (e.g., airc_register, airc_send, airc_discover). No mixing of conventions.

    Tool Count5/5

    10 tools is well-scoped for a messaging and agent discovery system. Each tool earns its place, covering the essential operations without excess.

    Completeness4/5

    The tool surface covers registration, messaging, presence, consent, key rotation, revocation, discovery, and capability inspection. Minor gaps like profile updates or unregistration might exist but are not critical.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources