Built-in MCP server

AI-generated summary

mcwumbly announces the addition of a built-in MCP server directly into Discourse core, served at /mcp. This new feature replaces the existing client-side MCP implementation and is designed to enable integration with cloud harnesses where installing the client-side tool is not possible. The primary goals are to provide every site with first-class, permission-aware access for AI assistants without requiring extra services, to offer admins a centralized location for managing user and group access scopes, and to align with the latest MCP standards.

The first pull request for this feature is under review, and mcwumbly shares a guide for users to begin testing the new capabilities.

Subsequent updates from mcwumbly highlight two additional focus areas. First, the team is working to make it easier for agents running within Discourse to consume the full suite of MCP tools. Currently, internal agents either require complex authentication and network overhead when using the MCP server or rely on manually configured, overlapping built-in tools. The goal is to provide direct, low-overhead access to the MCP toolset for internal agents. Second, the team is improving the experience for configuring external harnesses on new sites. This effort aligns with broader initiatives to streamline new site administration, ensuring that connecting familiar AI agents to a newly created Discourse community is as seamless as possible. Future updates will be announced in the news channel as these features land.

We are adding an MCP server built directly into core, served at /mcp, which will replace the current client side MCP and enable cloud harnesses (where the existing client side tool cannot be installed) to integrate with Discourse.

Our goals are to:

  • Make it easy for every site to offer AI assistants first-class, permission-aware access with no extra service to stand up.
  • Give admins a single place to grant access to different scopes for different users and groups, so they have confidence in what they are allowing people and agents to do with these features.
  • Catch up with the most recent standards and conventions for MCP servers, and make it easier for us to keep up as they evolve.

A first PR is up and being reviewed here:

https://github.com/discourse/discourse/pull/42798

9 likes

And here’s what we’ve got for you to start kicking the tires with now:

2 likes

A couple other things we’re working on related to this project now:

Making it easier for an agent within a site to consume all the tools that the new MCP exposes

With the new MCP server, we made a bunch of “tools” available to agents. This was primarily designed for people using external harnesses. But since it’s possible to run agents within Discourse too, we want to make all those tools available to those agents too.

You can do this already today, by configuring a Discourse agent to use the the MCP server, but that means setting up authentication and making unnecessary network round trips. Alternatively, there are a list of built in tools that overlap in functionality which don’t have that extra overhead, but have to be manually configured.

We want to avoid both of those things and give agents on Discourse direct access to the toolset underlying the MCP server within the same site. Technically, that’s not really MCP anymore, but it’s reusing a bunch of stuff developed for the MCP feature, so we’re doing it under this umbrella.

Making it even easier to configure an external harness to use the MCP server on a new site

Wiring up an agent to Discourse is especially helpful when starting a new community since there’s a fair bit of setup and configuration that is front loaded. We’re taking a number of approaches in parallel to help admins on new sites get their site set up, including ongoing investments in the UI for site setup.

But making it easier to configure the agent or harness you’re familiar with to your new Discourse site is one of the approaches we also want to invest in. So we’re doing that as part of this effort too.


Stay tuned for more about each of these things. As features land, we’ll share them in Announcements.

1 like