RecurPost MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RECURPOST_EMAIL | Yes | Your RecurPost login email address. | |
| RECURPOST_API_KEY | Yes | Your RecurPost API Password Key (generated in Account Settings). |
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 |
|---|---|
| user_loginB | Verify RecurPost API credentials |
| connect_social_account_urlsB | Get URLs to connect new social media accounts to RecurPost |
| social_account_listB | List all connected social media accounts with their IDs |
| library_listB | List all content libraries with their IDs |
| history_dataA | Get posting history for a social account (max 100 posts per request) |
| add_content_in_libraryB | Add a post to a content library for recurring/evergreen posting |
| post_contentB | Post content immediately or schedule it for a future time on a social account |
| generate_content_with_aiA | Generate social media content text using RecurPost AI. Supports multi-turn conversations via ai_id. |
| generate_image_with_aiC | Generate an image from a text description using RecurPost AI |
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 9 tools
Each tool has a clearly distinct purpose with no overlap: library management (add_content_in_library, library_list), social account management (connect_social_account_urls, social_account_list), content generation (generate_content_with_ai, generate_image_with_ai), posting operations (post_content, history_data), and authentication (user_login). The descriptions make it easy to differentiate between similar-sounding tools like post_content and add_content_in_library.
The naming follows a mostly readable but mixed convention: snake_case is used consistently (e.g., add_content_in_library, social_account_list), but the patterns vary. Some tools use verb_noun (post_content, user_login), others use noun_verb (library_list, history_data), and some are more descriptive phrases (connect_social_account_urls). This inconsistency doesn't hinder usability but lacks a uniform style.
With 9 tools, the count is well-scoped for a social media management server, covering key areas like content creation, scheduling, account management, and authentication. Each tool serves a specific function without redundancy, making the set comprehensive yet manageable for typical workflows in this domain.
The tool surface covers core social media management operations effectively: content generation (text and image), library management, posting (immediate and scheduled), account listing and connection, and authentication. A minor gap is the lack of tools for updating or deleting existing content or libraries, which agents might need to work around, but the essentials for posting and content creation are well-covered.