muro - Live Chat & AI Support Inbox

chat.muroPublished by muro.chatOfficial publisherv1.0.0Updated Oct 24, 2026

Live chat + AI support inbox: list, triage, and reply to customer conversations; configure widgets.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Lets an assistant list, triage and reply to customer live-chat conversations and configure chat widgets in muro.

What you can do
This remote MCP server connects an assistant to the muro live chat and AI support inbox. According to the registry description, it lets the assistant list, triage and reply to customer conversations, and configure widgets. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth adding when support agents or teams want an assistant to work inside their muro inbox: reviewing incoming conversations, sorting them, drafting or sending replies, and adjusting widget settings. It is not useful if you do not use muro for customer chat.
Requirements
A remote streamable HTTP endpoint at nothing runs locally. A muro API key is required and sent as a Bearer token in the Authorization header; the key is created in the muro dashboard under Settings > API keys. Network access to the endpoint is needed.
Before you install
The server requires a muro API key (Authorization header), which is a secret and should be handled as one. Because it can reply to customer conversations and change widget configuration, assistant actions may send messages to customers or alter live support settings; review before granting write access.

Installation

In SourceWeft

  1. Open muro - Live Chat & AI Support Inbox in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/chat.muro%2Fsupport/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "muro-live-chat-ai-support-inbox": {
      "type": "http",
      "url": "https://muro.chat/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.