Looked in this forum and on GitHub Discourse for an official Discourse Model Context Protocol (MCP) and did not find anything.
While there are unofficial Discourse MCP (ref ), would much prefer an official one. Yes I am considering creating my own if needed.
---
Update:
DeepLearning.AI just released a free online class taught by Elie Schoppik from Anthropic
https://learn.deeplearning.ai/courses/mcp-build-rich-context-ai-apps-with-anthropic/lesson/fkbhh/introduction
Discuss this on our forum.
1 Like
sam
May 22, 2025, 12:38am
2
My current thinking roadmap wise is is along this… still needs lots of refinement but it helps paint a picture of how I think about this.
V0 - MCP server Allow admin to select a collection of tools (either custom or built-in) and publish to a particular endpoint. /discourse-ai/mcp/NAME
Use Bearer for authentication - in particular a user API key
Key can be scoped to a particular MCP service
Milestone
Discourse tools (eg: search instance, read topics etc…) can be consumed by Cursor and Claude desktop V1 - MCP client Allow admin to consume an MCP service, which adds a list of tools to the available tool list that can then be consumed by personas.
Use Bearer for authentication
Milestone
V2 - MCP client per user When discussing with bot, privileged users can click “add MCP” and add MCP to an ongoing conversation Use Bearer for auth Milestone
End users can choose to add context for an MCP of choice to an ongoing AI conversation V3 - Implement OAuth 2 for auth This is a more complex auth mechanism especially registration
Milestone
V4 - Implement a “bridge” mechanism for local resource access Implement a gem or desktop app that allows access to local resources via MCP to discourse, utilizing stdio transport milestone
You can converse with a Discourse Bot PM and access local files for extra context Discuss this on our forum.
2 Likes
leaving this here as a possible way of modularizing it , glad to see a conversation on this topic.https://smithery.ai/
Discuss this on our forum.
Hi everyone,
Just jumping in to say that we currently operate as an MCP client via ravenala.ai , and we’ve seen some of our users start to integrate Discourse through Zapier-based workflows.
We're especially excited by the potential of a native MCP server , and would love to know if there’s a rough ETA for V0 or any experimental endpoint we might start testing with. Even a simple /discourse-ai/mcp/NAME
setup with basic tools (search/read topics, fetch posts) would open up some great async automation use cases.
Happy to share specific feedback and lightweight ideas if helpful—looking forward to seeing how this evolves!
Discuss this on our forum.
1 Like