Your content team, inside your AI client.
Connect Depost AI to Claude, ChatGPT, or any MCP client. Draft posts, pull analytics, manage the calendar, and work the approval queue without leaving the assistant you already use.
7 days free · Strategy in your first 15 minutes · Cancel anytime
- It answers from your numbers
- “What worked last month?” gets a real answer: your own impressions and follower history, not a guess.
- One brand or your whole workspace
- Connect a single presence, or every brand your team runs, and manage them from the same conversation.
- The approval valve still holds
- Drafts land in your queue instantly. Anything that reaches LinkedIn waits for your explicit yes.
Why it matters
Meet your team where you already work.
MCP (Model Context Protocol) is the open standard that lets AI assistants like Claude and ChatGPT call external tools. Depost AI ships as an MCP server: your brand memory, drafts, calendar, and analytics become tools any assistant can use, with keys you scope and publishing locked behind a permission you grant deliberately.
1key
scopes an assistant to a single brand or a whole workspace. Revoke it anytime.
Any
MCP client works: Claude, ChatGPT, and agent frameworks alike.
100%
of plans include MCP. Most alternatives don’t offer it at all.
How it works
Your team works wherever you work.
Connect with a scoped key
Keys are scoped to one brand or a whole workspace, so an assistant sees exactly what you hand it: one client, or the whole agency.
Ask for real work
“Draft a post from this thread.” “How did last week perform?” “What is waiting for approval?” The same agents answer, with the same brand memory behind them.
Publishing stays deliberate
By default a key can read context and analytics and write drafts. Scheduling and publishing sit behind a separate scope you grant on purpose, so nothing ships by accident.
What ships
Real work, straight from your AI client.
Scoped keys
Brand-scoped for a single presence, workspace-scoped for a whole client or team. Revoke one without touching the rest.
Draft from anywhere
Turn a Claude conversation or a research thread into a LinkedIn draft, in your voice, queued for review.
Analytics on demand
Pull real impressions and follower history into the conversation you are already having.
Calendar operations
See the schedule, move posts, fill gaps: calendar work is a sentence, not a tab switch.
The queue, readable
List drafts, posts in review, approved work, and scheduled slots, and check whether a post is ready to publish.
On every plan
MCP ships on Solo, Team, and Enterprise alike. Most alternatives do not offer it at all.
The operations
Every operation, a sentence away.
Every chip is a real operation on the Depost AI MCP server, the same ones your assistant calls. A new key can read context, content, and analytics and write drafts; everything heavier is a scope you add deliberately.
Brand context
The assistant starts briefed: voice, strategy, pillars, and everything you have published, readable before any work begins.
Drafting & ideas
Any conversation becomes a draft or a saved idea. Edits are versioned, quotas are enforced, and everything lands in your queue.
Media
Attach the graphic from a URL or a short-lived upload link, straight onto the draft it belongs to.
Calendar & publishing
See the queue, find open slots, and schedule approved work. Publishing sits behind its own scope, so nothing ships by accident.
Analytics
The dashboard’s numbers as answers: overviews, period comparisons, pillar and format breakdowns, top performers.
Workspace & knowledge
Roster-wide analytics and calendar reads for agencies, behind explicit consent, plus a brand knowledge base you can feed from anywhere.
In practice
One prompt does the whole errand.
For founders
The research you are already doing in Claude becomes Tuesday’s post, without a single tab switch.
For teams
The Monday report writes itself from dashboard-computed numbers instead of an evening of screenshots.
For agencies
One prompt replaces the per-client export ritual. Workspace reads stay behind explicit consent.
What people ask about MCP.
Which AI clients work?
Claude, ChatGPT, and any MCP-enabled assistant or agent framework. If it speaks MCP, it can run your content team.
Is it safe to hand an assistant my LinkedIn?
The assistant never touches LinkedIn. It talks to Depost AI with a key you scope, and everything it drafts waits in the same approval queue as the rest of your content.
Why does MCP matter for an agency?
Workspace-scoped keys mean your own AI workflows can run the whole client roster: brief in the morning, review a full queue after lunch. It is the difference between a tool you visit and infrastructure you build on.
What is MCP?
MCP (Model Context Protocol) is an open standard that lets AI assistants securely call external tools. Depost AI ships an MCP server, so assistants like Claude and ChatGPT can draft posts, pull analytics, manage the calendar, and work the approval queue as native tools.
How do I connect it?
Create a key in Depost AI scoped to a brand or a workspace, add Depost AI as a connector in your MCP client, and the tools appear in your conversation. Revoking the key cuts access instantly, without touching anything else.
Can MCP publish posts directly?
Only if you allow it. Scheduling and publishing sit behind a dedicated publish scope you grant per key. Without it, an assistant can draft and queue but never ship; with it, the instruction still comes from you.
Make LinkedIn your
best-performing channel.
Brief your team once. It studies, plans, writes, designs, and schedules. You approve.
Your brief comes with you: once you're set up, it's the team's first job.
7 days free · Strategy in your first 15 minutes · Cancel anytime