Skip to content

Cursor

Connect OpenQuok MCP to Cursor via .cursor/mcp.json for Agent, Composer, and inline chat tools.

3 min read

Connect your agent today

Draft from chat, review in your calendar, and publish only what you approve.

Start for $0

Prerequisites

  • Cursor with MCP support enabled (recent stable builds).
  • An OpenQuok programmatic token (opo_) from AccountSettingsDevelopersAccess.
  • At least one connected social channel in your OpenQuok workspace (for verification).

Configuration file

Cursor reads MCP servers from .cursor/mcp.json at the project root. Create the file (or merge into an existing one) so Agent and Composer can call OpenQuok tools.

Setup

Generate your token

In the OpenQuok app, open AccountSettingsDevelopersAccess. Create an OAuth app if prompted, then generate an opo_… token.

Generate programmatic token

Create or edit .cursor/mcp.json

In your project root, add an openquok entry under mcpServers:

Attach OpenQuok in Cursor

Save .cursor/mcp.json, then make sure Cursor has loaded the server into the session you will use:

  1. Open Customize → MCPs (or Cursor Settings → MCP on builds that still use that label).
  2. Confirm openquok shows as connected — not error or disabled.
  3. Start a new Agent or Composer chat and ask there. Existing sessions often keep the old server list and will not see tools from a server added after the chat started.

On some Cursor versions, editing mcp.json alone is not enough. If the file looks valid but openquok is missing or stuck, fully quit Cursor and reopen the project, then repeat the steps above.

Verify the connection

Ask your agent:

List my connected social media accounts

The agent should call integrationList and return channel names and IDs from your workspace.

Self-hosted API

Replace https://api.openquok.com with your BACKEND_DOMAIN_URL origin (no /api/v1 suffix). The MCP path is always /mcp on the API host.

Troubleshooting

Search documentation
Find a docs page
Discord Support