# How to connect Cursor, VS Code or Windsurf to DunSocial MCP

> Every editor uses the same URL but a different key: mcpServers for Cursor, servers with type http for VS Code, serverUrl for Windsurf & context_servers for Zed. Add the snippet, then authorize in the browser when the editor asks.

Updated: 2026-10-05.

## One URL, different config shapes

Every client points at the same endpoint. What changes is the JSON key each editor expects. Getting that key wrong is the most common reason a connection doesn't appear.

```
https://api.dunsocial.com/api/mcp
```

## Cursor

Add this to `~/.cursor/mcp.json`, or to a project's `.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "dunsocial": {
      "url": "https://api.dunsocial.com/api/mcp"
    }
  }
}
```

Cursor opens DunSocial to authorize the first time it connects.

## VS Code

Add this to `.vscode/mcp.json` in your workspace. The top-level key is `servers`, not `mcpServers`, & it needs `"type": "http"`:

```json
{
  "servers": {
    "dunsocial": {
      "type": "http",
      "url": "https://api.dunsocial.com/api/mcp"
    }
  }
}
```

## Windsurf

Windsurf uses `serverUrl` instead of `url`:

```json
{
  "mcpServers": {
    "dunsocial": {
      "serverUrl": "https://api.dunsocial.com/api/mcp"
    }
  }
}
```

DunSocial's endpoint is identical here. Only the key name differs, which is a Windsurf convention.

## Zed & Grok

Zed nests the URL under `context_servers` in `settings.json`:

```json
{
  "context_servers": {
    "dunsocial": {
      "settings": {
        "url": "https://api.dunsocial.com/api/mcp"
      }
    }
  }
}
```

Grok takes the endpoint as a custom MCP connector or connector URL, with no JSON file. Paste the URL & approve in the browser when prompted.

These snippets match what DunSocial shows under Settings → MCP for each client.

## Check that the tools loaded

Open the assistant panel & confirm DunSocial's tools are listed. DunSocial exposes 53 tools across posts, drafts, media, memory & workspaces, so a list that is empty or very short usually means the authorization didn't finish.

Ask a read-only question first, such as listing your connected accounts, before trying to schedule anything.

## If it doesn't connect

Check the key name for your editor first, then confirm the file is where the editor reads it. A user-level file applies everywhere & a project-level file applies only in that project.

DunSocial uses OAuth, so there's no token to add to these files. Don't paste a bearer token into the config: new setups don't accept tokens in the URL, & the connection is designed to be approved in the browser.

## Related guides

- [How to connect Claude to DunSocial over MCP](https://www.dunsocial.com/hub/dunsocial-mcp-guides/how-to-connect-claude-to-dunsocial-mcp.md)
- [What can an AI assistant do with DunSocial MCP tools?](https://www.dunsocial.com/hub/dunsocial-mcp-guides/what-can-an-ai-assistant-do-with-dunsocial-mcp-tools.md)
- [How to connect an AI agent to your social accounts safely](https://www.dunsocial.com/hub/social-media-automation-for-developers/how-to-connect-an-ai-agent-to-your-social-media-accounts-safely.md)
- [CLI vs API vs MCP: which one should you use?](https://www.dunsocial.com/hub/social-media-automation-for-developers/cli-vs-api-vs-mcp-which-one-should-you-use.md)

## About this document

This is the Markdown representation of https://www.dunsocial.com/hub/dunsocial-mcp-guides/how-to-connect-cursor-vs-code-or-windsurf-to-dunsocial-mcp. The HTML version of the same page is at the same URL. You can also request Markdown from any page by sending `Accept: text/markdown`.

Machine-readable summary of the whole site: https://www.dunsocial.com/llms.txt

## Company

- Product: DunSocial, https://www.dunsocial.com
- Legal entity: THISUX PRIVATE LIMITED, Chennai, Tamil Nadu, India
- Support: support@dunsocial.com
- Open the app: https://app.dunsocial.com/login