Built-in MCP server

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