Discourse MCP is here!

[Falco]

@pacharanero

Various LLMs reported to me while using the MCP that they could create new Topics and Replies, but couldn’t edit existing posts. For Discourse sysadmins, being able to ask an LLM to update a Wiki (for example) would be a super powerful capability.

@jrgong

for this!!!

Ability to edit existing posts/topics is a very useful addition.

I added an edit tool to MCP, just update to latest.

@pacharanero

Remote (web) MCP

First up, I think while a local npx-run, stdout-based MCP is useful for power users who are competent in the CLI and have npm installed and are already using Claude Code, opencode, Codex CLI or similar, it won’t really be possible for the majority of Discourse users to use the MCP until it is something that each Discourse instance publishes at a well-known URL.

I wonder if perhaps a plugin-ized version of the MCP could run on the same server as a self-hosted Discourse (perhaps in a separate container like mail-receiver), interacting with the Discourse via API (as does mail-receiver) but also interacting with web-based LLMs like Claude Web / ChatGPT Web via an authenticated web API. This would unlock the MCP feature for non-dev users.

I wanted to check that something similar isn’t in the pipeline already.

Our MCP has support for http transport too, not only stdout. I added that before publishing this blog post even, back in October of last year. So you can run it on a sidecar service anywhere you want!