Cursor MCP Social Media — Schedule Posts from Your Editor | Nimply

Name: Nimply
Author: Nimply

If you work in Cursor, the agent already sits inside your context: the diff you just merged, the changelog you just wrote, the PR description that explains why any of it matters. The announcement post is usually written from exactly that material — and then you tab out to a social media dashboard and retype it.

Connecting Nimply closes that gap. One entry in mcp.json gives Cursor's agent tools for your real posting queue: it can list your connected channels, draft platform-appropriate copy from whatever is in the editor, and schedule it to Instagram, Facebook, TikTok, YouTube, LinkedIn, X, Pinterest, or Threads. Shipping the code and announcing it become one workflow.

What is Cursor?

Cursor is an AI-first code editor built around an agent that can plan and execute multi-step work — reading your codebase, editing files, running commands. Because it supports the Model Context Protocol (MCP), that same agent can operate external services: any tool registered in mcp.json becomes something the agent can call mid-task, alongside its editing and terminal abilities.

Nimply's MCP server is remote, so there is nothing to install or run locally — Cursor connects straight to https://mcp.nimply.io/mcp with an API key from your workspace. The key is scoped to that single workspace and its permissions, which means an agent acting on your behalf can only ever do what you have explicitly allowed, and you can revoke access instantly.

What Cursor can do with Nimply connected

Ship the release post with the release

Merge the PR, then ask the agent to announce it. It has the diff and the changelog in context, so the post it drafts describes what actually changed — and it can queue that post for your next free slot on LinkedIn or X before you close the tab.

Turn docs and changelogs into a content queue

Point the agent at a changelog file or a docs page you just wrote and ask for a batch of posts. It can produce a different angle per platform and schedule each one through Nimply, filling a week of content from work you already did.

Build against the Nimply API with live calls

If you're integrating Nimply's public API into your own product, the MCP connection doubles as a workbench. Ask the agent to list channels or create a test draft and compare the real responses against the code it's writing — no separate REST client needed.

Keep a human in the loop with drafts and approvals

Nothing has to go live automatically. Tell the agent to save everything as a draft, or to submit posts through Nimply's approval workflow so a teammate reviews before publishing. The agent does the assembly; a person makes the call.

Connect Cursor to Nimply

Setup is one JSON entry. You need a Nimply workspace with at least one channel connected and an API key from Settings → Developers.

1
Create a Nimply API key
In Nimply, open Settings → Developers and create an API key. Keys start with nim_live_, are scoped to one workspace, and can be revoked at any time without affecting anything else.
2
Add the server to mcp.json
Open Cursor Settings → MCP → Add new MCP server, or edit the config file directly — .cursor/mcp.json inside your project, or ~/.cursor/mcp.json to make it available everywhere:
mcp.json
```
{
  "mcpServers": {
    "nimply": {
      "url": "https://mcp.nimply.io/mcp",
      "headers": {
        "Authorization": "Bearer nim_live_YOUR_KEY"
      }
    }
  }
}
```
3
Keep the key out of version control
Don't commit a config that contains your key. Use the global ~/.cursor/mcp.json, or keep the project-level file untracked. If the key ever leaks, revoke it from Settings → Developers and issue a new one.
4
Check the green dot and try it
Nimply appears in the MCP list with a green dot and its tools listed. Then ask the agent: "Use nimply to list my connected channels" or "Draft a post announcing the feature in this PR and schedule it for the next free slot."

Frequently asked questions

Which social platforms can Cursor post to through Nimply?

All channels connected to your Nimply workspace: Instagram, Facebook, TikTok, YouTube, LinkedIn, X (Twitter), Pinterest, and Threads. The agent works with your actual accounts and posting schedule, not a simulation.

Do I need to run an MCP server locally for Cursor?

No. Nimply hosts the server at https://mcp.nimply.io/mcp and Cursor connects to it directly over HTTP with your API key in the Authorization header. There is nothing to install, update, or keep running.

Will the agent publish posts without asking me?

Only if you tell it to. You can instruct it to save drafts instead of publishing, or route posts through Nimply's approval workflow so nothing goes live without a human sign-off. The API key's permissions also cap what the agent can do at all.

The server shows a red dot in Cursor — what now?

That's usually a typo in the URL or the Authorization header. Fix the config, then toggle the server off and on. A 401 means the key was revoked or mis-pasted; a valid key always starts with nim_live_.

Should the config live in the project or globally?

Global (~/.cursor/mcp.json) is the safer default because the key never sits inside a repository. Use the project-level .cursor/mcp.json only if you keep it untracked — for example when different projects should post to different Nimply workspaces.