Ayrshare Unofficial MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AYRSHARE_API_KEY | Yes | Your Ayrshare Primary Profile API key | |
| AYRSHARE_PROFILE_KEY | No | Default Profile Key for user profile operations (Business plan) |
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 |
|---|---|
| create_postB | Publish or schedule a social media post to one or more platforms. Supports text, images, videos, scheduling, and auto-scheduling. |
| get_postA | Get details of a specific post by its Ayrshare Post ID. Returns status, content, platform-specific post IDs and URLs. |
| get_post_historyC | List post history with optional filters. Returns posts with their status, content, platforms, and scheduling info. |
| delete_postA | Delete a post from social platforms. Can delete a single post, multiple posts in bulk, or all scheduled posts. |
| create_profileA | Create a new user profile for managing separate social media accounts. Returns the profile key needed for subsequent operations. Requires Business plan. |
| list_profilesB | List all user profiles with their linked social accounts. Supports filtering and pagination. Requires Business plan. |
| update_profileB | Update an existing user profile's settings. Requires Business plan. |
| upload_mediaA | Upload an image or video to Ayrshare's media library. Accepts either a public URL (which will be downloaded and uploaded) or base64-encoded data. Files are stored for 90 days. Max 30MB. Requires Premium plan. |
| post_commentB | Post a comment on a social media post. Supports text and image comments across multiple platforms. Requires Premium plan. |
| get_commentsC | Get comments on a social media post. Can retrieve by Ayrshare Post ID, Social Post ID, or Social Comment ID. Requires Premium plan. |
| delete_commentB | Delete a comment from a social media post. Uses the Social Comment ID from the platform. Supported on Facebook, Instagram, TikTok, X/Twitter, and YouTube. Requires Premium plan. |
| send_messageB | Send a direct message on a social platform. Supports text and media messages on Facebook, Instagram, and X/Twitter. Requires Business plan. |
| get_messagesB | Get messages and conversations from a social platform. Supports listing all conversations or getting a specific conversation's messages. Requires Business plan. |
| get_post_analyticsA | Get engagement analytics for a specific post (likes, views, shares, impressions, comments). Returns real-time metrics across all platforms the post was published to. Note: TikTok/YouTube can take 24-48h to update. Requires Premium plan. |
| get_social_analyticsB | Get account-level analytics for social profiles (follower count, demographics, impressions, engagement rates). Requires Premium plan. |
| set_auto_scheduleB | Create or update an auto-posting schedule with predefined times and days. Posts created with autoSchedule enabled will be queued to the next available time slot. Requires Premium plan. |
| list_auto_schedulesB | List all configured auto-posting schedules with their times, days, and last scheduled dates. Requires Premium plan. |
| delete_auto_scheduleB | Delete an auto-posting schedule by its title. Requires Premium plan. |
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 18 tools
Each tool has a clearly distinct purpose targeting specific resources and actions in the social media management domain. For example, create_post vs. delete_post vs. get_post handle different lifecycle stages, while tools like get_comments, post_comment, and delete_comment focus specifically on comment management without overlap. The descriptions clearly differentiate operations like analytics (get_post_analytics vs. get_social_analytics) and scheduling (set_auto_schedule vs. list_auto_schedules vs. delete_auto_schedule).
All 18 tools follow a consistent verb_noun naming pattern with snake_case throughout. The verbs are clear and appropriate (create, delete, get, list, post, send, set, update, upload), and nouns precisely describe the target resources (post, profile, auto_schedule, comment, messages, analytics, history, media). There are no deviations in style or convention across the toolset.
With 18 tools, the count is slightly high but reasonable for a comprehensive social media management server covering posting, profiles, comments, messages, analytics, scheduling, and media. Each tool appears to earn its place by addressing a specific need, though some closely related tools like get_post_history and list_auto_schedules might be consolidated. The scope justifies the number without feeling excessively bloated.
The toolset provides complete CRUD/lifecycle coverage for social media management: create/delete/get/update posts and profiles, full comment operations (get/post/delete), message handling (get/send), analytics at both post and account levels, auto-scheduling management (set/list/delete), and media upload. There are no obvious gaps—agents can perform end-to-end workflows from content creation to publishing, engagement, and analysis without dead ends.