Cursor MCP server setup for social media publishing and scheduling
A Cursor MCP server lets you publish, schedule, reply, and read analytics across your social accounts without leaving Cursor.
{
"mcpServers": {
"social-media": {
"url": "{{MCP_BASE_URL}}/mcp"
}
}
}{"social-media":{"url":"{{MCP_BASE_URL}}/mcp"}}
The captured setup described 36 MCP tools across 9 platforms with Secure OAuth. This guide covers the exact .cursor/mcp.json configuration, the Secure OAuth sign-in approval step, and the verification sequence using MCP tools and list_integrations before you use social media publishing or scheduling.
What this setup does
This setup connects Cursor to a hosted MCP server so an agent working in your repository can help with social media publishing, scheduling, replies, and analytics. The agent can write its own configuration by reading the instructions on this page, adding the server entry to .cursor/mcp.json, and then pausing when you need to approve the secure sign-in. That pause is intentional: configuration can be automated, but authentication should remain a user-approved step.
Input contract: exact .cursor/mcp.json structure and fields
Create or update .cursor/mcp.json using the exact mcpServers structure shown in the configuration example. The file contains a single server entry whose url points to the hosted MCP endpoint, and it does not contain an Authorization header. Keep the structure minimal: the top-level mcpServers field, the server name, and the url field are the only parts required for this connection step. If the file already exists, merge the new server entry into the existing mcpServers object rather than replacing unrelated entries.
Step-by-step connection flow with secure sign-in approval
After writing the configuration, do not add an Authorization header and do not proceed as if authentication is complete. Stop and ask the user to approve the sign-in from Cursor MCP settings. The sign-in uses Secure OAuth, so the user completes approval in the editor rather than pasting credentials into the configuration file. Only continue once that approval step is done.
Verification: confirm connection, confirm tools listed, call list_integrations
Confirm that the server is connected and that its MCP tools are listed before continuing with any social media task. Listing the tools is the verification that Cursor has loaded the server configuration and can reach the hosted endpoint. After that confirmation, call list_integrations and report which social accounts are available. That result is your working inventory: it tells you which accounts can be used for publishing, scheduling, replies, and analytics, and it prevents assumptions about accounts that are not actually connected.
Scheduling preference and when to publish immediately
Prefer scheduling over immediate publishing unless the user explicitly asks to publish now. Scheduling gives you a review point before content goes live and matches the default instruction for agent-assisted work. Treat immediate publishing as an exception that requires an explicit request, not as the default outcome of a drafting or planning task. When the user asks for scheduling, confirm the intended account from the list_integrations result and the intended time before creating the scheduled item.
Failure matrix and troubleshooting checklist
Work through the failure matrix in order. If the configuration file is missing or malformed, fix .cursor/mcp.json first. If sign-in has not been approved, complete the Secure OAuth approval from Cursor MCP settings. If the server is connected but tools are not listed, re-check the url value and reload the MCP settings. If tools are listed but list_integrations returns no accounts, treat the connection as working and the account inventory as empty, then connect a social account before attempting publishing, scheduling, replies, or analytics.
| Check | Expected result | If it fails |
|---|---|---|
| .cursor/mcp.json exists and contains mcpServers | Server entry is present with a url field and no Authorization header | Create or update the file and merge the server entry into mcpServers |
| Secure OAuth sign-in approved from Cursor MCP settings | User approval is complete before continuing | Stop and ask the user to approve sign-in; do not add credentials to the config |
| Server connected and MCP tools listed | Tools are visible in Cursor MCP settings | Re-check the url value, reload MCP settings, and confirm the file is valid JSON |
| list_integrations called | Available social accounts are reported | If no accounts are returned, connect a social account before publishing, scheduling, replies, or analytics |
Staging checklist based on the captured setup instructions; runtime behavior requires implementation-stage verification.
| Symptom | Likely cause | Action |
|---|---|---|
| Config file missing or invalid JSON | File was not created or was edited incorrectly | Recreate .cursor/mcp.json with the exact mcpServers structure |
| Sign-in not approved | Secure OAuth approval step was skipped | Approve sign-in from Cursor MCP settings; do not add an Authorization header |
| Server connected but MCP tools not listed | Configuration not loaded or endpoint unreachable | Verify the url field, reload MCP settings, and confirm tools are listed |
| Tools listed but list_integrations returns no accounts | No social accounts connected yet | Connect a social account, then call list_integrations again |
| User asked for a draft or plan but content published immediately | Scheduling preference was not applied | Use scheduling by default; publish immediately only on explicit request |
Troubleshooting guidance derived from the setup steps; platform-specific errors are not covered by supplied evidence.
Frequently asked questions
What is the exact setup sequence for a Cursor MCP server?
Create or update .cursor/mcp.json with the mcpServers structure shown in the configuration example, without adding an Authorization header. Then approve the secure sign-in from Cursor MCP settings, confirm the server is connected and its MCP tools are listed, and call list_integrations to report available social accounts.
Should I add an Authorization header to the MCP configuration?
Do not add an Authorization header to the configuration. Stop and ask the user to approve the sign-in from Cursor MCP settings, using Secure OAuth, before continuing.
Should posts be scheduled or published immediately by default?
Prefer scheduling over immediate publishing unless the user explicitly asks to publish now. Use scheduling as the default path and treat immediate publishing as an explicit exception.
What should I check if the MCP tools are not listed or no accounts are returned?
Check that .cursor/mcp.json exists and contains mcpServers, confirm sign-in was approved, confirm the server shows as connected with its tools listed, and then call list_integrations. If no accounts are returned, the connection may be working but no social accounts are available to use yet.