Why does VS Code need a different config shape than Cursor?

VS Code keys remote servers under "servers" with an explicit "type": "http" field; Cursor and Claude Desktop key them under "mcpServers" with just a "url" — copying one file’s shape into the other client fails.

Does every client generate a JSON file I can paste?

No — only Cursor and VS Code read a config file. Claude, ChatGPT, n8n, Zapier and Make connect through their own UI, so the generator gives you the field(s) to fill in there instead.

Do I need an API key to connect?

Not for most clients — Claude, ChatGPT, n8n, Zapier and Make all authenticate over OAuth. Cursor and VS Code support a static bearer token as an optional fallback if OAuth doesn’t start.

What server URL does this generator fill in?

SkedCast’s own real remote MCP server URL — the same one every /mcp/ connection guide on this site uses.

Is the generated config validated as real JSON?

Yes — the output is built and parsed as JSON in an automated test, so a malformed snippet cannot ship silently.

Can I add the bearer token later instead of now?

Yes — leave the token field blank to get a plain URL entry, then add a "headers" block with an Authorization value yourself whenever you have a key.

Where do I put the Cursor config file?

At ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside a single repository if you only want it there.

Free tool

MCP config generator for a social media MCP server

This config generator connects your MCP client to SkedCast’s social media MCP server: it picks the right connection shape and fills in the real remote server URL. Cursor and VS Code get a real, correctly keyed JSON snippet — they use different shapes (`mcpServers` vs `servers`, and VS Code needs an explicit `"type": "http"`) — while Claude, ChatGPT, n8n, Zapier and Make get the exact field(s) to paste into their own connection screen, since none of them read a config file.

Generate your social media MCP server config

Cursor shows a native "Connect" button for OAuth once this is saved. If your workspace issued a static API key instead, add it as a bearer header below rather than waiting on OAuth.

Bearer token (optional — leave blank to use OAuth instead)

Never uploaded — everything renders locally in your browser.

Save this to ~/.cursor/mcp.json (or .cursor/mcp.json in one project):

{
  "mcpServers": {
    "skedcast": {
      "url": "https://api.skedcast.com/mcp"
    }
  }
}

How to use the MCP config generator

Pick your MCP client. Choose Cursor, VS Code, Claude, ChatGPT, n8n, Zapier or Make from the list.
Add a bearer token if you have one. Cursor and VS Code accept an optional static API key as a fallback to OAuth; the field is skipped for every other client, since they don’t support it.
Copy the real output. A JSON-config client gets a file path plus ready-to-paste JSON; a UI-connector client gets the exact field(s) to fill in.
Paste it into your client. Save the JSON to the real file path shown, or paste the field value into your client’s connector screen.
Approve the OAuth prompt. Most clients run an OAuth flow the first time a tool from the server is called — approve it to finish connecting.

Worked examples

Cursor with no token

Picking Cursor with no bearer token outputs `{"mcpServers":{"skedcast":{"url":"https://api.skedcast.com/mcp"}}}`, ready to save to `~/.cursor/mcp.json`.

VS Code uses a different key entirely

Picking VS Code outputs the same server URL under `"servers"` instead of `"mcpServers"`, with a required `"type": "http"` field Cursor’s config does not need — save it to the 2 files these clients actually read, `.vscode/mcp.json` for VS Code and `~/.cursor/mcp.json` for Cursor, and copying one shape into the other client’s file fails.

Social media MCP server config FAQ

Why does VS Code need a different config shape than Cursor?: VS Code keys remote servers under "servers" with an explicit "type": "http" field; Cursor and Claude Desktop key them under "mcpServers" with just a "url" — copying one file’s shape into the other client fails.
Does every client generate a JSON file I can paste?: No — only Cursor and VS Code read a config file. Claude, ChatGPT, n8n, Zapier and Make connect through their own UI, so the generator gives you the field(s) to fill in there instead.
Do I need an API key to connect?: Not for most clients — Claude, ChatGPT, n8n, Zapier and Make all authenticate over OAuth. Cursor and VS Code support a static bearer token as an optional fallback if OAuth doesn’t start.
What server URL does this generator fill in?: SkedCast’s own real remote MCP server URL — the same one every /mcp/<client> connection guide on this site uses.
Is the generated config validated as real JSON?: Yes — the output is built and parsed as JSON in an automated test, so a malformed snippet cannot ship silently.
Can I add the bearer token later instead of now?: Yes — leave the token field blank to get a plain URL entry, then add a "headers" block with an Authorization value yourself whenever you have a key.
Where do I put the Cursor config file?: At ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside a single repository if you only want it there.

Ready to broadcast everywhere?

Sign up free — no credit card. You land on the Free plan, and you can start a one-time 7-day Studio trial from your workspace whenever you are ready. Connect your first accounts, import a batch, and watch one post fan out across every platform.

Start free Log in to your console