MCP server

The MCP server gives AI assistants SocialHelper’s features as tools. It’s at https://socialhelper.app/mcp, speaks streamable HTTP, and uses your API key in the Authorization header.

claude mcp add --transport http socialhelper https://socialhelper.app/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Setup guides for other clients: Claude Code, Cursor, VS Code, Claude Desktop, Windsurf (Devin Desktop), Codex CLI, Gemini CLI, Zed, Cline.

Tools

list_accounts tool

List the accounts connected to this workspace. Accounts with can_publish receive posts: use their IDs as `accounts` in create_post. Accounts with tools (Search Console, Analytics, Ads…) offer reports and lookups: see list_account_tools. Only accounts with status "active" can be used.

get_platform_rules tool

Get the rules posts must fit on each platform: text limit and how it is counted, how many images/videos, accepted file types and sizes, and platform-specific options you can pass in create_post overrides.

upload_media tool

Import an image or video from a public URL so it can be attached to a post. Returns a media ID for create_post. Accepts JPEG, PNG, WebP, GIF, MP4 and MOV up to 60 MB.

create_post tool

Publish a post to one or more connected accounts, now or at scheduled_at. The content is checked against every target platform first: if anything does not fit, nothing is posted and all problems are returned. Posting is public — confirm the text and accounts with the user first.

get_post tool

Get a post and the status of each target account: scheduled, queued, publishing, confirming, published (with its live URL), failed (with the reason) or cancelled.

list_posts tool

List recent posts, newest first, optionally filtered by status. Useful for finding scheduled posts or recent failures.

cancel_post tool

Cancel a scheduled post on every account where it has not started publishing. Already-published targets are not removed from the platform.

list_account_tools tool

List the tools a connected account offers, such as Search Console queries, Analytics reports or Google Ads searches, with each tool's input schema. Run them with run_account_tool. Accounts that only receive posts have no tools.

run_account_tool tool

Run one of a connected account's tools (see list_account_tools) and get its result. Pass the tool's input as `input`, matching its input schema.

How agents use them

The server explains two flows to every agent that connects:

• Posting: list_accounts → get_platform_rules → upload_media (optional) → create_post → get_post. Agents are told that posting is public and immediate unless scheduled_at is set, and to confirm the text and accounts with you first.
• Data: list_accounts → list_account_tools → run_account_tool, starting with a listing tool to find the IDs other tools need.

Details

• create_post takes the same fields as the REST API, plus an optional idempotency_key.
• upload_media imports from a public URL (up to 60 MB). Agents can’t upload local files.
• Problems come back as tool errors with a readable message, so the agent can fix and retry.
• Calls count towards the key’s 120 requests a minute, shared with REST.
• A GET on the endpoint returns 405; clients use POST.