How to Use the Discourse MCP in VS Code Copilot

Q: How do we share the Discourse MCP Server configuration in VS Code Copilot?

Create a .vscode/mcp.json file at the root of your shared git repository. When team members open the project in VS Code Copilot, the editor automatically loads the MCP tools, giving everyone access to listforumcategories and other Discourse endpoints.

Q: Can this tool modify user profiles or group memberships?

No, this integration is read-only. Tools like getuserprofile and listgroupmembers only retrieve information to help your VS Code Copilot team understand the current state of your Discourse forum.

Q: Where does the Discourse forum data go when queried by Copilot?

All Discourse forum data retrieved via gettopicdetails or listactivemembers is processed in memory on your local machine. It is used strictly to answer your active VS Code Copilot chat prompt and is never saved or cached externally.

Share Discourse forum context across your entire engineering team inside VS Code Copilot.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Discourse MCP to VS Code Copilot

Create your Vinkius account to connect Discourse to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Discourse with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Share forum context across your team in VS Code Copilot

Keep your entire engineering team aligned by checking your team's internal Discourse forum directly from the editor. By committing an MCP configuration file to your repository, every developer gets instant access to `search_community_content` inside their VS Code Copilot chat panel. When debugging a legacy bug, VS Code Copilot can call `get_topic_details` to retrieve the original design discussion from your Discourse forum. Developers do not need to search external wikis when the answer is already documented in the thread.

Audit community access and groups

Managing user permissions during development is tricky. VS Code Copilot uses `list_community_groups` and `list_group_members` to let developers verify which roles have access to specific Discourse categories. This makes it easy to write secure backend rules in VS Code Copilot. Your agent can check `get_user_profile` to confirm that your local authorization logic matches the actual Discourse trust levels.

Monitor forum health from your workspace

Keep an eye on platform stability by monitoring Discourse user activity directly from your editor. VS Code Copilot can run `list_active_members` and `list_trending_discussions` to check if a recent deployment caused an issue. If users start reporting bugs, your VS Code Copilot agent can pull the latest threads with `list_latest_topics`. This lets you spot and fix production issues on your Discourse forum before they escalate.

Setup guide

Set up Discourse MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Discourse MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Discourse tools listed. Try asking: "List my recent Discourse transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "discourse-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Discourse. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Discourse now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Discourse MCP in VS Code Copilot

Create a `.vscode/mcp.json` file at the root of your shared git repository. When team members open the project in VS Code Copilot, the editor automatically loads the MCP tools, giving everyone access to `list_forum_categories` and other Discourse endpoints.

It depends on the API key configured in your settings. If the key has read permissions for private categories, VS Code Copilot can use `search_community_content` to find those hidden Discourse discussions.

No, you can configure a single shared MCP token within your team's workspace settings. This lets VS Code Copilot run `get_site_configuration` and other Discourse tools without requiring every developer to have their own admin account.

No, this integration is read-only. Tools like `get_user_profile` and `list_group_members` only retrieve information to help your VS Code Copilot team understand the current state of your Discourse forum.

All Discourse forum data retrieved via `get_topic_details` or `list_active_members` is processed in memory on your local machine. It is used strictly to answer your active VS Code Copilot chat prompt and is never saved or cached externally.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript