Skip to content
Discourse logo

Discourse MCP server

Modern open source forum software

Discourse is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
6
Works with
Any MCP client
Auth
Custom auth
License
MIT, open source
Updated
September 2026

About the Discourse MCP server

Connect Discourse once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Discourse and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Discourse tools your AI can run

Once connected, your assistant can call any of these Discourse actions by asking in plain language.

  • Create Post

    Create a new post in discourse

    2 fields

  • Create Topic

    Create a new topic in Discourse

    3 fields

  • Change User Trust Level

    Change the trust level of a user

    2 fields

  • Add Users to Group

    Add users to a group

    2 fields

  • Send Private Message

    Send a private message in Discourse

    3 fields

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Give your assistant Discourse

Connect Discourse once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Discourse MCP, answered.

No. That is the point of it. One Activepieces server exposes Discourse alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Discourse in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 6 tools, including Create Post, Create Topic, Change User Trust Level, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.