# Asyntai Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Asyntai

Manage your website's AI support chatbot: knowledge base, conversations, leads and live chat replies.

- Record: https://musedirectory.ai/connector/asyntai
- Category: Productivity
- Developer: Asyntai (https://asyntai.com/documentation/mcp/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 530ms, checked 2026-09-28T09:16:00Z
- Endpoint: https://asyntai.com/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-09-24T11:10:55Z)
- Source: Found in the official MCP Registry (com.asyntai/support-agent) https://registry.modelcontextprotocol.io/v0/servers?search=com.asyntai%2Fsupport-agent

Connect to your Asyntai account to manage AI support agents on your websites. Add knowledge, configure chatbot behavior, view conversations and leads, track analytics, and manage products and bookings through your chat widget.

Example request: "Show me the support conversations from my website this week and what questions my chatbot couldn't answer."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Asyntai to help me. It is a free service with an MCP server at https://asyntai.com/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- list_websites: List the websites (AI agents) on this Asyntai account, with the id every other tool takes. Start here when the account may have more than one.
- get_account: Get the signed-in account's email, plan, and how many chat messages it has used against its monthly allowance.
- list_plans: List every Asyntai plan with its price, monthly message allowance and the features it includes, alongside the plan this account is on. Use it to answer which plan someone should move to, and why.
- search_asyntai_docs: Search Asyntai's own product documentation and get back the pages that match, with a short excerpt from each. Use this to find out how a feature works before changing anything, rather than guessing. This searches Asyntai's documentation, NOT the customer's own content: for that, 
- get_asyntai_doc: Read one page of Asyntai's documentation in full, given the url or slug from search_asyntai_docs, for example /documentation/mcp/ or just mcp.
- get_website: Get the full record for one website: its name, domain, platform, widget id and the embed code to paste into the site.
- create_website: Add a new website (a new AI agent) to the account and return its embed code. Each plan allows a limited number of websites, and this refuses once that limit is reached. By default it also starts a crawl of the site to build the knowledge base.
- get_widget_settings: Read all appearance and behaviour settings for one website's chat widget: colours, greeting, position, auto-trigger, data collection, bookings and the rest. Also returns which settings this account's plan cannot change, and the plan each of those needs.
- update_widget_settings: Change one or more chat widget settings. Pass an object of setting name to new value; read them with get_widget_settings first. Changes are live for every visitor at once. Settings the plan does not include are refused with the plan they need, and nothing is written unless every 
- set_data_feed: Point the chatbot at a product feed and index it. This fetches the feed, checks it really is a feed, clears whatever was indexed before, and rebuilds the index in the background. Send an empty url to remove the feed. Needs the Standard plan or higher.
- set_data_feed_max: Same as set_data_feed, for the Max tier, which indexes a larger catalogue. Fetches, validates, clears the old index and rebuilds it in the background. Needs the Pro plan or higher.
- set_access_tags: Switch Access Tags on or off for one website. Turning it on creates the signing secret your server needs to sign visitor entitlements. Needs the Enterprise plan.
- set_widget_pinning: Freeze the chat widget at its current version, so the site always serves the same copy with an integrity hash. Turning it on builds that snapshot and changes the embed code. Needs the Enterprise plan.
- get_website_features: Read the plan-gated features for one website: Real-Time Data Feed and its Max tier, Product Cards, Dynamic Images, User Context, Link Parameters, Chat Retention, Chat Categories, Access Tags, Widget Pinning, Zero Retention, PII Redaction and the Output Classifier. Shows current v
- update_website_features: Turn website features on or off and set their values, for example the Real-Time Data Feed URL or the PII Redaction rules. Pass an object of field name to value; read them with get_website_features first. A feature the plan does not include is refused with the plan it needs. These
- search_knowledge_base: Search one website's knowledge base and return the passages the chatbot would retrieve for this question, with a relevance score. Use this to check what the chatbot knows about a topic. It does not generate an answer and does not use the message allowance.
- list_knowledge: List the sources in one website's knowledge base: uploaded text, documents, added pages and crawls.
- add_knowledge_text: Add a titled block of text to one website's knowledge base. The chatbot can use it in answers as soon as this returns. Adds a new entry; it never replaces an existing one.
- delete_knowledge_entry: Permanently delete one knowledge base entry and every passage built from it. The chatbot stops using that content immediately. This cannot be undone.
- get_ai_instructions: Get the instructions that shape how one website's chatbot answers: its role, tone and rules.
- update_ai_instructions: Replace one website's AI instructions with new text. This overwrites the current instructions and changes how the live chatbot answers every visitor. Read them with get_ai_instructions first, and show the user what will change before calling this.
- get_knowledge_entry: Read the stored text of one knowledge base entry. Works for the content you supplied: text, documents, spreadsheets, single pages and videos. A website crawl is listed but not exported, because the source is your own public site.
- add_knowledge_url: Fetch one web page and add its text to the knowledge base. Use this for a single page. To take in a whole site, use start_crawl instead.
- set_knowledge_tags: Restrict who can retrieve one knowledge base entry. A visitor must present a matching tag, signed by your own server, before the chatbot will use the entry. Send an empty list to make it public again. Access Tags needs the Enterprise plan.
- start_crawl: Crawl a website and add its pages to the knowledge base. Runs in the background; check on it with list_crawls. Each plan caps the pages per crawl, and asking for more than the cap is refused.
- list_crawls: List recent crawl jobs for one website with their status, how many pages they took, and why each one stopped.
- list_conversations: List recent visitor conversations for one website, newest first, with the session id, message count and any email or phone the visitor gave.
- get_conversation: Read the full message history of one conversation, in order, from its session id.
- list_leads: List the email addresses and phone numbers visitors left in chat, newest first, with the page they were on.
- get_analytics: Summarise one website's chat activity over a period: conversations, messages, leads captured, escalations, and the countries visitors came from.
- list_knowledge_gaps: List the Knowledge Gaps Asyntai recorded: real visitor questions the chatbot could not answer. Use this to find what to fill in with add_knowledge_text. Needs the Standard plan or higher.
- list_images: List the images the chatbot may show a visitor, with the description that tells it when each one is relevant.
- add_image: Add an image the chatbot may show. The description is what the AI reads to decide when the image answers the question, so describe what it shows and when it helps.
- delete_image: Remove one image so the chatbot stops showing it.
- list_products: List the products the chatbot can show as cards, with price and links. Product Cards needs the Standard plan or higher.
- add_product: Add a product the chatbot can show as a card. Needs the Standard plan or higher.
- delete_product: Remove one product so the chatbot stops offering it.
- list_booking_types: List the appointment types visitors can book, with length, price and how many spots each has. Bookings needs the Standard plan or higher.
- list_embeds: List the third-party tools embedded in the chat, such as a booking calendar or a form. Embeds needs the Standard plan or higher.
- list_tickets: List support tickets raised from chat, with status, priority and the visitor's details. Needs the Standard plan or higher.

Screening checks:
- MCP handshake: pass (Answered in 81ms)
- Domain against threat feeds (Cloudflare security DNS): pass (asyntai.com not flagged)
- Published packages against the OSV malicious-package database: pass (No malicious-package advisories)
- Hidden instructions or invisible characters in tool text: pass (54 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 977 days ago)
- AI review of purpose and tool behavior: pass (No concerns)