Postoria MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POSTORIA_API_KEY | Yes | Your Postoria Public API key |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workspacesA | List Postoria workspaces available to the API key. Returns workspace IDs that should be used in follow-up Postoria tools. |
| list_social_accountsA | List social accounts in a Postoria workspace. Returns account IDs that should be used when publishing, scheduling, or queueing posts. |
| list_queuesA | List publishing queues in a Postoria workspace. Returns queue IDs that should be used with add_post_to_queue. |
| create_media_uploadA | Create a media upload slot and signed upload URL. This tool does not upload file bytes; upload raw bytes to the returned URL with PUT, then call complete_media_upload. |
| complete_media_uploadB | Complete a media upload after the raw file bytes have been uploaded to the signed upload URL. |
| upload_media_from_fileA | Upload a local file from the machine running this MCP server. Local stdio mode only. |
| import_media_from_urlB | Import media into Postoria from a public URL. |
| get_mediaA | Get the processing status and details for a Postoria media item. |
| publish_post_nowB | Create and publish a Postoria post immediately. |
| schedule_postB | Create a Postoria post scheduled for a specific UTC date-time. |
| add_post_to_queueB | Create a Postoria post and add it to a publishing queue. |
| get_postA | Get status and publishing results for a Postoria post. |
| list_postsB | List posts in a Postoria workspace, optionally filtered by accounts, queue, status, networks, UTC date range, and cursor pagination. |
| delete_postA | Delete/cancel a Postoria post. This is destructive and should only be called after user confirmation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| postoria_create_social_post | Guide an AI agent to create a Postoria post safely using workspace and social account discovery first. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| postoria_api_info |
TDQS
Scored across 14 tools
Each tool maps to a distinct resource/action: workspaces, social accounts, queues, media, and posts are cleanly separated. The three media intake paths (local file, URL, signed-URL slot) are differentiated by their descriptions, so an agent should be able to select correctly.
Tools consistently follow a snake_case verb_noun pattern (get_, list_, create_, delete_, publish_, schedule_, add_, upload_, import_, complete_). Minor variations like publish_post_now and add_post_to_queue are still predictable and fit the overall convention.
14 tools is well within the ideal 3-15 range and covers all major workflows: discovery, media ingestion, post creation, retrieval, and deletion. No tool feels redundant, and the count matches the server's domain.
The core post lifecycle is covered: create (now/scheduled/queued), read (get/list), and delete, plus media upload and workspace/account/queue discovery. Obvious gaps are an update/edit endpoint for posts and media listing/deletion, but these are not fatal to common workflows.