mixpost-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MIXPOST_API_KEY | Yes | Your Mixpost API access token | |
| MIXPOST_BASE_URL | Yes | Your Mixpost instance base URL (e.g., https://your-domain.com) | |
| MIXPOST_CORE_PATH | No | Custom core path (optional) | mixpost |
| MIXPOST_WORKSPACE_UUID | Yes | The UUID of your Mixpost workspace |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mixpost_list_accountsA | List all connected social media accounts in the workspace |
| mixpost_get_accountA | Get details of a specific social media account |
| mixpost_create_postC | Create a new social media post |
| mixpost_update_postC | Update an existing social media post |
| mixpost_approve_postC | Approve a social media post |
| mixpost_get_postC | Get details of a specific post |
| mixpost_list_postsB | List posts in the workspace |
| mixpost_delete_postB | Delete a specific post |
| mixpost_delete_multiple_postsA | Delete multiple posts at once |
| mixpost_schedule_postC | Schedule a post for publishing |
| mixpost_add_post_to_queueB | Add a post to the publishing queue |
| mixpost_list_mediaA | List media files in the workspace |
| mixpost_get_mediaA | Get details of a specific media file |
| mixpost_update_mediaC | Update media file metadata |
| mixpost_delete_mediaB | Delete a media file |
| mixpost_list_tagsA | List all tags in the workspace |
| mixpost_get_tagB | Get details of a specific tag |
| mixpost_create_tagC | Create a new tag |
| mixpost_update_tagC | Update an existing tag |
| mixpost_delete_tagB | Delete a tag |
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 20 tools
Most tools target distinct resource-action pairs (posts, tags, media, accounts). The only potential confusion is between mixpost_schedule_post and mixpost_add_post_to_queue, but their descriptions clarify the difference (specific time vs. queue placement). Overall, tool boundaries are clear.
All tools follow a consistent mixpost_<verb>_<noun> pattern using snake_case and a common prefix. Verbs like list, get, create, update, delete are used uniformly across resources, making the API predictable and easy to navigate.
With 20 tools, the server is slightly heavy but appropriate given the breadth of the domain (posts, media, tags, accounts). The tool count reflects the need for CRUD operations on multiple resources without becoming excessive or unwieldy.
The tool surface provides thorough coverage for posts (create, update, approve, schedule, queue, delete, bulk delete) and full CRUD for tags. Minor gaps exist, such as missing account management (creation/deletion) and media upload, but these are likely handled outside the MCP server scope.