Connect ClientPoster to Claude

Prepare content for your clients by chatting with Claude: it lists your clients, tells you the price first, generates once you confirm, fixes a single scene and sends the content to your client for approval. No API key needed; it works on every plan, including the free plan.

Start free Go to the steps

Before you start

A ClientPoster account — the free plan is enough. Have at least one client added for Claude to work on.
A Claude account: claude.ai, Claude Desktop or Claude Code.
On Team and Enterprise plans, an owner first adds the connector under Organization settings → Connectors.

Add the connector to Claude

In Claude (claude.ai or Claude Desktop), open Customize → Connectors.
Choose + Add → Add custom connector.
Enter ClientPoster as the name, paste the address below and add it:
```
https://api.clientposter.com/mcp
```
Press Connect next to ClientPoster in the list; Claude takes you to ClientPoster.

If you use Claude Code

In Claude Code, run this command, then sign in with /mcp:

claude mcp add --transport http clientposter https://api.clientposter.com/mcp

The command that adds the connector in Claude Code, with its confirmation — Claude Code: the command adds the connector.

ClientPoster with the Authenticate option on Claude Code's /mcp screen — /mcp → ClientPoster → Authenticate: ClientPoster opens in your browser.

Grant access in ClientPoster

Sign in to ClientPoster with your own account. On the permission screen, tick what Claude may do and press Allow; you then return to Claude. Claude never receives your password or an API key.

Permissions you can choose

ReadCustomers, content, token summary, price quotes, image and video downloads, reports (Agency+)
Content generationGenerating, fixing and editing text, images and video — spends tokens
Customers and brand guideCreating and updating customers, brand voice, keywords, logo
ApprovalsSending content to the customer for approval by email, tracking it, withdrawing it; emailing content and reports

Claude never goes beyond what your role allows; for example, with the Viewer role in your team it cannot generate content.

ClientPoster's connection permission screen — The permission screen: you choose what Claude may do.

The line in Claude Code confirming the connection — After you allow access you return to Claude Code; the connection is in place.

Ask Claude in plain language

In a new chat, make sure ClientPoster is turned on and write your request. Claude picks the tools it needs and may ask for your permission the first time it uses one.

Example requests

List my clients.
How many tokens do I have left?
List my latest content.
How much would a 30-second horizontal LinkedIn video for client X cost?
For client X, prepare a 60-second, 6-scene horizontal product video for LinkedIn; tell me the price first and generate it only if I approve.
Give me the download link for this video.

When you ask for something that spends tokens

Claude tells you the price first and asks for your confirmation; the price comes from the same calculation the ClientPoster app uses.
If you confirm, it starts the generation. If the price has changed in the meantime, nothing is generated and Claude asks again with the new price.
Images and videos render in the background; Claude follows the progress and gives you the content and its download link when it is ready.
If a scene is not what you wanted, ask Claude to fix it; this also spends tokens and the price is again given first.

Retrying the same request is never charged twice.

From a real session

A real Claude Code session, run in Turkish; real client names, the plan and the balance are blurred.

Claude's reply with the client list and token balance; real names and the balance are blurred — Asking for clients and the balance is free.

Claude's reply stating the post's price and settings and asking for confirmation — Before anything that costs tokens, Claude states the price and waits for your confirmation.

Claude's reply describing the finished post and the next steps — After your confirmation the post is ready in ClientPoster.

The image ClientPoster generated for the post: a person working in an architecture office — The post's image, generated in ClientPoster.

Client approval and publishing

When the content is ready, ask Claude to send it for client approval: ClientPoster emails your client an approval link. Once your client approves, you publish it right away or schedule it on the client's connected LinkedIn account; publishing is done in the app.

You stay in control

The connection is opened with your own ClientPoster account; Claude never receives your password or an API key.
Claude can only do what you ticked when connecting.
For anything that spends tokens the price comes first; generation only starts at the confirmed price.
You can remove the connection any time under Account → API Keys → Connected apps; once removed, Claude loses access right away.
Removing the connector in Claude does not close the connection in ClientPoster; to cut it completely, remove it in ClientPoster as well.

The Connected apps card in account settings — Connected apps: this is where you remove the connection.

Troubleshooting

Claude does not use ClientPoster

Check that ClientPoster is turned on in the chat's tools menu. If the connector list still shows Connect, the sign-in was not completed.

Claude says it cannot generate content

You may not have ticked Content generation when connecting, or your role does not allow generating. Remove the connection, connect again and tick it.

Not enough tokens

Claude can tell you your balance. You buy token packs or change your plan in the app; Claude cannot make payments.

The permission screen said the connection request is invalid

Remove the connector in Claude, add it again and press Connect.

Which plans does it work on?

The connector works on every plan, including the free plan. API keys are only available on paid plans.

For developers: with an API key

If you work with the Claude API, Claude Code or another agent that can call an HTTP API, create an API key on a paid plan and give Claude the plain-text guide prepared for AI tools and the OpenAPI definition. The details are in the developer guide.

Developer guide

Try your first request today

Start free See plans and pricing

No credit card required. Start with the free plan.