Nimply
Manage social media from your AI assistant: draft, schedule and publish posts to 10 networks, run approvals, hire AI agents, create designs and check analytics.
Hosted MCP Server
npx add-mcp 'https://mcp.nimply.io/mcp'Installs into Claude Code, Codex, Cursor and more
Documentation
MCP Server
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.
2. API key header:
Authorization: Bearer nim_live_...(create one) for clients that use config files.
- 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.
2. API key header:
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 |
list_link_pages / get_link_page | Your nimply.link pages and their blocks |
add_link_block / update_link_block / publish_link_page | Add or change link-page blocks, then put the page live |
create_design / layer_image | Make an editable design from a prompt, or turn an image into editable layers (Designs). Uses AI credits |
get_design_job / cancel_design_job | Follow a design job until it's ready, or stop it |
list_designs / get_design / list_brand_kits / list_design_sizes / estimate_design_cost | Browse designs and brand kits, check the credit cost first |
create_brand_kit / import_brand_from_website / get_brand_kit / update_brand_kit | Set up a brand kit, or fill one from the brand's website (Brand kits) |
import_brand_from_sources / get_brand_import / save_brand_import | Make a brand kit from several sources at once: website, text, a PDF brand book, a connected channel, images. Uses AI credits |
list_style_post_candidates / add_style_examples / remove_style_example / learn_brand_style / get_brand_style / set_brand_style_rules | Teach a brand kit your look from your own posts and images, and set your own design rules. Learning uses AI credits |
list_agent_templates / list_agents / get_agent | Browse the agent gallery and your agents (Agents). MCP server 0.7.0 |
hire_agent / update_agent / set_agent_status / remove_agent | Hire an agent (the assistant asks only for missing settings), change it, pause or resume it, remove it. MCP server 0.7.0 |
run_agent / get_agent_run / cancel_agent_run | Run an agent now and follow the run. Uses AI credits; what it makes waits for approval. MCP server 0.7.0 |
list_automation_step_types / list_automation_recipes / list_automations / get_automation | Browse building blocks, recipes and your automations (Automations). MCP server 0.7.0 |
create_automation / create_automation_from_recipe / update_automation / delete_automation | Build an automation as a draft, change it, or delete it. MCP server 0.7.0 |
test_automation / set_automation_status / run_automation / get_automation_run | Test with sample data, switch on or off, run once, and check a run. MCP server 0.7.0 |
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?"
- "Make an Instagram post for our weekend sale in our brand colours."
- "Turn this image into an editable design."
- "Learn our brand look from our best Instagram posts."
- "Hire a LinkedIn ghostwriter for my page, then run it and show me the drafts."
- "Every morning, have my Trend Scout find a topic and my Designer make a carousel."
Notes
- Rate limits and plan quotas apply exactly as for direct API use — the MCP server is a thin wrapper over the REST API.
- Designs are asynchronous too: the agent polls
get_design_jobuntil it isdone, then shows you the preview and the edit link. - Agents never publish: what
run_agentmakes waits for approval, and the assistant approves a post only when you say so. Automations are created as drafts; the assistant tests them and switches them on only after you confirm. Nothing in the MCP server reads or sends inbox messages. - 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.
[
Data model
Workspaces, channels, posts, and media — the mental model in five minutes.
](https://developer.nimply.io/docs/data-model)[
Integrations
Connect Nimply to your AI assistant, editor, or automation platform