Skip to main content
Glama
Openclaw-Metis

codex-discord-mcp

by Openclaw-Metis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to codex-discord-mcp

No user-submitted related servers found.

    Related Servers

    • agent-talk

      YanZiBin
      A
      license
      A
      quality
      B
      maintenance
      A local MCP bridge that connects existing Codex and Claude Code conversations with DSH Web, enabling delegation, result retrieval, and human-in-the-loop coordination without leaving native chat apps.
      11
      1
      MIT

    • codex-app-mcp

      PyYoshi
      A
      license
      Not graded
      quality
      B
      maintenance
      A local stdio MCP server that lets any MCP client start a Codex thread and continue it by opaque thread ID through the codex and codex-reply tools, with fail-closed sandboxing and approval policies. It restores the removed Codex CLI MCP integration by bridging clients like OpenCode to the official Codex SDK.
      MIT

    • Crow

      Hydr46605
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server that gives AI agents first-class access to Discord, enabling discovery, messaging, channel management, moderation, and arbitrary REST calls through typed, consent-aware tools.
      9 npm
      3
      MIT

    • Mattermost Workflows for Codex

      shanginn
      F
      license
      Not graded
      quality
      C
      maintenance
      A local-first Codex plugin that bundles an MCP server to safely interact with Mattermost, enabling channel/thread summarization, conversation search, and reviewed post publishing via the Mattermost REST API.
      -
    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 11 tools

    Disambiguation3/5

    reply and send_message are described as identical in behavior, causing clear overlap and potential misselection. latest_generated_images and recover_generated_image also serve similar purposes with subtle differences that could confuse. Other tools are distinct enough.

    Naming Consistency3/5

    Naming mixes verb_noun patterns (send_message, edit_message) with bare verbs (reply, react) and noun phrases (latest_generated_images, bridge_status). While most names are readable, the inconsistency undermines predictability.

    Tool Count4/5

    At 11 tools, the count is reasonable for a Discord integration, though a few tools (reply/send_message) appear redundant and could be consolidated. Not excessive or thin.

    Completeness4/5

    Core Discord operations (send, edit, react, fetch, attachments) are covered, along with a queue mechanism and status check. Missing delete message and channel listing are minor gaps; agents can work around them using existing tools.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources