Connect Claude to PostNext via the Model Context Protocol. Schedule posts, draft threads, audit your queue, and generate content across X, Instagram, LinkedIn, Threads, and TikTok — all from inside a Claude conversation.
The MCP server is hosted and free to connect. You only need a PostNext account.
- Server URL:
https://mcp.postnext.io/api - Status: production, v1.5.1
- Tools: 21 · Resources: 4 · Prompts: 4
PostNext exposes its social media management API as a Model Context Protocol server. When you connect it to Claude (desktop, web, or any MCP-aware client), Claude can:
- See your connected social channels and current team
- Read your brand profile (voice, themes, hashtags) so generated posts sound like you
- Draft, edit, schedule, and cancel posts
- Audit your scheduled queue for duplicates, overload, or gaps
- Look up post metrics and account health
All actions happen against your PostNext account through your own auth token — PostNext sees what you authorize, nothing more.
You need a PostNext account. Sign up free at postnext.io — no API key required for the Claude flows below; OAuth handles auth.
Visit postnext.io/mcp/connect and click Open in Claude Desktop. The deep link configures the MCP server for you and walks you through the OAuth grant.
Edit your Claude Desktop config (path varies by OS — see Anthropic's docs) and add:
{
"mcpServers": {
"postnext": {
"url": "https://mcp.postnext.io/api",
"transport": "http"
}
}
}Restart Claude Desktop. On first tool use, Claude opens a browser tab for the OAuth grant; once approved, the PostNext tools appear in the tools picker.
Go to claude.ai → Connectors → Add custom connector and
paste https://mcp.postnext.io/api. OAuth flow handles auth.
For scripts, agents, or non-Claude clients that don't do OAuth, generate
an API key at
postnext.io/account/api-keys and pass
it as Authorization: Bearer apikey_<uuid> on every request.
You: What's scheduled for this week?
Claude: [calls list_scheduled_posts, summarizes]
You: Draft a thread about the new MCP launch.
Claude: [reads postnext://brand-profiles/active for voice,
calls create_post_draft with a thread shape]
You: Audit my queue for the next 14 days.
Claude: [invokes the audit-queue prompt, flags duplicates and gaps]
| Category | Tools |
|---|---|
| Account + plan | get_plan, get_plan_limits, get_account_health |
| Teams | list_teams, set_current_team |
| Channels | list_connected_accounts, connect_channel |
| Drafts | create_post_draft, update_post_draft, list_drafts, delete_draft |
| Schedule | schedule_post, cancel_scheduled_post, list_scheduled_posts, get_publish_status |
| Posts | get_post, search_posts, get_post_metrics |
| Analytics | get_best_time_to_post, get_post_metrics |
| Brand | update_brand_profile |
| Meta | search_tools |
Most read-only tools work on every plan. A couple of analytics-flavored
reads (get_account_health, get_best_time_to_post) need a paid plan.
Mutating tools (create, schedule, channel-connect, draft-edit,
brand-profile update) require a paid plan with available quota. See
postnext.io/pricing for current limits.
MCP resources are read-on-demand context pulls. Claude reads these to ground its replies without re-asking you.
| URI | What it returns |
|---|---|
postnext://account/summary |
Plan, usage this month, channels connected |
postnext://teams/current |
Currently-selected team |
postnext://channels/connected |
All connected social handles for the active team |
postnext://brand-profiles/active |
Brand voice, themes, hashtags |
Pre-built multi-step prompts you can invoke from any MCP client:
| Name | What it does |
|---|---|
weekly-plan |
Builds a 7-day content plan grounded in your brand profile |
draft-thread |
Drafts a 5–10 post thread from a topic or URL |
audit-queue |
Walks the next N days of scheduled posts, flags duplicates / overload / gaps. Read-only |
channel-sweep |
Reviews which platforms you have connected and recommends gaps to fill |
| Endpoint | Status | Notes |
|---|---|---|
https://mcp.postnext.io/api |
Canonical | Use this |
https://postnext.io/mcp/api |
Deprecated | Backward-compat through 2026-06-08; do not use for new integrations |
The server reports version: 1.5.1 on initialize. Breaking changes are
versioned; non-breaking additions (new tools, resources) ship without a bump.
- Two auth modes: OAuth 2.0 (Claude Desktop and claude.ai connector flows)
or API key (
Bearer apikey_<uuid>, manage at postnext.io/account/api-keys) - Tokens are revocable at any time from your account dashboard
- Tool calls are rate-limited per token and per IP; live limits are
exposed in
RateLimit-*response headers - Security disclosure: postnext.io/security ·
RFC 9116
security.txtpublished at/.well-known/security.txt - Privacy: postnext.io/privacy — MCP data flow detailed under "MCP Server and AI Assistant Access"
Worked examples for common workflows. Each is a paste-ready prompt with notes on what Claude does under the hood.
- Weekly content plan — plan a week of posts across your connected channels, grounded in your brand voice
- Draft a thread from an article — turn a URL into a 5–10 post thread in your voice
- Audit the scheduled queue — read-only walk through your next N days, flagging duplicates / overload / gaps
- Channel-connection sweep — review coverage against your brand strategy, connect the missing ones
Full hosted reference at postnext.io/mcp/docs. Repo-local reference (handy for offline / fork use):
- Quickstart — connect from Claude Desktop, claude.ai, or a programmatic client
- Tool reference — all 21 tools, gating, error envelopes
- Resource reference — the 4 MCP resources Claude reads on demand, with example payloads
- Prompt reference — the 4 named workflows + argument schemas
MIT — documentation and examples are free to copy, fork, and adapt. The MCP server itself is hosted by PostNext; see Terms of Service.
- Marketing site: postnext.io
- Pricing: postnext.io/pricing
- MCP landing: postnext.io/mcp
- Account dashboard: app.postnext.io
- API keys: postnext.io/account/api-keys
- Support: contact@postnext.io
Built by the team at PostNext. Pull requests on these docs welcome.