A TikTok MCP server: let an agent publish your videos
If the thing deciding what to post is a script or an agent rather than a person, the interesting question stops being “where do I click” and becomes “what can it call”. The Model Context Protocol answers that: the server publishes a set of tools with typed arguments, and the client reads them rather than being taught each endpoint by hand.
EasyDrop exposes publishing to TikTok that way — twelve tools on one remote endpoint, authorised with an API key.
What the server has to solve
Three problems, and only the first is obvious.
The video. Tool arguments are JSON, and a hundred-megabyte file cannot travel in JSON. So the video arrives as a URL and the server fetches it — which happens to fit how agents work anyway, since something that just generated or stored a clip is almost always holding a link to it rather than the bytes.
The credentials. The agent must be able to publish without ever holding a TikTok token. Authorisation stays where you granted it — on TikTok, bound to your account — and the agent carries only an EasyDrop API key, which you can revoke without touching the social accounts themselves.
The pace. An agent will happily fire twenty calls in a second. TikTok’s API publishes per-account request limits, so the server queues rather than forwards: the tool call returns a job, and the job goes out at a rate the account can take.
The tools
- Accounts
list_accounts, get_account_healthWhich accounts are connected, and whether an authorisation has gone stale.
- Publishing
publish_video, publish_video_to_many, publish_existing_videoOne account, many accounts, or a file already uploaded.
- Status
get_upload_status, list_uploads, retry_upload, cancel_uploadFollow a job, retry the one that failed, cancel what has not gone yet.
- Numbers
get_account_analytics, get_post_metrics, list_videosDaily account snapshots, per-post engagement, and what has been uploaded.
The fan-out tool is the one that earns its place. “Post this everywhere” is what an agent is usually asked to do, and expressing it as one call rather than a loop means the pacing and the partial-failure handling stay on the server where they belong.
Connecting one
The server is remote, not a package you install. Point your client at the endpoint, send an EasyDrop API key as a Bearer token, and the tools appear. Keys are issued and revoked in the dashboard, so an agent that misbehaves is switched off in one place rather than re-authorised account by account.
Because it is hosted, there is nothing to keep running on a laptop — which matters when the caller is a workflow on a server somewhere rather than a desktop app.
What it publishes through
TikTok’s official Content Posting API, the same path the web interface uses. No browser automation, no session cookies, nothing signing in as you. The API’s rules apply to agent calls exactly as they do to people: a privacy level has to be chosen for every post, interaction settings are never enabled on your behalf, and music usage has to be confirmed.
An agent that skips those steps does not get a faster publish. It gets a rejected one.
Common questions
What is an MCP server for TikTok?
An endpoint that exposes publishing to TikTok as tools an AI agent can call, instead of an HTTP API it has to be taught by hand. The agent reads the tool schemas, sees what arguments each one takes, and calls them. EasyDrop's server exposes twelve tools covering accounts, publishing, upload status and analytics.
Which MCP clients can connect to it?
Any client that can reach a remote MCP endpoint and send an Authorization header. The server is hosted rather than installed locally, so there is no npm package to run on your machine — you point the client at the URL and give it an EasyDrop API key.
How does the agent authenticate?
With an EasyDrop API key sent as a Bearer token on every request. Keys are created in the dashboard and can be revoked there. The agent never sees a TikTok password or token — those stay on our side, bound to the accounts you authorised through TikTok.
Can the agent post to several accounts in one call?
Yes. publish_video_to_many takes a list of accounts and fans the video out to all of them, which is the thing agents usually want. There is also publish_video for a single account, and publish_existing_video to reuse a file already uploaded.
Also on this site: posting one video to several accounts and bulk uploads.