About qpost-mcp
qpost-mcp connects AI agents to QPost for publishing and scheduling video and image posts on YouTube, TikTok, and Instagram. It offers account and post management tools through hosted HTTP or a local stdio server.
Key features
- 01Publish or schedule video and image posts
- 02List connected social accounts
- 03List, retrieve, and update posts
- 04Delete posts or retry failed posts
- 05Accept media URLs or local files
Use cases
- 01Schedule posts across supported social platforms
- 02Check connected account status
- 03Update captions or publishing schedules
- 04Retry a failed post
MCP support
Exposes QPost account and post-management tools to MCP clients. It can run as a hosted Streamable HTTP endpoint or locally over stdio.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://qpost.dev/mcpclaude mcp add --transport http arslan2012-qpost https://qpost.dev/mcp{"mcpServers":{"arslan2012-qpost":{"type":"http","url":"https://qpost.dev/mcp"}}}Open in Cursor{"servers":{"arslan2012-qpost":{"type":"http","url":"https://qpost.dev/mcp"}}}Open in VS Code{"mcpServers":{"arslan2012-qpost":{"type":"http","url":"https://qpost.dev/mcp"}}}{"mcpServers":{"arslan2012-qpost":{"serverUrl":"https://qpost.dev/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://qpost.dev/mcpAuth requiredTools
Details
From the project READMEqpost-mcp
MCP server for QPost — lets AI agents schedule and publish video/image posts to YouTube, TikTok, and Instagram through QPost's REST API.
Install
Generate an API key from your QPost dashboard (Settings → API Keys), then pick one of the two options below.
Hosted (recommended — nothing to install)
QPost runs the same server at https://qpost.dev/mcp over Streamable HTTP:
claude mcp add --transport http qpost https://qpost.dev/mcp \
--header "x-api-key: YOUR_API_KEY"
Any MCP client that speaks Streamable HTTP can point at that URL with an
x-api-key (or Authorization: Bearer) header. The endpoint is stateless, so
there is no session to manage.
Local (stdio) via npx
Use this if you self-host QPost or would rather run the server yourself:
claude mcp add qpost -e QPOST_API_KEY=your_key_here -- npx -y qpost-mcp
Claude Desktop / other MCP clients
{
"mcpServers": {
"qpost": {
"command": "npx",
"args": ["-y", "qpost-mcp"],
"env": {
"QPOST_API_KEY": "your_key_here"
}
}
}
}
Set QPOST_BASE_URL too if you're self-hosting QPost (defaults to https://qpost.dev).
Tools
| Tool | Description |
|---|---|
list_connected_accounts | List connected YouTube/TikTok/Instagram accounts and their status |
create_post | Create and publish (or schedule) a post, with video or image media from a URL or local path |
list_posts | List posts, optionally filtered by status/platform |
get_post | Get a single post by ID |
update_post | Update a post's caption/schedule/timezone/status |
delete_post | Delete a post |
retry_post | Retry a failed post |
Media handling differs by transport
The local stdio server can read files from your machine, so create_post
accepts mediaPath as well as mediaUrl. The hosted endpoint obviously
cannot reach your disk — it takes mediaUrl/imageUrls, or mediaBase64
with an optional mediaFilename to set the MIME type.
Full request/response shapes and per-platform metadata options (YouTube category/privacy, TikTok privacy level, Instagram media type, etc.) are documented at qpost.dev/docs — this server is a thin wrapper over that same REST API.
Local development
npm install
npm run dev # runs src/index.ts directly via tsx
npm run build # compiles to dist/
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.