Connect Cursor to Discord

Can Cursor post to Discord?

Postgale is the secure layer for AI agents on social media. MCP (Model Context Protocol) is the open standard that lets AI assistants such as Claude and Cursor use outside tools. An MCP server is what they connect to. Cursor does not reach Discord on its own; with Postgale connected it gets tools for the Discord accounts you connected and nothing else.

What do you need?

• A Discord server where you have the Manage Webhooks permission.
• A Postgale workspace, and a sign-in or an API key for the agent.
• Optional files on a public HTTPS URL (upload them with upload_media): up to 10 MB each.
• Cursor, set up as below (Cursor’s agent with MCP).

Step 1: connect your Discord channel

1. Create a Postgale workspace and open Dashboard → Accounts → Discord.
2. On Discord, pick the server and the channel and authorize. Discord creates a webhook for Postgale in that channel.
3. Back in Postgale the channel is listed under Connected accounts, ready to publish.
4. Connect your AI tool: add https://postgale.com/mcp in ChatGPT, Claude or Cursor and sign in to Postgale, or create a key under Dashboard → API keys for n8n or your own code.

An agent can also start the connection itself: the connect_account tool (or GET /api/v1/connect/discord) returns a link for the server admin to open. The agent never gets a token.

Step 2: connect Cursor to Postgale

1. Create a Postgale workspace and connect the social accounts the agent may use under Dashboard → Accounts.
2. In Cursor, open Settings → MCP and add a server, or edit .cursor/mcp.json in the project (or ~/.cursor/mcp.json for every project). The URL alone is enough:

{
  "mcpServers": {
    "postgale": {
      "url": "https://postgale.com/mcp"
    }
  }
}

1. Cursor shows a sign-in prompt for the server. A Postgale page opens in the browser: sign in, pick the workspace the app may use and approve. The consent page names the app and where it returns to; approve only requests you started yourself.
2. Cursor lists the Postgale tools under the server once it connects; enable them for the agent.
3. In the agent chat, ask: “Which social accounts are connected in Postgale?” to check the connection.

Can I use an API key instead?

Yes, for shared or automated setups where nobody should sign in personally. In Postgale, open Dashboard → API keys, create a key and copy it (it starts with sk_ and is shown once). Connect the social accounts the agent may use under Dashboard → Accounts. Then add a headers block:

{
  "mcpServers": {
    "postgale": {
      "url": "https://postgale.com/mcp",
      "headers": {
        "Authorization": "Bearer sk_…"
      }
    }
  }
}

Keep the key out of version control: use the global file, or an environment variable if your Cursor version supports ${env:…} in mcp.json.

What can I ask Cursor to do on Discord?

Check the connection first: “Which Discord accounts are connected in Postgale?” Then, in plain language:

Ask your agent“Post the release notes to #announcements on Discord as an embed with the version number and the screenshot attached.”

Ask your agent“Schedule a Discord message for Monday at 9am reminding the server about the community call.”

Ask your agent“Delete the Discord message we posted by mistake an hour ago.”

{
  "content": "Release 2.4 is out",
  "platforms": [
    {
      "accountId": "acc_dc",
      "platformSpecificData": {
        "mediaUrl": "https://media.example.com/screenshot.png",
        "embeds": [
          {
            "title": "Changelog",
            "description": "Faster sync and dark mode.",
            "fields": [
              {
                "name": "Version",
                "value": "2.4",
                "inline": true
              }
            ],
            "image": {
              "url": "attachment://screenshot.png"
            }
          }
        ]
      }
    }
  ],
  "publishNow": true
}

Which Discord rules does Postgale enforce?

• Text is limited to 2000 characters, embeds to Discord’s field limits and 6000 characters in all; a post over a limit is refused before it reaches Discord.
• Files are uploaded by Postgale within Discord’s default limits: 10 MB per file, 10 files per message.
• @everyone and @here do not ping unless the post asks for it explicitly.
• When Discord asks to slow down, Postgale waits the time Discord gives before retrying.
• If the webhook is deleted in Discord, the account is marked as needing reconnection and your webhook hears about it.

How do I keep a person in the loop?

• Approval: tick “Hold posts from this app for approval” when you sign in, or in the Postgale dashboard require approval for the API key the agent uses (or for the whole workspace, or one account). Posts then wait as pending approval; comment replies and moderation, direct messages, WhatsApp sends and edits to live posts wait in the same queue. A person approves, edits or rejects each one in Dashboard → Approvals; the agent’s own key or sign-in cannot approve.
• Tool annotations: every Postgale tool declares whether it only reads, writes, or publishes or sends live, deletes or spends. Clients that honour annotations ask before destructive tools run.
• Audit log: every write the agent makes is recorded with the key or the connected app, the action and the time.
• Revoking: each sign-in appears under Dashboard → Connected apps and each key under Dashboard → API keys; either can be revoked at any time.

What can’t an agent do on Discord through Postgale?

• Read messages, reply in threads or react. A webhook can only post, edit and delete its own messages.
• Read views, reactions or member counts. Webhooks get no analytics.
• Post files over 10 MB, even in boosted servers.

Common questions