Supovia Customer Support

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Reply to and resolve customer chats, search your help docs and see which conversations need you.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Supovia Customer Support": {
      "url": "https://mcp.supovia.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (15)

• list_websites read-only

  Use this when someone asks which websites their Supovia support chat runs on, or a website's id is needed. Returns each website's id, name, domain and whether its AI customer agent is on, most recently edited first, 20 per page by default. Not for customer conversations.

  Parameters:

  • limit — integer — Websites per page, from 1 to 50; defaults to 20
  • cursor — string — The page.nextCursor of the previous page; absent for the first page

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_website read-only

  Use this when someone asks about one of their Supovia websites by name or id, such as whether its AI customer agent is on. Returns the website's id, name, domain, AI-agent status and created and edited times, or not-found. Not for the help articles published on it.

  Parameters:

  • idOrName (required) — string — Website id, exact vanity id (its lowercase public address) or exact display name

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_conversations read-only

  Use this when someone asks which customer conversations are open, unread or recently active, optionally for one website. Returns conversation ids with website, channel, resolved flag, unread count and times, most recent activity first, 20 per page by default (no message text or customer details). Not for open-conversation totals.

  Parameters:

  • limit — integer — Conversations per page, from 1 to 50; defaults to 20
  • cursor — string — The page.nextCursor of the previous page with the same filters; absent for the first page
  • resolved — boolean — true for resolved conversations, false for open ones; omit for both
  • websiteId — string — Only conversations on this website; every website when absent

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_conversation read-only

  Use this when someone asks about one customer conversation's status, such as whether it is resolved or unread and how many messages the customer, staff and AI agent sent. Returns its channel, status, unread count, times and sender counts from the latest 50 public messages (no message text or internal notes). Not for reading or quoting what was said.

  Parameters:

  • conversationId (required) — string — Conversation id, up to 200 characters

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_unresolved_conversation_counts read-only

  Use this when someone asks how many customer conversations are still open or unresolved, in total or per website. Returns the total plus a per-website count, largest first, listing up to 100 websites (no customer or message data). Not for finding which conversations are open.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_documents read-only

  Use this when someone asks which help articles or support docs exist, optionally for one website, language or article. Returns each article's id, title, slug, language, website and published flag, most recently edited first, 20 per page by default, without the article text. Not for finding articles about a topic.

  Parameters:

  • limit — integer — Articles per page, from 1 to 50; defaults to 20
  • cursor — string — The page.nextCursor of the previous page with the same filters; absent for the first page
  • locale — string — Only articles in this language code, e.g. en, it or fr; every language when absent
  • websiteId — string — Only articles on this website; every website when absent
  • slugOriginal — string — Only the language versions of one article: its original slug before translation

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_document read-only

  Use this when someone needs the text of one help-center article, to quote it or answer a customer from it. Returns the article's title, slug, language, published flag and text up to 20000 characters, with the text's format (html, markdown, plain-text). Not for finding articles on a topic.

  Parameters:

  • slug — string — Article slug, used only when documentId is omitted
  • locale — string — Language code for the slug lookup, e.g. en, it or fr; defaults to en
  • documentId — string — Article id; takes precedence over slug

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• search_documents read-only

  Use this when someone asks which help article covers a topic or question on one of their websites. Returns up to 5 matching published articles with id, title, slug and language, matched by meaning in one language (English by default). Not for reading an article's text.

  Parameters:

  • query (required) — string — What the article should cover, in natural language, up to 500 characters
  • websiteId (required) — string — Website whose help center to search
  • locale — string — Language code to search in, e.g. en, it or fr; defaults to en

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_campaigns read-only

  Use this when someone asks which email campaigns one of their websites has. Returns each campaign's id, name and created and edited times, 20 per page by default (no recipients, subject or content). Not for sending a campaign.

  Parameters:

  • websiteId (required) — string — Website whose campaigns to list
  • limit — integer — Campaigns per page, from 1 to 50; defaults to 20
  • cursor — string — The page.nextCursor of the previous page for the same website; absent for the first page

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• send_message destructive

  Use this when the user approves an exact reply to send to a customer in one Supovia conversation. Returns the conversation id and send time. The reply reaches the customer on the conversation's own channels (chat, email, WhatsApp or Messenger); replies to app-store reviews are public. Not for internal notes or closing the conversation.

  Parameters:

  • conversationId (required) — string — Conversation to reply in
  • content (required) — string — Exact reply text the user approved, 1 to 4,000 characters
  • idempotencyKey (required) — string — Unique key you generate for this conversation and text, up to 255 characters; reuse it only to retry the same send

  Hints: read-only no · destructive yes · idempotent yes · open-world no

• resolve_conversation destructive

  Use this when someone wants to mark a customer conversation resolved or done, or reopen it. Returns the conversation id, resolved state and last edit time, and the operator dashboard updates live. Repeating the same state has no further effect. Not for replying to the customer.

  Parameters:

  • conversationId (required) — string — Conversation to update
  • resolved — boolean — true to mark it resolved (the default), false to reopen it

  Hints: read-only no · destructive yes · idempotent yes · open-world no

• open_supovia read-only

  Use this when someone wants to open Supovia and browse their workspace interactively. Support websites, conversation activity and help articles. Starts with up to 100 items. Not for changing data.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• show_support_overview read-only

  Use this when someone wants a quick visual summary of their customer support. Returns a card with up to 20 websites (name, domain, AI agent on or off) and the 20 most recently active conversations (channel, open or resolved, times), optionally for one website. Not for complete open-conversation totals.

  Parameters:

  • websiteId — string — Only this website; every website when absent

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• show_customer_inbox read-only

  Use this when someone wants to see their unread customer conversations in an inbox view. Returns how many of the 50 most recently active conversations have unread messages; the view lists up to 20 with channel, status, unread count and times (no message text or customer details). Not for complete open-conversation totals.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• open_customer_inbox_conversation read-only

  Use this when the embedded Supovia inbox opens a conversation the user selected. Returns whether it was found and gives the view its channel, status, unread count and times (no message text or customer details). Not for questions asked in chat.

  Parameters:

  • conversationId (required) — string — Conversation id the user selected in the inbox view

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.