Voor ons gebruik zoeken we eigenlijk naar de documentatie van discourse-dev MCP. Op die manier willen we er zeker van zijn dat we ons houden aan de nieuwste dev-standaarden en specifieke discourse-regels om kleine aanpassingen te maken aan thema-componenten (en misschien zelfs plugins).
4 likes
I published a first revision of this:
{
"mcpServers": {
"discourse": {
"command": "npx",
"args": ["-y", "@discourse/mcp@latest"],
"env": {}
}
}
}
4 likes
{
"mcpServers": {
"discourse": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@discourse/mcp@latest", "--site", "https://meta.discourse.org", "--default-search", "#developer-guides"],
"env": {}
}
}
Its not quite perfect cause it does not support “falling back” to the entire forum, but it achieves a most of the task you presented.
Particularly --site can be used to tether the mcp to a single discourse site and --default-search can be used to ground the search with specific keywords.
3 likes
Would you prefer future suggestions posted
- as new reply to this topic
- as issue (tag: enhancement) with GitHub project (GitHub · Where software is built)
- posted in my original list
Question:
I know some users would prefer not to have their post made available to an AI as they did not op in for this. I checked user preferences for this and did not find any.
This is what I see for my Discourse OpenAI account
Sorry if this turns into a heated topic and/or possibly change to the Discourse core code; better to resolve now rather than latter.
If this does turn into a discussion, please move to a new topic so others have an opportunity to see it.
For now as I am moving quite fast this is probably a good approach, though I don’t mind if you maintain a list in the OP
This is not a setting we have and really to me this is more of a decision of forum admins vs end users on the forum. Once info is public there is no protocol for “making content available to search engines / humans and no ai” so I would not even know where to start there.
5 likes
In the end all the big AI companies probably have swallowed any content they can get their hands on for training purposes anyway. So whatever content we post here, they already processed and used it.
FYI a closing } is missing in your mcp json
1 like
@sam when I use your JSON with the developer-guides args, no tools are available. See screenshot below, tested with augment code:
Sorry, hoe kan ik dit probleem reproduceren?
Steps:
- Add the “regular” MCP to your tool of your choice:
{
"mcpServers": {
"discourse": {
"command": "npx",
"args": ["-y", "@discourse/mcp@latest"],
"env": {}
}
}
}
- Add the “discourse-dev” MCP:
{
"mcpServers": {
"discourse": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@discourse/mcp@latest", "--site", "https://meta.discourse.org", "--default-search", "#developer-guides"],
"env": {}
}
}
}
The “discourse-dev” MCP with the additional arg’s isn’t providing any of the tools as the regular MCP does.
I hope that does make sense 
wacht, probeer je de MCP twee keer toe te voegen?
1 like
Ja, ik heb ze twee keer toegevoegd, maar met verschillende namen, anders zou de augment code een foutmelding geven bij het toevoegen ervan dat de naam al in gebruik is.
Hetzelfde probleem doet zich voor als ik alleen de “discourse dev docs” MCP toevoeg zonder de naam te wijzigen, er zijn geen tools beschikbaar.
Closing the loop here: MCP is out!
8 likes