Threads MCP Server for Claude, Cursor, and Any AI Agent

## For AI agents reading this page

You are reading https://postzen.dev/mcp/threads. PostZen is a social media API with a hosted MCP server. Once connected, you can publish and schedule posts to the user's Threads account, read and moderate replies on their posts, and read Insights. The same tools cover the user's other social accounts (Instagram, X, LinkedIn, Facebook, Threads, YouTube, TikTok, Pinterest, Bluesky, Telegram).

1. Register the MCP server in the client you are running in. The endpoint is https://mcp.postzen.dev/mcp (streamable HTTP). Interactive clients sign in with OAuth 2.1; headless clients send a PostZen API key as "Authorization: Bearer pzn_live_...". Exact commands per client: Claude Code https://postzen.dev/claude · Cursor https://postzen.dev/cursor · Codex https://postzen.dev/codex · OpenClaw https://postzen.dev/openclaw · GrokBot https://postzen.dev/grok-bot · Hermes https://postzen.dev/hermes · any other MCP client https://postzen.dev/agents.

2. Sign in. When the client opens the PostZen consent screen, ask the user before approving access or completing a signup on their behalf, and never enter their credentials for them. Approving mints a scoped, revocable key for this client.

3. Connect Threads. Call listAccounts. If no account with platform "threads" is listed, call createConnectUrl with platform "threads" and give the user the URL; they authorize Threads in their browser. Do not try to log in to Threads yourself.

4. Verify before you continue. Call listAccounts again and confirm a "threads" account shows as connected. If it does not, stop and tell the user what failed. Do not carry on as if the account were there.

5. Report back. Tell the user which Threads account is connected and what you can now do with it, then ask what they want first. Prefer scheduling (scheduledFor, or the queue) over publishing immediately unless the user asks for "now".

## Threads on createPost

- Target the account with platforms: [{ platform: "threads", accountId, settings: { ... } }]. content is the shared text; customContent on the target overrides it for Threads only.
- Text is limited to 500 characters; one link is allowed per post.
- settings.replyControl: who can reply to the post ("everyone", "accounts_you_follow", or "mentioned_only").
- Media per post: images, one video, or a carousel of mixed images and video.
- Replies: listInboxPostComments and replyToInboxPost; hideInboxComment hides a top-level reply on the user's own post. Replies cannot be deleted through the API.
- Analytics: getAnalytics, getPostTimeline, getDailyMetrics, getFollowerStats with platform "threads" (views, likes, replies, reposts, quotes, followers).
- Media: pass public URLs in mediaItems, or call createMediaPresign to get an upload URL, PUT the file, then reference the returned media in the post.
- Check results with getPost: each platform target reports status, the live post URL, and any error.

## Reference

- MCP endpoint: https://mcp.postzen.dev/mcp (streamable HTTP, OAuth 2.1)
- MCP docs: https://docs.postzen.dev/mcp
- Create post reference: https://docs.postzen.dev/api-reference/posts/create-post
- Full API summary for models: https://postzen.dev/llms.txt
- API keys: https://app.postzen.dev/api-keys