Skip to main content
Glama
matheusfillipe

ircv3-mcp

by matheusfillipe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ircv3-mcp

No user-submitted related servers found.

    Related Servers

    • hauddy by Hauddy

      hauddyofficial

      Hauddy
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to message each other by @nickname via an MCP server, with contacts, presence, and durable delivery across local and remote agents.
      3
      Apache 2.0

    • rocketchat-mcp

      SufiSR
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Rocket.Chat, enabling AI agents to interact with Rocket.Chat workspaces via tools like listing users, sending messages, and managing channels.
      2
      -

    • rivendell

      Fulviuus
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Rivendell, a workspace where AI agents collaborate on threaded discussions with resolutions. Provides tools for agents to create threads, reply with structured verdicts, and manage project context.
      2 npm
      MIT

    • agent-bridge

      itcomduke
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP central server that lets multiple AI agents (e.g., Claude Code, kimi-code) exchange private messages, shared channel broadcasts, and unified message streams via MCP tools, with SQLite persistence and per-connection identity binding.
      4 npm
      MIT

    • AgentTalks

      NovaSeth
      A
      license
      Not graded
      quality
      B
      maintenance
      A communication server for AI agents and humans to collaborate in channels, threads, and DMs with proven identity, mentions, wiki, and resource leases, accessible via MCP, REST, and CLI.
      MIT

    • halobot

      anthony-maio
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to communicate with humans through Discord. Agents can send messages, create threads, wait for replies, and manage conversations across any MCP client.
      9 npm
      ISC
    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.6/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools target clearly distinct actions and resources. The main overlaps are irc_send_message vs irc_send_with_typing and irc_read_history vs irc_recent_events, but the descriptions explicitly separate immediate delivery from typing-indicator sends and server history from the live event buffer, so agents can reliably disambiguate.

    Naming Consistency4/5

    All tools share the irc_ prefix and most follow a verb_noun pattern like irc_list_members, irc_send_message, and irc_mark_read. A few names deviate slightly—irc_status, irc_whois, and irc_recent_events are noun-like—but the overall pattern remains predictable and readable.

    Tool Count4/5

    17 tools is slightly above the typical sweet spot, but each tool maps to a meaningful IRC capability: connection status, history, live events, messaging, typing, reactions, membership, channel join/part, and raw protocol access. None feel redundant enough to remove, and the count is reasonable for an IRC client surface.

    Completeness4/5

    The core IRC lifecycle is well covered: join/part, send/reply/react/redact, read history and live events, list members, whois, typing indicators, and read markers. Dedicated tools for topic changes, mode changes, or nick changes are missing, but irc_send_raw provides a workable escape hatch for those operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources