MCP Server
Connect Claude, Cursor, and other AI agents to Nimply
Nimply ships a remote MCP (Model Context Protocol) server, so any MCP-capable AI agent can plan, create, schedule, and measure your social content conversationally.
- Endpoint:
https://mcp.nimply.io/mcp(Streamable HTTP) - Auth — two options:
- OAuth (recommended): in clients with connector support (claude.ai, ChatGPT, Claude Desktop), just add the server URL — you'll be redirected to Nimply to log in, pick a workspace, and approve the permissions. No keys to copy.
- API key header:
Authorization: Bearer nim_live_...(create one) for clients that use config files.
Either way, the agent acts with exactly the permissions you granted: read-only lets it analyze but not post; posts:write + posts:publish let it schedule and publish. Revoke access anytime (delete the key, or revoke the app from workspace settings).
Tools
| Tool | What it does |
|---|---|
list_channels | Connected accounts, ids, and connection health |
get_posting_schedule | A channel's posting time slots per weekday |
create_post | Create posts (draft / next free slot / now / at a time) |
create_youtube_video / create_tiktok_post / create_pinterest_pin / create_linkedin_post | Platform-specific posting with the full option set (YouTube visibility/category, TikTok privacy and disclosure, Pinterest board/link/alt text, LinkedIn visibility) |
get_pinterest_boards / get_tiktok_creator_info | Board list and TikTok posting constraints that feed the platform tools |
list_posts / get_post | Browse and inspect posts, filter by status/channel |
update_post / schedule_post / unschedule_post / publish_post / delete_post | Manage drafts and scheduled posts |
upload_media | Import an image/video from a public URL |
create_media_upload / complete_media_upload | Direct binary upload via presigned URL — for agents that can run an HTTP PUT (CLIs, IDEs) |
get_analytics | Workspace, channel, or post performance metrics |
request_approval / approve_post / reject_post | Client sign-off workflow for agencies |
Connect your client
Every supported platform has a dedicated step-by-step guide with the exact config for that client:
| claude.ai | Claude Desktop | Claude Code |
| ChatGPT | Cursor | VS Code |
| Windsurf | Codex CLI | Gemini CLI |
| Perplexity | Raycast | Any MCP client |
The 30-second version for OAuth-capable clients (claude.ai, ChatGPT, Claude Desktop): add a custom connector with URL https://mcp.nimply.io/mcp, log in to Nimply, choose a workspace, approve — done. Config-file clients use the same URL plus an Authorization: Bearer nim_live_... header.
Browse all integrations — including Zapier, Make, and n8n for no-code automation.
Try it
Once connected, ask your agent things like:
- "What channels do I have connected, and are any unhealthy?"
- "Draft a week of posts about our product launch and schedule them into the next free slots."
- "Which of my posts performed best last month?"
Notes
- Rate limits and plan quotas apply exactly as for direct API use — the MCP server is a thin wrapper over the REST API.
- Publishing is asynchronous: after "publish now" the post is
SCHEDULED; the agent should pollget_postforPUBLISHEDorFAILED. - Treat your API key like a password. Use a dedicated key per agent so you can revoke one without breaking others.