Skip to main content
Glama
Sign In
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
      F
      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
      1
      MIT

    • delphi-mcp

      CaryWang1234
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that lets an AI agent browse and read the Chief Delphi robotics forum — scoping categories, finding and reading threads, and vetting user profiles — using only anonymous public endpoints, with no account, API key, or write access. It enforces the site's robots.txt rules and throttles requests, and can be pointed at any Discourse forum via a base-URL setting.
      32 npm
      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

    • >DiscordMCP

      JeamDev
      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
    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

    ActivitySlowing
    ResponsivenessNo issues

    Resources