Using SuperSocial MCP with Cursor IDE

Why Use SuperSocial in Cursor?

Cursor is an AI-powered code editor that supports the Model Context Protocol (MCP). By adding SuperSocial as an MCP server in Cursor, you give the built-in AI assistant access to your messaging accounts — LinkedIn, WhatsApp, Instagram, Telegram, Gmail, and Outlook — without ever leaving your editor.

This means you can read incoming messages, draft replies, search conversations, and send follow-ups while you work. No tab switching, no context loss. Just ask Cursor's AI and it handles the rest.

This setup works with any Cursor plan, including the free tier.

Prerequisites

Before you start, make sure you have the following:

• Cursor IDE installed on your machine (macOS, Windows, or Linux)
• Node.js installed — the configuration uses npx to run the MCP bridge, so Node.js must be available in your system PATH
• A SuperSocial account — sign up at app.getsupersocial.me if you have not already. The free trial works perfectly for testing the Cursor integration.
• At least one connected messaging account — connect LinkedIn, WhatsApp, or another platform from your SuperSocial dashboard before proceeding

Not sure if Node.js is installed? Open a terminal and run node --version. If you see a version number, you are good to go. If not, download it from nodejs.org.

Step 1: Open the MCP Configuration File

Cursor stores its MCP server configuration in a JSON file on your system. The file location depends on your operating system:

• macOS / Linux: ~/.cursor/mcp.json
• Windows: %USERPROFILE%\.cursor\mcp.json

Open this file in any text editor. If the file does not exist yet, create it. If it already exists and contains other MCP server entries, you will add SuperSocial alongside them in the next step.

Step 2: Add the SuperSocial MCP Server

Add the following configuration to your mcp.json file. If the file is empty or does not exist, paste the entire block below:

{
  "mcpServers": {
    "supersocial": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://app.getsupersocial.me/mcp"]
    }
  }
}

If you already have other MCP servers configured, add the "supersocial" entry inside the existing "mcpServers" object. For example:

{
  "mcpServers": {
    "some-other-server": {
      "command": "...",
      "args": ["..."]
    },
    "supersocial": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://app.getsupersocial.me/mcp"]
    }
  }
}

Make sure the JSON is valid — watch out for missing commas between entries or trailing commas after the last entry.

Step 3: Restart Cursor

After saving the configuration file, fully quit and reopen Cursor. A simple window reload is not enough — Cursor loads MCP server configurations at startup, so a full restart is required for the changes to take effect.

Step 4: Authenticate with SuperSocial

The first time Cursor's AI tries to use a SuperSocial tool, it will prompt you to log in. A browser window will open asking you to authenticate with your SuperSocial account. Use the same email address you used when you created your SuperSocial account.

Once you log in, the session is cached and you will not need to authenticate again for subsequent requests. If your session expires, Cursor will prompt you to log in again automatically.

Step 5: Start Using Messaging in Cursor

With everything connected, open Cursor's AI chat (Cmd+L on macOS, Ctrl+L on Windows) and try a few commands:

1. "Show me my latest LinkedIn messages" — pulls in your recent LinkedIn conversations
2. "Summarize my unread WhatsApp messages" — get a quick overview without leaving your editor
3. "Reply to the last message from Sarah on LinkedIn saying I will review the PR today" — send a message directly from Cursor
4. "Search all my conversations for messages about the deployment issue" — search across platforms in one query
5. "Draft a follow-up email to the client who asked about pricing" — let AI compose context-aware replies

Cursor's AI will automatically detect the available SuperSocial tools and use them to fulfill your requests. You stay in your code editor the entire time.

Troubleshooting

Cursor does not detect the MCP server

Double-check that your mcp.json file is valid JSON. Even a single missing comma or extra bracket will prevent Cursor from parsing the configuration. You can validate your JSON at jsonlint.com. After fixing any issues, restart Cursor completely.

The npx command is not found

This means Node.js is either not installed or not in your system PATH. Install Node.js from nodejs.org (the LTS version is recommended). After installing, restart your terminal and Cursor so the updated PATH is picked up.

Authentication window does not appear

Make sure your default browser is not blocking pop-ups from SuperSocial. Try opening https://app.getsupersocial.me/mcp directly in your browser to verify you can reach the server. If you are behind a corporate firewall or VPN, check that outbound HTTPS connections to app.getsupersocial.me are allowed.

Tools are available but return errors

Verify that you have at least one messaging account connected in your SuperSocial dashboard. The MCP tools need connected accounts to fetch and send messages. Also confirm that your free trial has not expired — if it has, upgrade to the Pro plan to restore access.

What Comes Next

Now that SuperSocial is running in Cursor, you have a unified messaging assistant inside your development environment. Here are some ideas for getting the most out of it:

• Morning standup prep — ask for a summary of all messages received overnight across every platform
• Quick replies between coding sessions — respond to clients and colleagues without leaving your editor
• Cross-platform search — find that conversation about a bug report, whether it came through LinkedIn, WhatsApp, or email
• Scheduled messages — draft a message now and schedule it for later

For a complete list of everything your AI can do through SuperSocial, see the MCP Tools Reference.