Run your social channels from an AI assistant: Klipsy's MCP server

An MCP server lets an AI assistant like Claude or ChatGPT securely call an app's own tools on your behalf. Klipsy ships one: a Model Context Protocol server that gives your assistant read access to every channel's analytics and controlled access to two low-risk actions — all scoped to your own projects, authorized by a token only you can mint. You ask "how are my channels doing this month?" in plain language, and the assistant pulls the real numbers from your Klipsy account and answers.

This post explains what the Model Context Protocol is, exactly what Klipsy's server can and can't do, how access is secured, and how to connect it to your AI assistant in a few minutes.

What is the Model Context Protocol (MCP)?

The Model Context Protocol is an open standard, introduced by Anthropic in late 2024, for connecting AI assistants to external tools and data. Instead of every app inventing its own plugin format, MCP defines one: an MCP client (your AI assistant — Claude Desktop, Claude Code, or any MCP-compatible app) talks to an MCP server (a program a company runs to expose its own capabilities).

When a server is connected, the assistant can see the list of tools it offers, decide which one answers your question, call it with the right arguments, and read the result back — without you ever leaving the chat. The protocol is documented in the public MCP specification, and Klipsy implements the server half of it.

What can you do with Klipsy's MCP server?

Klipsy's server exposes 15 tools, grouped by what they help you do. Almost all of them only read your data; the two that act are deliberately low-risk.

See how a channel is doing

• list_projects — list your channels/brands and their activity counts. This is the starting point: it hands the assistant the project ids the other tools need.
• get_project_performance — a 30-day trend by platform, lifetime totals, and the current best-performing template. The right first call for any "how am I doing?" question.

Dig into individual posts

• list_posts — your post inventory with per-platform publish status and current counters: views, likes, comments and shares.
• get_post_target_detail — full detail on one post on one platform: status, error message, the live URL, and when its metrics last synced. Use it to debug a single failed post.
• compare_post_metrics — put up to five posts side by side and compare their daily growth curves, to answer "why did post A beat post B?"

Decide what to make next

• list_templates_performance — your templates ranked by average views and likes per post, so you make more of what works.
• get_template_detail — one template's full configuration: prompt, voice, aspect ratio, style, duration and model.
• search_templates — find a template by name instead of needing to know its id.

Check what's running

• list_automations_status — every automation's schedule, last and next run, and any errors.
• get_pending_review_posts — drafts waiting for your approval.
• get_generation_status — poll a content generation or Studio render to see if a draft is ready.
• list_connected_accounts — connected platforms, handles, connection status and token expiry, so you can check channel health.
• get_content_cost_report — AI-generation cost totals with a simple views-per-dollar ratio (admin-only).

The two tools that actually act

• generate_template_content — generate a new draft from an existing template. It produces content for review and does not publish or attach any social account — it only makes a draft.
• set_automation_status — pause or resume an automation. Pausing stops future scheduled runs immediately and never touches anything already published.

So your assistant can ask questions like "Which template got the best average views on my cooking channel last month, and generate a fresh draft from it," or "Pause every automation on the travel project — I'm reworking the templates."

What Klipsy's MCP server will not do

This is the part worth reading twice. Of the 15 tools, 13 are read-only. Only two make any change, and both are intentionally cautious:

• The AI cannot publish to your social accounts. generate_template_content produces a draft for review; it never posts. Publishing still happens through Klipsy's own scheduler, on the cadence and review settings you configured.
• The AI cannot delete content, disconnect accounts, change your billing, or touch published posts. Pausing an automation is fully reversible and leaves live posts alone.

The assistant reads a lot and can nudge two safe levers. Everything with real consequences stays inside Klipsy, under your control. If you want the fuller picture of how publishing and review work, how Klipsy works walks the pipeline end to end.

How is MCP access secured?

Handing an AI assistant a key to your account only makes sense if that key is tightly bounded. Klipsy's is, in four ways:

1. A single-purpose token. The key is a personal-access token minted with exactly one ability — mcp:access. If it ever leaked, it still couldn't be replayed against the rest of your account's routes; it only opens the MCP endpoint.
2. Owner-scoped tools. Every tool is scoped to the authenticated user's own projects. There is no way to name another account's project id and read its data.
3. Plan re-checked on every request. Access isn't just granted when the key is minted — Klipsy re-verifies your plan on every single MCP call, so entitlement can't drift out of sync.
4. One key, revocable anytime. A single key covers all your projects (matching Klipsy's single-owner model). Generating a new one immediately invalidates the old one, and the plaintext value is shown only once, when you create it.

Which plans include MCP?

The MCP server is available on the Personal plan and up — every paid tier. You can see what each tier includes on the pricing page. (Klipsy is in limited access before launch; join the waitlist to lock in launch pricing.)

How to connect Klipsy to your AI assistant

1. Open Settings → MCP in Klipsy.
2. Click Generate key and copy the token — it's shown once.
3. Note your endpoint URL: https://theklipsy.com/mcp/klipsy.
4. Add the server to your MCP client's configuration. Klipsy uses the streamable HTTP transport, so you point your assistant at the endpoint above and send the token as a bearer credential (Authorization: Bearer <your-token>).
5. Start a chat and ask your assistant to list your projects first — that discovers the ids every other tool builds on.

From there, plain-language questions work: "How did my Shorts channel do this week?", "Which post got the most shares, and why?", "Show me drafts waiting for review."

Example things to ask

• "Give me a 30-day performance summary for each of my channels."
• "Compare my last five TikTok posts and tell me what the top one did differently."
• "Rank my templates by average views and generate a new draft from the best one."
• "Which automations have errors, and what are they?"
• "Pause every automation on my food project."

Why this matters

Most social tools give you a dashboard and leave the thinking to you. Pairing Klipsy's metrics with an AI assistant over MCP turns "log in, click around, export a CSV" into a conversation: the assistant reads views, likes, comments and shares straight from your account, spots the pattern, and can act on the two safe levers without you touching the UI. It's the same create → publish → measure loop Klipsy already runs, now queryable in natural language. For how that loop fits together, see why Klipsy runs the whole loop and the full feature tour.

FAQ

Which AI assistants work with Klipsy's MCP server?

Any MCP-compatible client — Claude Desktop, Claude Code, and other assistants that support the Model Context Protocol. Klipsy runs a standard streamable-HTTP MCP server, so anything that speaks the protocol can connect with your key.

Can the AI post to my social accounts?

No. The assistant can generate a draft and pause or resume an automation — nothing else changes your account. Publishing stays inside Klipsy, on the schedule and review mode you set. The AI never posts on your behalf.

Is my data safe if I connect an AI assistant?

Your key carries a single ability (mcp:access), every tool is scoped to your own projects, your plan is re-checked on every request, and you can revoke or regenerate the key at any time. A new key instantly invalidates the old one.

What metrics can the assistant read?

Views, likes, comments and shares — per post, per platform, and rolled up per project — the same numbers Klipsy tracks natively.

What does MCP access cost?

It's included on the Personal plan and every tier above it. See the pricing page for details.