As soon as Anthropic open sourced their Model Context Protocol (MCP) proposal for interfacing with AI agents almost a year ago, we started getting excited about how good of a match it was for Discourse.
Here is a good example of workflows that are possible with Discourse MCP, Discourse → Jira integration
Impressive, although I’m surprised you’re using Jira and not Discourse 
I know you are joking, but was going for an good illustrative example for large companies with many channels for customer support who centralize things on Jira for historical reasons
Does anyone have more ideas for integrations like that? I could do a couple more screencasts.
This is how I feel about this 
But in all seriousness, fantastic addition.
Where can we find the final documentation about possible arg values and all available commands/tools?
For example, I would like to add the MCP to my IDE but limit it to specific categories such as Dev and Documentation > Developer Guides
Documentation is maintained at GitHub - discourse/discourse-mcp: MCP client for Discourse sites
This also shows in the UI of your MCP client, for example Claude Code shows
Currently you can prompt your way there with something along the lines of:
When searching or filtering, via
discourse_filter_topicsordiscourse_search, appendcategory:dev,documentationto thequeryso you only search relevant information.
Question for using Discourse MCP. If a user uses MCP, does that count towards their login date? so they can get Devotee badge easily?
The Meta TOS forbids to use this anyway 
You may not automate access to the forum, or monitor the forum, such as with a web crawler, browser plug-in or add-on, or other computer program that is not a web browser. You may crawl the forum to index it for a publicly available search engine, if you run one.
A post was split to a new topic: Discourse MCP User API Key Generator Error Nodejs 20
Great news, and this sparks all good moonshot ideation. I would love to see Discourse MCP available on Cursor. This will open up the door to community users of all levels on dev or coding. This integration would serve a bountiful source of use cases and practical feedback.
Oh, it is, you just need to add it to your mcp config 
So far, the MCP works like a charm!
But another question: Is there any way to add an argument to retrieve a specific translation of the topic?
Our use case: We have a large KB in German which is then translated to English. Our maintainers are German speakers with limited English skills.
Hence, we would like to maintain content in German but retrieve the localized English content.
Is that achievable?
Not currently, but adding an extra parameter to the read tool to pass a locale would be a good feature.
It might be related to my feature request here: Support for tl=[lang] parameters in REST API (for non-anon users)
From a user perspective, it would be great to have an identical parameter and set of values for MCP as well as the REST API.
Does that make sense?
@falco do you accept PRs? While the discourse MCP has a tool to create new categories, there is no permissions argument.
I could submit the following PR:
Proposed Changes for Discourse
src/tools/builtin/create_category.ts
Update
zodschema to accept an optionalpermissionsfield.
Type:
z.record(z.string(), z.number()).optional().Description: Map of group names to permission levels.
Format:
{ "group_name": permission_type_int }Permission type values (from Discourse schema):
1: full (See, Reply, Create)
2: create_post (Reply only)
3: readonly (See only)Pass
permissionsin the payload toclient.post('/categories.json', payload).
Yes, feel free to send PRs.
