# 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:** 13
**Page:** 2
### Author:  [@rey.riel](https://meta.discourse.org/u/rey.riel)
#### Post date: [January 20, 2026, 12:43pm UTC](https://meta.discourse.org/t/discourse-mcp-is-here/386983/22 "2026-01-20T12:43:20Z")
Behind admin makes total sense. Move on to bigger better things and I’ll submit a PR, then we can discuss more if need be
---
### Author:  [@rey.riel](https://meta.discourse.org/u/rey.riel)
#### Post date: [January 21, 2026, 7:06pm UTC](https://meta.discourse.org/t/discourse-mcp-is-here/386983/23 "2026-01-21T19:06:18Z")
PR created, feel free to review and discuss: [FEAT: Send user email if admin access is available by rjriel · Pull Request #38 · discourse/discourse-mcp · GitHub](https://github.com/discourse/discourse-mcp/pull/38)
---
### Author:  [@rey.riel](https://meta.discourse.org/u/rey.riel)
#### Post date: [January 21, 2026, 7:08pm UTC](https://meta.discourse.org/t/discourse-mcp-is-here/386983/24 "2026-01-21T19:08:50Z")
I was having an issue there as well, it’s an interesting caveat to be aware of, maybe important for the docs? If creating an admin key, don’t select “all users”, but instead select “single user” and choose “system”.
---
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [February 6, 2026, 5:27pm UTC](https://meta.discourse.org/t/discourse-mcp-is-here/386983/25 "2026-02-06T17:27:18Z")
> [@Falco](#):
>
> So we chose to ship our first iteration of the MCP server as a standalone command-line interface (CLI) that is compatible and can connect to every Discourse instance.
>
> This means you don’t have to bother your friendly Discourse admin for an update or to tweak with settings to start experimenting
How is MCP related to the Discourse-AI plugin? Does the plugin need to be installed and activated in the forum? Since you say I don’t need to ask the admin to do anything, I would expect that it isn’t required. But there is the tag for the Discourse AI Plugin on this topic. (And since you also added it to the new topic today, it doesn’t seem like this was added by accident.)
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [February 8, 2026, 5:48am UTC](https://meta.discourse.org/t/discourse-mcp-is-here/386983/26 "2026-02-08T05:48:28Z")
Perhaps the #ai tag is supposed to refer to ‘ai’ in general and not the plugin specifically.
---
### Author:  [@pacharanero](https://meta.discourse.org/u/pacharanero)
#### Post date: [March 4, 2026, 9:54pm UTC](https://meta.discourse.org/t/discourse-mcp-is-here/386983/27 "2026-03-04T21:54:29Z")
I found it was a bit tricky to set up Discourse MCP on OpenAI Codex CLI, so I wrote a guide for anyone else wanting to do the same thing.
> [@Discourse MCP Setup in OpenAI Codex CLI](https://meta.discourse.org/t/discourse-mcp-setup-in-openai-codex-cli/397662):
>
> I have been experimenting with [Discourse MCP](https://github.com/discourse/discourse-mcp) but found that the existing documentation in Meta for using it didn’t include anything for Codex CLI, and it was a little confusing working out which parts of the documentation would apply: is it npx or npm install? which parts of the setup are Codex and which parts are Discourse MCP? where do I put the settings like read\_only: false? So, after quite a bit of messing about, here is a tested guide for installing the Discourse MCP into Codex CLI, and…
---
### Author:  [@anaderi](https://meta.discourse.org/u/anaderi)
#### Post date: [March 17, 2026, 3:05pm UTC](https://meta.discourse.org/t/discourse-mcp-is-here/386983/28 "2026-03-17T15:05:34Z")
Is it possible to access PDF attachments to discourse posts via MCP?
---
### Author:  [@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.
---
### Author:  [@jrgong](https://meta.discourse.org/u/jrgong)
#### Post date: [March 31, 2026, 1:20pm UTC](https://meta.discourse.org/t/discourse-mcp-is-here/386983/30 "2026-03-31T13:20:21Z")
> [@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 this!!!
Ability to edit existing posts/topics is a very useful addition.
In our use case, we use LLMs to maintain KB/Docs categories, so we use local helper scripts to edit existing post/topics.
A Markdown repo with Github Actions is not on option unfortunately. Most of our community moderators and contributors are non-technical people and already familiar with discourse composer.
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [April 1, 2026, 9:42pm UTC](https://meta.discourse.org/t/discourse-mcp-is-here/386983/31 "2026-04-01T21:42:52Z")
> [@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!
---
### Author:  [@pacharanero](https://meta.discourse.org/u/pacharanero)
#### Post date: [April 10, 2026, 9:30am UTC](https://meta.discourse.org/t/discourse-mcp-is-here/386983/32 "2026-04-10T09:30:49Z")
> [@Falco](#):
>
> So you can run it on a sidecar service anywhere you want!
Is there a guide for a ‘Meta recommended’ way to do this?
> [@Falco](#):
>
> I added an edit tool to MCP, just update to latest.
Thanks @Falco that’s awesome!
Great work on the MCP.
---
### Author:  [@putty](https://meta.discourse.org/u/putty)
#### Post date: [April 17, 2026, 4:08pm UTC](https://meta.discourse.org/t/discourse-mcp-is-here/386983/33 "2026-04-17T16:08:50Z")
Any plans to release an http/sse streaming version of the Discourse MCP server so we can add it as a connector to Claude.ai Chat?
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [April 17, 2026, 4:34pm UTC](https://meta.discourse.org/t/discourse-mcp-is-here/386983/34 "2026-04-17T16:34:04Z")
> [@putty](#):
>
> Any plans to release an http/sse streaming version of the Discourse MCP server so we can add it as a connector to Claude.ai Chat?
We already support HTTP, since this announcement, see two replies above:
> [@Falco](#):
>
> > [@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!
I have used it with Claude desktop here:
> [@Exploring your Discourse Data with Discourse MCP](https://meta.discourse.org/t/exploring-your-discourse-data-with-discourse-mcp/395383):
>
> We just added [Data Explorer](https://meta.discourse.org/t/32566?silent=true) integration to Discourse MCP, allowing both technical and non-technical users alike to explore the vast data on their Discourse instances. The MCP uses the existing [Data Explorer](https://meta.discourse.org/t/32566?silent=true) workflow, running read-only queries in the live production database, and is able to create, run, update, and delete any [Data Explorer](https://meta.discourse.org/t/32566?silent=true) reports. To get started, use the same flow as described in our [Discourse MCP is here!](https://meta.discourse.org/t/discourse-mcp-is-here/386983) blog post, provide an admin API key, and connect it to your favorite LL…
That said, for use with a website, you will need to run the MCP CLI in a web accessible address. When I tested that I used Cloudflare Tunnels for it.
[Previous page](https://meta.discourse.org/t/discourse-mcp-is-here/386983.md?page=1)