YaparAI Enterprise MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YAPARAI_ORG_ID | Yes | Organization ID; can also be passed per-call | |
| YAPARAI_API_KEY | Yes | Your API key from kurumsal.yaparai.com | |
| YAPARAI_BASE_URL | No | API base URL (default: https://api.yaparai.com) | https://api.yaparai.com |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_organizationsA | List all organizations associated with your API key. Use this to find your Organization ID (org_id) required for all social media and CRM tools. You can also set YAPARAI_ORG_ID env var to avoid passing it every time. Returns: List of organizations with id, name, plan, and member count. |
| list_social_accountsA | List connected social media accounts (Instagram, Facebook, TikTok, X/Twitter). Shows all social accounts linked to the organization with their status, username, and follower count. Requires enterprise subscription. |
| create_social_postA | Create and publish (or schedule) a social media post. Supports text, images, and videos on Instagram, Facebook, TikTok, X. Use scheduled_at to queue posts for a future time. |
| list_social_postsA | List published and scheduled social media posts. Returns all posts for the organization with engagement stats. Supports filtering by platform, account, or post status. |
| delete_social_postA | Delete a social media post. Deletes the post from both the YaparAI platform and the social media platform (if supported by the platform's API). Scheduled posts are cancelled. |
| get_social_analyticsA | Get social media analytics and performance metrics. Returns engagement stats, follower growth, reach, and impressions for your social media accounts over a given time period. |
| generate_captionA | Generate an AI-powered social media caption. Creates engaging, platform-optimized captions using AI. Supports Turkish and English, multiple tones. |
| generate_hashtagsB | Generate AI-optimized hashtags for a social media post. Creates relevant, trending hashtags based on caption content. |
| list_inboxA | List social media inbox conversations (DMs and comments). Shows all incoming messages from Instagram, Facebook, WhatsApp, etc. Optionally filter by platform or unread status. |
| read_conversationA | Read all messages in a social media conversation. Get the full message history of a DM or comment thread. |
| reply_to_messageA | Reply to a social media DM or message. Send a reply in an existing conversation on Instagram, Facebook, WhatsApp, or other connected platforms. |
| ai_reply_suggestionA | Get an AI-generated reply suggestion for a conversation. The AI reads the full conversation context and suggests an appropriate, personalized reply. Customize with a system prompt. |
| get_social_quotaA | Get social media quota and usage limits for the current billing period. Returns remaining post quota, message limits, and when the period resets. Useful before running bulk operations. |
| list_customersA | List CRM customers with optional filtering. Browse the customer database built from social media conversations. Filter by name/email/phone search, platform source, or tags. |
| get_customerA | Get detailed information about a specific customer. Returns full customer profile including contact details, tags, notes, conversation history summary, and order information. |
| create_customerA | Manually create a new CRM customer record. Add a customer who may not have come through the social inbox. Useful for migrating existing customers or adding offline contacts. |
| update_customerA | Update an existing customer's information. Partially update a customer record — only provided fields are changed. Tags replace the existing tag list completely. |
| add_customer_noteB | Add a note to a customer's record. Notes are visible in the customer profile and help your team track important context (order issues, preferences, follow-ups, etc.). |
| extract_customer_infoA | Extract contact information from conversation history using AI. The AI reads all messages with this customer and extracts their name, phone number, email, and address. Great for auto-filling CRM records. |
| send_shipping_infoA | Send shipping and tracking information to a customer. Automatically sends a tracking message through the same social platform the customer used to contact you (Instagram DM, WhatsApp, etc.). |
| bulk_messageA | Send a message to multiple customers at once. Broadcast promotions, announcements, or updates. Target by specific IDs, a customer tag, or a platform. At least one of customer_ids, tag, or platform is required. |
| sync_customers_from_inboxA | Import customers from social media inbox conversations. Scans all inbox conversations and creates CRM customer records for everyone who has messaged you. New customers are auto-tagged by platform. Existing customers are not duplicated. |
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 22 tools
Each tool targets a distinct action and resource. For example, customer tools (create, get, update, list, note) are separate from social posting (create, delete, list, caption, hashtags) and inbox management (list, read, reply, bulk, AI suggestion). Even overlapping domains like AI reply suggestion vs. reply_to_message are clearly distinguished by generation vs. sending.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_customer, list_social_posts, get_social_analytics). No mixing of camelCase or other conventions. The pattern is predictable across all 22 tools.
22 tools is slightly above the typical 3-15 range for a well-scoped server, but each tool has a clear purpose and the number is justified by the breadth of functionality (CRM, social posting, inbox, analytics, organization management). It is not excessive and avoids redundancy.
The tool set covers core CRUD for customers and social posts, inbox interaction, analytics, and AI-assisted features. Minor gaps like missing update for social posts, tag management, or message deletion exist, but the main workflows are well-supported. Agents can accomplish most tasks without dead ends.