Skip to main content
Glama
discobrain

discourse-mcp

by discobrain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to discourse-mcp

No user-submitted related servers found.

    Related Servers

    • MCP for Flarum

      linkrobins
      A
      license
      A
      quality
      A
      maintenance
      Provides MCP-compatible AI clients with full access to a Flarum forum's API, enabling reading, searching, creating discussions, replying, moderation, and management of users, tags, and groups.
      15
      2
      MIT

    • ptalk-agent

      kaecer68
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to connect to the P-Talk civic discussion forum over MCP/stdio, synchronizing platform rules, reporting skill attestation, running health checks, and posting questions or replies as an AI agent using environment-provided credentials.
      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.
      5 npm
      3
      MIT
    • agoradigest-mcp by agoradigest

      agoradigest-mcpofficial

      agoradigest
      A
      license
      A
      quality
      D
      maintenance
      MCP server that connects your AgoraDigest A2A agent to MCP-compatible clients, enabling drive of agent actions like sending DMs, checking inbox, managing friends, and rehydrating context with persistent per-friend memory.
      12
      1
      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.9/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool maps to a distinct resource/action: search, topic, post, user, categories, notifications, PM list, and PM content. The two PM tools are clearly list-vs-read, and read_private_message's error behavior clarifies its boundary.

    Naming Consistency4/5

    Tool names consistently use snake_case and the discourse_ prefix, but the verb choice is slightly mixed across search, read, get, and list. This is mostly predictable, with minor deviations like discourse_get_user standing apart from the discourse_read_* content tools.

    Tool Count5/5

    Eight tools is a well-scoped size for a read-only Discourse client. Each tool earns its place, covering public reading, search, user info, categories, notifications, and private messages without redundancy.

    Completeness3/5

    The read-only surface covers the main resources, but there is no direct way to list or browse topics, such as latest topics or topics within a category, so discovery depends heavily on search. Write/reply operations are also absent, which is consistent with a read-only intent but limits full forum workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources