Cursor MCP social media: how it connects#
Cursor MCP social media scheduling means adding SkedCast to Cursor's mcp.json, with either Cursor's native OAuth "Connect" flow or a static bearer token in a headers field. Once connected, Cursor's agent can call SkedCast's scheduling tools directly from the editor.
1. Open mcp.json#
Open Cursor's MCP settings (or edit the file directly): ~/.cursor/mcp.json for every project, or .cursor/mcp.json in one repo.
2. Add SkedCast as a remote server#
Add an entry with a url (not command/args — that form is for local stdio servers):
3. Connect#
Cursor shows a "Connect" button for OAuth-capable servers — click it and approve the SkedCast sign-in. If your workspace instead issued you a static API key, add it as a bearer header (see the code block below) rather than waiting on the OAuth flow.
mcp.json#
json
{
"mcpServers": {
"skedcast": {
"url": "https://api.skedcast.com/mcp",
"headers": { "Authorization": "Bearer ${env:SKEDCAST_API_KEY}" }
}
}
}Known limitations#
| What to know |
|---|
Cursor's native OAuth "Connect" button has open community bug reports of occasionally not starting the flow — the static-token headers form below is a reliable fallback if that happens. |
| Enterprise-managed Cursor installs may have network allow/deny lists that block outbound remote MCP connections entirely; check with your admin if the connection times out. |
Cursormcpai agents
FAQ
- Does Cursor support OAuth for remote MCP servers?
- Yes, natively — but if you hit the known "Connect button does nothing" issue, fall back to a static bearer token in `mcp.json`'s `headers` field using a SkedCast API key instead.
- What can an agent do once it's connected?
- Whatever your SkedCast role and plan allow — the connection acts as you, not with elevated access. Read posts and analytics, schedule and revise posts, and act on approvals, all through the same tools listed on the MCP hub.