# Discourse MCP is here! **URL:** https://meta.discourse.org/t/discourse-mcp-is-here/386983 **Category:** Blog **Tags:** ai, mcp **Created:** [October 28, 2025, 7:08pm UTC](https://meta.discourse.org/t/discourse-mcp-is-here/386983 "2025-10-28T19:08:37Z") **Posts on this page:** 1 **Showing post:** 29
### Author: ![pacharanero](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pacharanero/32/500583_2.png) [@pacharanero](https://meta.discourse.org/u/pacharanero) #### Post date: [March 31, 2026, 12:30pm UTC](https://meta.discourse.org/t/discourse-mcp-is-here/386983/29 "2026-03-31T12:30:46Z")
Thanks for the Discourse MCP, it is great to be able to interact with my various Discourses via LLM! Having played with it, I have a couple of thoughts around the functionality. ### 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. ### Edit an existing post 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. --- _[View the full topic](https://meta.discourse.org/t/discourse-mcp-is-here/386983)._