Qpost Mcp

io.github.arslan2012Published by GitHub account arslan2012v0.4.0Updated Nov 5, 2026

MCP server for QPost — lets AI agents publish video and image posts to YouTube, TikTok, Instagram.

VerifiedStreamable HTTPWeb executableBusiness & CommerceMedia & Design

Overview

AI-generated overview

QPost MCP server that lets an AI assistant create, schedule, update, delete and check stats for video and image posts on YouTube, TikTok and Instagram.

What you can do
  • List connected YouTube, TikTok and Instagram accounts and their status
  • Create and publish or schedule video and image posts to those platforms
  • List posts, or fetch one post with its per-platform publish status
  • Read live engagement stats (views, likes, comments, shares) and public URLs
  • Update a post's caption, schedule, timezone or status, and delete posts
  • Retry publishing for a post that previously failed
When to use it
Useful when you want an assistant to draft, schedule and publish short-form video or image content to social accounts through QPost, or to check how published posts are performing, without opening the QPost dashboard.
Requirements
A QPost account with destination social accounts connected, plus an API key from the QPost dashboard. Either the hosted endpoint at qpost.dev with an x-api-key header, or the local npm package run with npx, which needs Node 20+ and the QPOST_API_KEY environment variable. QPOST_BASE_URL can point at a self-hosted instance.
Before you install
The API key (QPOST_API_KEY or x-api-key header) grants access to the account's publishing; keep it out of shared configs. The tools publish, schedule, update and permanently delete posts on real social accounts, and publishing happens immediately when no schedule is set. Media must be a public URL or base64 for the hosted endpoint, so content is sent to QPost's hosted service even when the bridge runs locally.

Installation

In SourceWeft

  1. Open Qpost Mcp in the dashboard and add it to a workspace.
  2. Connect x-api-key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.arslan2012%2Fqpost-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "qpost": {
      "type": "http",
      "url": "https://qpost.dev/mcp",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

qpost-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

Connect your destination accounts and generate an API key at QPost 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:

bash
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 to run the MCP bridge on your machine while QPost handles publishing:

bash
claude mcp add qpost -e QPOST_API_KEY=your_key_here -- npx -y qpost-mcp

Claude Desktop / other MCP clients

json
{  "mcpServers": {    "qpost": {      "command": "npx",      "args": ["-y", "qpost-mcp"],      "env": {        "QPOST_API_KEY": "your_key_here"      }    }  }}

QPOST_BASE_URL defaults to https://qpost.dev. Running this MCP bridge locally still uses QPost’s hosted publishing service.

Tools

ToolDescription
list_connected_accountsList connected YouTube/TikTok/Instagram accounts and their status
create_postCreate and publish (or schedule) a post, with video or image media from a URL or local path
list_postsList posts, optionally filtered by status/platform
get_postGet a single post by ID
get_post_statsViews, likes, comments and shares for a published post, plus its public URL
update_postUpdate a post's caption/schedule/timezone/status
delete_postDelete a post
retry_postRetry 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.

Both the stdio server and the hosted endpoint speak MCP 2026-07-28 and still accept clients on 2025-era protocol versions. The stdio server needs Node 20+.

Publishing from n8n?

Use the tested n8n video-to-draft workflow. It uses built-in HTTP Request nodes, works without a community package, and saves a draft before you publish. The page includes the downloadable JSON and the settings to change.

For TikTok app-review restrictions, see self-hosted publishing options.

Local development

bash
npm installnpm run dev   # runs src/index.ts directly via tsxnpm run build # compiles to dist/

License

MIT

Source: README.md at commit abd3931

Tools

8

list_connected_accounts

List the YouTube/TikTok/Instagram accounts connected to this QPost account. Call this before creating a post to see which platforms are available.

Takes no parameters.

create_post

Create and publish (or schedule) a video or image post to connected platforms. Media must be supplied as a publicly reachable URL (mediaUrl / imageUrls) or base64 (mediaBase64) — this is a hosted server and cannot read files from your machine. Omit scheduledFor to publish immediately.

ParameterstitlecaptionrequiredmediaUrltimezoneimageUrlsmediaKindrequiredplatformsrequiredmediaBase64scheduledFormediaFilename

list_posts

List posts on this account, optionally filtered by status or platform.

Parametersstatusplatform

get_post

Get a single post by ID, including per-platform publish status.

Parametersidrequired

get_post_stats

How a published post is doing: views, likes, comments and shares per platform, read live from the platform (TikTok so far), plus each platform's public URL.

Parametersidrequired

update_post

Update a post's caption, schedule, timezone, or status. Only the fields you pass are changed.

ParametersidrequiredstatuscaptiontimezonescheduledFor

delete_post

Permanently delete a post you own.

Parametersidrequired

retry_post

Retry publishing a post that previously failed.

Parametersidrequired

Version history

2
  1. v0.4.0LatestOct 29, 2026
  2. v0.3.0Sep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts