Postproxy

Postproxy MCP Server

MCP (Model Context Protocol) server for integrating Postproxy API with Claude Code. This server provides tools for publishing posts, checking statuses, and managing social media profiles through Claude Code.

Installation

Global Installation

npm install -g postproxy-mcp

Local Installation

npm install postproxy-mcp

Claude Code stores MCP server configuration under ~/.claude/plugins/. After installing postproxy-mcp, Claude will automatically detect the server on restart.

Configuration

Register MCP Server

After installing postproxy-mcp, register it with Claude Code using the claude mcp add command:

claude mcp add --transport stdio postproxy-mcp --env POSTPROXY_API_KEY=your-api-key --env POSTPROXY_BASE_URL=https://api.postproxy.dev/api -- postproxy-mcp

Replace your-api-key with your actual Postproxy API key.

The configuration will be automatically saved to ~/.claude/plugins/. After running this command:

1. Restart your Claude Code session
2. Test the connection by asking Claude: "Check my Postproxy authentication status"
3. If tools are available, Claude will be able to use them automatically

Alternative: Interactive Setup

For non-technical users, you can use the interactive setup command:

postproxy-mcp setup

or

postproxy-mcp-setup

This will guide you through the setup process step by step and register the server using claude mcp add automatically.

Available Tools

Authentication Tools

auth_status

Check authentication status, API configuration, and workspace information.

Parameters: None

Returns:

{

"authenticated": true, "base_url": "https://api.postproxy.dev/api", "profile_groups_count": 2 }

Account Overview

summary_get

Answer "what's the status?" in one call — an activity snapshot for a time window instead of separate history_list / comments_list / dm_chats_list round trips.

Parameters:

• window (string, optional): 24h (default), 7d, or 30d
• from (string, optional): ISO 8601 timestamp or bare date starting an explicit range. Overrides window, and the *_previous counts come back null
• to (string, optional): End of the explicit range. Defaults to now when only from is given
• profile_group_id (string, optional): Report on a single group. Omit to cover every group the key can reach

Returns:

{

"window": { "label": "24h", "from": "2026-08-17T09:00:00Z", "to": "2026-08-18T09:00:00Z", "previous_from": "2026-08-16T09:00:00Z", "backlog_from": "2026-07-19T09:00:00Z" }, "posts": { "published": 4, "published_previous": 3, "failed": 1, "scheduled_ahead": 6, "next_scheduled_at": "2026-08-18T14:00:00Z", "by_platform": { "instagram": { "published": 4, "failed": 0 } } }, "engagement": { "total": { "impressions": 48210, "likes": 1204 }, "by_platform": { "instagram": { "impressions": 31002, "likes": 900 } }, "posts_with_insights": 14 }, "comments": { "received": 96, "received_previous": 71, "awaiting_reply": 12, "by_platform": { "instagram": 61 } }, "reviews": { "received": 7, "received_previous": 4, "awaiting_reply": 3 }, "dms": { "inbound": 41, "outbound": 33, "chats_awaiting_reply": 5, "reply_window_closing": 2 }, "api": { "calls": 812, "calls_previous": 640 } }

Notes:

• Post counts are posts, so a post sent to three networks counts once and a thread counts once. by_platform counts per-network deliveries, so a 3-item X thread is 3 under twitter.
• `engagement` is lifetime-to-date for posts published in the window, not engagement earned during it — it sums each post's newest stats snapshot. A post published minutes ago may have no snapshot yet and won't be in posts_with_insights. Keys are the normalized metrics listed in Stats Fields by Platform.
• The `awaiting_reply` counts describe current state, not the window — they don't change when you change window. They look back 30 days, returned as window.backlog_from. A comment counts as replied only when the reply came from you (via Postproxy or the profile itself); chats_awaiting_reply is derived from message timestamps, since Postproxy has no read/unread state.
• reply_window_closing counts chats with under 6 hours of their 24h messaging window left. Networks without a window (Telegram, Bluesky) are excluded.
• engagement is null when insights are off for the account; dms is null when DMs are off.
• Scoped like every other tool: a group-scoped key reports only its group.

Profile Management

profile_groups_list

List all profile groups accessible with your API key. Profile groups are organizational containers (e.g. per brand or client) that hold related profiles. Use a group's id to filter profiles_list by profile_group_id.

Parameters: None

Returns:

{

"profile_groups": [ { "id": "grp123abc", "name": "Main Brand", "profiles_count": 4 } ] }

profile_groups_initialize_connection

Generate a connect URL for a new profile in a profile group. The user opens the URL to finish the OAuth flow.

Parameters:

• profile_group_id (string, required): Profile group ID
• platform (string, required): Platform to connect (e.g. instagram, linkedin, whatsapp)
• onboarding (string, optional): Instagram and WhatsApp only. Instagram: instagram (default) uses Instagram Login; facebook uses Facebook Login, for an Instagram professional account linked to a Facebook Page you manage. The profile is platform: "instagram" either way, and reconnecting with the other method updates the existing profile in place. WhatsApp: api or business_app (see WhatsApp Business Management).
• identifier + app_password (Bluesky) / bot_token (Telegram): credentials, local server only

profiles_list

List all available social media profiles for posting.

Parameters:

• profile_group_id (string, optional): If provided, only profiles in this group are returned (use profile_groups_list to find group IDs)

Returns:

{

"profiles": [ { "id": "profile-123", "name": "My Twitter Account", "platform": "twitter", "profile_group_id": "group-abc" } ] }

profiles_placements

List available placements for a profile. For Facebook profiles, placements are business pages. For LinkedIn profiles, placements include the personal profile and organizations. For Pinterest profiles, placements are boards. For Telegram profiles, placements are channels the bot can post to. For Google Business profiles, placements are locations, returned as full resource paths (accounts/X/locations/Y) to pass as location_id. For WhatsApp profiles, placements are the phone numbers on the Business Account — the placement id is the phone_number_id every whatsapp_* tool and dm_chat_create take. Available for facebook, linkedin, pinterest, telegram, google_business, and whatsapp profiles.

Parameters:

• profile_id (string, required): Profile hashid

Returns (LinkedIn example):

{

"placements": [ { "id": null, "name": "Personal Profile" }, { "id": "108520199", "name": "Acme Marketing" } ] }

Notes:

• If no placement is specified when creating a post:
• LinkedIn: defaults to the personal profile
• Facebook: defaults to a random connected page (if only one page is connected, no need to set a placement ID)
• Pinterest: it fails
• Telegram: it fails — chat_id is required on every post
• Google Business: it fails — location_id is required on every post and on every google_business_* tool

profiles_stats

Get the follower/engagement timeseries for a profile. Snapshots are captured roughly every 23 hours, so you can plot follower growth and other trends over time. The stats fields are platform-native (not normalized) — see Stats Fields by Platform in the post_stats section for shape and add-on profile-level keys (followers_count, followersCount, etc.) per network.

Parameters:

• profile_id (string, required): Profile hashid
• placement_id (string, conditional): Required for facebook, linkedin, telegram, and google_business profiles. Get it from profiles_placements. Omit for instagram, threads, youtube, twitter, tiktok, pinterest, and bluesky.
• from (string, optional): ISO 8601 timestamp — only include snapshots recorded at or after this time
• to (string, optional): ISO 8601 timestamp — only include snapshots recorded at or before this time

Returns (LinkedIn example):

{

"data": { "profile_id": "prof_li_001", "platform": "linkedin", "placement_id": "108520199", "records": [ { "stats": { "followerCount": 4500, "shareCount": 8, "likeCount": 80 }, "recorded_at": "2026-05-09T08:00:00Z" }, { "stats": { "followerCount": 4520, "shareCount": 9, "likeCount": 90 }, "recorded_at": "2026-05-10T08:00:00Z" } ] } }

For non-placement networks (e.g. Bluesky), omit placement_id:

{

"data": { "profile_id": "prof_bsky_001", "platform": "bluesky", "placement_id": null, "records": [ { "stats": { "followersCount": 8800, "postsCount": 40 }, "recorded_at": "2026-05-09T08:00:00Z" } ] } }

Post Management

post_publish

Publish a post to specified social media profiles.

Parameters:

• content (string, required): Post content text
• profiles (string[], required): Array of profile IDs (hashids) or platform names (e.g., "linkedin", "instagram", "twitter"). When using platform names, posts to the first connected profile for that platform.
• schedule (string, optional): ISO 8601 scheduled time
• media (string[], optional): Array of media URLs or local file paths
• idempotency_key (string, optional): Idempotency key for deduplication
• require_confirmation (boolean, optional): If true, return summary without publishing
• draft (boolean, optional): If true, creates a draft post that won't publish automatically
• queue_id (string, optional): Queue ID to add the post to. The queue will automatically assign a timeslot. Do not use together with schedule.
• queue_priority (string, optional): Priority when adding to a queue: high, medium (default), or low
• platforms (object, optional): Platform-specific parameters. Key is platform name (e.g., "instagram", "youtube", "tiktok"), value is object with platform-specific options. See Platform Parameters Reference for full documentation.

Example:

  {

"instagram": { "format": "reel", "collaborators": ["username1", "username2"], "first_comment": "Link in bio!" }, "youtube": { "title": "My Video Title", "privacy_status": "public" }, "tiktok": { "privacy_status": "PUBLIC_TO_EVERYONE", "auto_add_music": true } }

Returns:

{

"post_id": "job-123", "accepted_at": "2024-01-01T12:00:00Z", "status": "pending", "draft": true }

Note on draft posts: If you request a draft post (draft: true) but the API returns draft: false, a warning field will be included in the response indicating that the API may have ignored the draft parameter. This can happen if the API does not support drafts with certain parameters (e.g., media attachments) or under specific conditions. Check the warning field in the response for details.

post_status

Get status of a published post by job ID.

Parameters:

• post_id (string, required): Post ID from post.publish response

Returns:

{

"post_id": "job-123