ChatYug MCP — AI assistants for Messaging, CRM, Marketing, Commerce, and Chatbot

ChatYug MCP (v2.1.0) lets you connect an MCP-compatible AI assistant (for example Claude, ChatGPT, or Gemini CLI) to your ChatYug account. You can ask it in plain language to search contacts, send templates, run marketing bulk/schedules, manage catalogs and orders, edit commerce flows, or manage chatbot keyword flows — about 85 tools across Messaging, CRM, Marketing, Commerce, and Chatbot on the official WhatsApp Business API.

Connector URL: https://mcp.chatyug.com/mcp · Jump to usage guidelines · tool catalog · connect steps.

What you can ask an assistant to do

With ChatYug MCP connected, typical requests include:

  • Messaging — send text, template, interactive, media, carousel, or poll messages; check delivery; prepare media uploads
  • Contacts and CRM — find people, export lists, update names or labels, create and manage contact groups, careful bulk import
  • Marketing — list/sync templates and carousel templates, schedule campaigns, create/cancel 1-recipient bulk jobs, group broadcast (with confirmation)
  • Commerce — list catalogs and products, send product or flow messages when the catalog is linked on your WABA, list/update orders, create/get/update/publish commerce flows
  • Chatbot — list/get/create/update/publish keyword chatbot flows (requires automation permission on the WABA)

Your assistant only acts within the WhatsApp Business Account linked to the API key (or OAuth binding) used for MCP.

How to use ChatYug MCP (guidelines)

  1. Call get_identity first if you need phoneNumberId or WABA context.
  2. Send success ≠ delivered. After a send, call get_delivery_status (or get_message_status) before telling the user a message was delivered.
  3. Confirm dangerous writes. Tools such as bulk create/cancel, group broadcast, schedule create/cancel/run-now, notify_order, CRM import/remove, chatbot create/update/publish/unpublish, and update_commerce_flow return a dry-run preview first. Re-call with confirm=true and the returned confirmId to execute.
  4. Media from Claude.ai: allowlist mcp.chatyug.com under Settings → Capabilities → Code execution → Additional allowed domains, then use prepare_media_upload (see sending media). Never compress originals.
  5. Trial vs paid: Trial = read-only lookups/lists. Monthly/Annual unlock Messaging, CRM, Marketing, and Commerce writes as allowed by your scopes.
  6. After ChatYug MCP updates: remove and re-add the connector, then start a new chat so the client loads the latest tools and instructions.
  7. Commerce product messages work when the catalog is linked on your WhatsApp Business Account. If Meta returns an invalid parameter error, link/sync the catalog in ChatYug first.
  8. Chatbot tools require automation permission on the WABA. Designing full node graphs is easiest in the portal builders; MCP accepts valid flowData JSON.

Example prompts

  • “List my approved WhatsApp templates, then show status for the first one.”
  • “Create a bulk job that sends template X to only +91 70167 93529, then cancel it if needed.”
  • “List recent commerce orders and show details for order 94.”
  • “Create a commerce flow, update its JSON, publish it, and send it to +91 70167 93529.”
  • “Create a chatbot flow with keyword MCPFLOW, publish it, then tell me to reply with that keyword.”
  • “When my catalog is linked, send a single-product message for retailer AHPBS200 to this customer.”
  • “Send a text message to this number and then check delivery status.”

Tool catalog (v2.1.0)

About 85 tools are registered. Names below match what the assistant can call. Support, AI, and Admin MCP domains are not included in this release.

Messaging

get_identity, send_text_message, send_template_message, send_media_message, send_interactive_message, send_carousel_message, send_poll, forward_message, mark_message_read, get_message_status, get_delivery_status, prepare_media_upload, get_media_upload_status, upload_media, upload_media_begin, upload_media_chunk, upload_media_finish, download_media, resolve_media_url, list_conversations, get_conversation_messages, start_conversation_with_template, star_message

CRM

search_contacts, get_contact, create_contact, update_contact, set_contact_label, import_contacts_csv, export_contacts, list_contact_groups, create_contact_group, add_contacts_to_group, remove_contacts_from_group, import_group_csv, list_contact_tags, set_custom_fields

Marketing

Templates: list_templates, get_template, create_template, get_template_status, sync_template, list_carousel_templates, get_carousel_template, register_carousel_template

Schedules: list_schedules, get_schedule, create_scheduled_message, upload_schedule_csv, get_schedule_report, run_schedule_now, cancel_scheduled_message

Bulk / broadcast: create_bulk_job, upload_bulk_csv, list_bulk_jobs, get_bulk_job_status, cancel_bulk_job, get_bulk_job_report, send_group_broadcast

Not in this ship: template edit/delete via MCP, schedule update, bulk zip/media helpers.

Chatbot

list_chatbot_flows, get_chatbot_flow, create_chatbot_flow, update_chatbot_flow, publish_chatbot_flow, unpublish_chatbot_flow

Requires automation permission. Create/update/publish/unpublish use confirm. Supply valid flowData JSON (portal builders remain the primary canvas UX).

Commerce

Catalog / products: list_catalogs, create_catalog, list_catalog_categories, get_product_list_payload, list_products, create_product, update_product, send_product_list_message, send_single_product_message, send_commerce_flow_message

Orders: list_orders, get_order, update_order_status, add_order_note, notify_order

Flows: list_commerce_flows, get_commerce_flow, create_commerce_flow, update_commerce_flow, publish_commerce_flow

Not in this ship: commerce settings / RSA / enable-cart / catalog Meta sync / flow health / deprecate-delete via MCP.

How to turn it on in ChatYug

  1. Sign in to ChatYug and open API Configuration.
  2. Make sure you have an API key for your WhatsApp Business Account.
  3. Ask support (or your admin) to enable MCP / AI Assistants for your account if it is not already on.
  4. Optional for CLI tools: in MCP Tokens, click Generate MCP Token, copy the mcp_ value once, and store it safely.

Connect your AI assistant

ChatYug MCP connector URL: https://mcp.chatyug.com/mcp

Claude.ai / Claude Desktop (recommended)

  1. Open Settings → Connectors → Add custom connector.
  2. Name: e.g. ChatYug.
  3. Remote MCP server URL: https://mcp.chatyug.com/mcp.
  4. Leave OAuth Client ID and OAuth Client Secret empty (ChatYug registers Claude automatically).
  5. Click Add, then Connect.
  6. Sign in with your ChatYug username and password on the ChatYug authorize page and click Allow.

Claude’s Custom Connector feature may require a paid Claude subscription. That is Claude’s rule, not a ChatYug plan limit.

Sending images / media from Claude.ai

Claude stores attached files in a code-execution sandbox. ChatYug MCP sends the original file over WhatsApp using a one-shot HTTPS upload (the same pattern used by other production Claude connectors)—not by pasting large base64 into tool calls.

One-time setup (required for attached media)

  1. Open Claude Settings → Capabilities → Code execution and file creation → Additional allowed domains.
  2. Add mcp.chatyug.com and save.
  3. In a chat, attach the image (or video/audio/document) and ask Claude to send it via ChatYug.

What the assistant should do

  1. Call prepare_media_upload (returns uploadUrl, curlExample, and browserUploadUrl).
  2. Run the returned curl on the sandbox file path (original bytes), or if egress is still blocked, ask you to open browserUploadUrl in your normal browser and pick the file.
  3. If you used the browser link, poll get_media_upload_status until ready.
  4. Call send_media_message with the returned mediaId.

Do not

  • Compress, resize, or re-encode the file to “make it smaller.”
  • Paste huge base64 into MCP tools (slow and unreliable for normal images).
  • Ask the user to host the file on a public CDN URL.

Org policy blocks allowlisting? Use the short-lived ChatYug upload link Claude provides—open it in your normal browser, pick the original file, then tell Claude to continue.

Meta size caps: image 5MB; video/audio 16MB; document 100MB.

After ChatYug MCP updates: remove and re-add the ChatYug connector, then start a new chat so Claude loads the latest tools and instructions.

Claude Code / other CLI tools (Bearer token)

Generate an MCP token in the portal, then:

claude mcp add --transport http chatyug https://mcp.chatyug.com/mcp --header "Authorization: Bearer mcp_YOUR_TOKEN"

Same pattern works for Gemini CLI and other clients that accept a custom Authorization header.

Where do I paste an mcp_ token?

Only for CLI / Request-header style clients — not required for Claude.ai Connect (that uses ChatYug sign-in).

  • Do not put the token in the connector Name or URL.
  • Do not put the token in Claude’s OAuth Client ID / Secret boxes.
  • Optional: Claude Request headers beta can still use authorization = Bearer mcp_….

ChatGPT

  1. Turn on Developer mode if required for your plan.
  2. Create a custom connector with URL https://mcp.chatyug.com/mcp.
  3. If ChatGPT starts an OAuth / sign-in flow, complete ChatYug login on the authorize page.
  4. If it asks for API key / Bearer instead, use Bearer mcp_YOUR_TOKEN from the portal.

Gemini

Gemini web — Connected Apps (custom app)

Gemini requires a static OAuth Client ID and Client secret (unlike Claude, which auto-registers).

  1. In Gemini, open Set up a custom connected app, enter URL https://mcp.chatyug.com/mcp, expand Advanced settings.
  2. Click Copy redirect URI.
  3. Open https://mcp.chatyug.com/oauth/gemini-setup, paste that redirect URI, and create credentials.
  4. Paste the generated Client ID and Client secret into Gemini Advanced settings → Next.
  5. Sign in with your ChatYug username/password and click Allow.

Gemini CLI

gemini mcp add chatyug https://mcp.chatyug.com/mcp --transport http --header "Authorization: Bearer mcp_YOUR_TOKEN"

Gemini Enterprise custom MCP datastore

Same ChatYug OAuth endpoints: Authorization https://mcp.chatyug.com/oauth/authorize, Token https://mcp.chatyug.com/oauth/token. Create Client ID/Secret via the Gemini setup page (use redirect https://vertexaisearch.cloud.google.com/oauth-redirect if that is what Google shows).

Other MCP-compatible assistants

Prefer OAuth Connect when the client supports it (same URL). Otherwise use URL + Authorization: Bearer mcp_YOUR_TOKEN.

Plans and safety

  • Trial — your assistant can look up and list information (read-only).
  • Monthly or Annual — your assistant can send messages and update Messaging, CRM, Marketing, and Commerce data as allowed by ChatYug. Platform fees: see ChatYug pricing.
  • Never share your MCP token in chat, email, or public docs.
  • Revoke any token that might have been exposed.
  • Bulk, broadcast, schedule run/cancel, and similar writes require an extra confirmation step so accidental fan-out is harder.

How ChatYug MCP compares

Hosted BSP MCP products, DIY open-source Cloud API MCP servers, and unofficial WhatsApp Web MCP projects all appear in the market. ChatYug MCP is an India-focused Meta BSP connector for Messaging, CRM, Marketing, Commerce, and Chatbot (Claude OAuth Connect + Bearer mcp_ for CLI). For a category comparison table and official-vs-unofficial guidance, see ChatYug MCP overview and WhatsApp MCP in India 2026. ChatYug does not claim to be the first BSP with MCP.

FAQ

Marketing FAQs (what MCP is, Claude connect, trial read-only, official vs unofficial) live on the product page: ChatYug MCP FAQ. Keep this guide for setup steps and the tool catalog; use the landing FAQ as the canonical Q&A set for search and AI citation.

For technical setups

CLI / static header:

Authorization: Bearer mcp_YOUR_TOKEN

OAuth access tokens from Connect use the mcat_ prefix and are issued after ChatYug sign-in. Do not put tokens in the URL query string.

Paid token scopes may include messaging:*, crm:*, marketing:*, and commerce:*. Legacy paid tokens that already have messaging:write continue to receive Marketing and Commerce write access for this release.

Related