Use Claude Code with PostEveryPlatform

What you need

• A PostEveryPlatform workspace with the destination accounts connected by the owner.
• A plan or trial for writing. Without either, the workspace is read-only and writes answer plan_required.
• Claude Code installed and access to its MCP sign-in flow.

Connect and check

1. Add the server in a terminal. The command uses the HTTP transport documented in the MCP guide.

   Copy

   claude mcp add --transport http posteveryplatform https://posteveryplatform.com/mcp

2. Sign in. Your browser opens PostEveryPlatform so you can choose the workspace and permissions.

   Copy

   claude mcp login posteveryplatform

3. Inside Claude Code, use /mcp to check the connection. Start by reading the workspace and connected accounts, then preview and save a draft.

A first prompt to try

List my connected PostEveryPlatform accounts and tell me which can post. Read the workspace timezone and approval rule. Help me prepare a draft for an account I choose, preview it, and show me any problems. Do not schedule or publish it.

Read the returned account names and permissions before asking for a post. An account the owner has not connected cannot be selected by an agent. The preview tools check what each destination would receive without saving anything. Review every problem and warning before creating the draft.

How approval works

Agent posts wait for the owner by default. A draft saves without scheduling. Scheduled, queued and post-now requests return pending_approval and waiting_for_approval when approval is required. Open the review_url in the app to inspect the post; that URL does not approve it. The owner decides in PostEveryPlatform.

The owner can change the workspace approval switch or let a particular key or connected app skip approval. Give each connection only the permissions it needs. Replies to comments are not held for post approval, so grant reply only when the agent may answer people. Agents cannot connect social accounts, change billing or approve their own posts.

A workspace with no plan or trial is read-only. Writing answers 402 plan_required and points to the Plans page; reading, exporting and deleting still work. A different refusal, 402 plan_limit, means a plan limit was reached. Changing credentials will not fix either plan condition.

Troubleshooting by transport

REST and HTTP

• 401: the key or sign-in is missing, wrong or revoked. Check credentials without putting them in a chat or a post.
• 400: fix malformed or missing inputs, such as an invalid time or required privacy setting.
• 422 validation_failed: fix every length, media or option problem in the response. A field name or its value may be wrong.
• 402 plan_required: the owner needs a plan or trial. 402 plan_limit: inspect the plan limit before trying again.
• 403 missing_scope: the owner needs to grant the named permission. Do not retry around it.
• 429: wait the Retry-After seconds before retrying the request.

MCP tools

A tool failure can be an HTTP-successful MCP result with isError: true and a text message. Read that message rather than treating the transport status as a successful post. Authentication, missing-scope and rate-limit failures can also be HTTP errors. A successful tool result has isError: false; inspect its structuredContent for the actual post or preview result.

Questions