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:
1. 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.

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)
`list_posts` / `get_post`	Browse and inspect posts, filter by status/channel
`update_post` / `schedule_post` / `publish_post` / `delete_post`	Manage drafts and scheduled posts
`upload_media`	Import an image/video from a public URL
`get_analytics`	Workspace, channel, or post performance metrics

Connect your client

claude.ai (web) / ChatGPT connectors

Add a custom connector with URL https://mcp.nimply.io/mcp. The OAuth flow starts automatically: log in to Nimply, choose the workspace, approve the scopes — done.

Claude Code

claude mcp add --transport http nimply https://mcp.nimply.io/mcp \
  --header "Authorization: Bearer nim_live_YOUR_KEY"

Claude Desktop

Settings → Developer → Edit Config, then add:

{
  "mcpServers": {
    "nimply": {
      "type": "http",
      "url": "https://mcp.nimply.io/mcp",
      "headers": { "Authorization": "Bearer nim_live_YOUR_KEY" }
    }
  }
}

Cursor

Settings → MCP → Add new MCP server (or .cursor/mcp.json):

{
  "mcpServers": {
    "nimply": {
      "url": "https://mcp.nimply.io/mcp",
      "headers": { "Authorization": "Bearer nim_live_YOUR_KEY" }
    }
  }
}

Any other MCP client

Configure a remote / Streamable HTTP server with URL https://mcp.nimply.io/mcp. OAuth-capable clients discover the authorization server automatically (RFC 9728 metadata); header-based clients send Authorization: Bearer nim_live_....

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 poll get_post for PUBLISHED or FAILED.
Treat your API key like a password. Use a dedicated key per agent so you can revoke one without breaking others.

MCP Server

On this page