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?

No. Every client signs in with OAuth: you approve access in a browser once. SkedCast’s MCP server does not accept API keys. API keys are for the REST API.

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

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

Save this file. Cursor opens a browser sign-in (OAuth) the first time it uses the server. SkedCast’s MCP server does not accept API keys, so there is no token to add.

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

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

How do you 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.

What does it look like in practice?

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.