How to Use the Discourse MCP in Cursor

Q: How do I configure the Discourse MCP Server inside Cursor?

Create a .cursor/mcp.json file in your project root and add the server configuration. Once added, Cursor can automatically call Discourse tools like getsiteconfiguration when you ask questions in the chat sidebar.

Q: Can I use the Discourse tools in Cursor Agent mode?

Yes, Cursor Agent mode can autonomously call tools like searchcommunitycontent or listforumcategories to gather context. This helps the editor write precise code that interacts with your Discourse forum's structure.

Generate code using real-time forum data from your Discourse instance inside Cursor.

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 Cursor

Create your Vinkius account to connect Discourse to Cursor 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 Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Write code against live forum API data in Cursor

Stop writing code against stale API documentation or mock forum payloads. When you run Cursor in Agent mode, it uses the Discourse MCP Server to inspect your actual forum settings and structure via `get_site_configuration`. If you are building custom Discourse widgets, Cursor can trigger `list_latest_topics` to see real JSON payloads. This lets the Cursor AI write exact, bug-free parsing logic based on your live community data.

Debug community API integrations faster

When your custom Discourse integration breaks, you do not need to open external API clients. Your Cursor editor runs `search_community_content` to find error reports or relevant forum discussions directly from your codebase. By using `get_topic_details`, Cursor pulls the exact Discourse thread where your team discussed the API change. You get the context behind a specific endpoint without leaving your active file in the editor.

Audit user permissions while writing admin scripts

If you are writing scripts to sync user directories, you need to know who is who. Cursor uses `get_user_profile` and `list_active_members` to check live Discourse accounts against your local database migrations. You can also query `list_group_members` in Cursor to verify that your script targets the correct Discourse community segments. This keeps your local test runs aligned with actual production groups.

Setup guide

Set up Discourse MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Discourse MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Discourse transactions." If the MCP tools are loaded correctly, Cursor will call the Discourse tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/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 Cursor

Create a `.cursor/mcp.json` file in your project root and add the server configuration. Once added, Cursor can automatically call Discourse tools like `get_site_configuration` when you ask questions in the chat sidebar.

Yes, Cursor Agent mode can autonomously call tools like `search_community_content` or `list_forum_categories` to gather context. This helps the editor write precise code that interacts with your Discourse forum's structure.

Yes, if your dev instance is running on localhost, you can configure the MCP Server to point to your local API. Cursor tools like `list_latest_topics` will pull data from your local database instead of production.

No, this toolset is strictly read-only for safety. Your Cursor editor can use `get_topic_details` to read content, but it cannot write new posts or modify existing Discourse forum data.

Your Discourse forum settings and API keys are stored locally on your machine. The server reads data like `get_site_configuration` to help you write code in Cursor, but that sensitive data is never sent to external servers or used to train public models.

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