QPost MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QPOST_API_KEY | Yes | API key from QPost dashboard. | |
| QPOST_BASE_URL | No | Base URL for self-hosted QPost. | https://qpost.dev |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_connected_accountsA | List the social media accounts (YouTube, TikTok, Instagram) currently connected to this QPost account, including connection status. Call this before creating a post to know which platforms are actually available. |
| create_postA | Create and publish (or schedule) a post to one or more connected social platforms (YouTube, TikTok, Instagram). Provide media as either a remote URL (mediaUrl fetched by the server) or a local file path (mediaPath read from disk) — exactly one media source per call. Omit scheduledFor to publish immediately. |
| list_postsA | List posts on this QPost account, optionally filtered by status or platform. |
| get_postA | Get a single post by ID, including its per-platform publish status. |
| update_postA | Update a post's caption, schedule, timezone, or status. Only works on posts you own. |
| delete_postA | Permanently delete a post you own. |
| retry_postA | Retry publishing a post that previously failed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: account listing, post CRUD, and retry. No two tools could be confused, as create/list/get/update/delete/retry operate on different actions and list_connected_accounts is separate.
All tool names follow the same snake_case verb_noun pattern (list_, create_, get_, update_, delete_, retry_). This is highly predictable and consistent.
Seven tools is well-scoped for a social media posting server. Each tool earns its place, covering the essential operations without unnecessary bloat.
The set covers the full lifecycle of posts: create, list, get, update, delete, plus retry for failures and account listing for platform awareness. No obvious gaps for the stated purpose.