Skip to main content
Glama
codex-discord-mcp

codex-discord-mcp

Related Servers

Alternatives to codex-discord-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      A local MCP bridge that lets Claude Desktop delegate work to OpenAI API models, drive a locally installed Codex app-server, and call user-configured external MCP servers. It also provides persistent memory, context compaction, a task queue, and workspace file reading/search, with write and remote actions gated behind explicit confirmations.
      34
      MIT
    • A
      license
      A
      quality
      C
      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
    • 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
    • A
      license
      B
      quality
      C
      maintenance
      Connects AI assistants to a user's own Discord bot over MCP stdio, letting them manage server design, channels, roles, messages, voice, moderation, community events, and webhooks through the official Discord API using natural language. Runs locally with a bot token, requires no custom bot commands, and restricts actions by the bot's granted permissions and an optional server allowlist.
      27
      1
      MIT

    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

    ActivityMaintained
    ResponsivenessNo recent community issues