For our use case, we are actually looking for discourse-dev documentation MCP. That way, we want to make sure by abide by the latest dev standards and discourse specific rules to make small modifications to theme components (and maybe even plugins).
4 Likes
I published a first revision of this:
{
"mcpServers": {
"discourse": {
"command": "npx",
"args": ["-y", "@discourse/mcp@latest"],
"env": {}
}
}
}
3 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.
2 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.
4 Likes