Muro Live Chat & AI Support Inbox vs Weav
A side-by-side look at the Muro Live Chat & AI Support Inbox and Weav MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
Muro Live Chat & AI Support InboxSupport & Service ManagementLive chat + AI support inbox: list, triage, and reply to customer conversations; configure widgets.38FairAuth: not declaredVerdict: choose Muro Live Chat & AI Support Inbox for support & service management work; choose Weav for support & service management over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
MChoose Muro Live Chat & AI Support Inbox when
- You need dedicated capabilities in the Support & Service Management domain.
Choose Weav when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
status, priority, type.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M Muro Live Chat & AI Support Inbox | |
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 38/100 · Fair | 47/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Muro Live Chat & AI Support Inbox | View Weav |
Tools & capabilities
Muro Live Chat & AI Support Inbox tools
No tool names declared yet. Check the project README from the listing page.
Weav tools 3
status`open` or `closed`priority`low`, `normal`, `high`, or `urgent`type`text`, `qa`, or `url`
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Muro Live Chat & AI Support Inbox
No confirmed install command for Muro Live Chat & AI Support Inbox yet — follow the setup steps linked from its listing page rather than a guessed package name.
Weav
{
"mcpServers": {
"weav": {
"url": "https://mcp.weav.com/mcp"
}
}
}
Frequently asked questions
Muro Live Chat & AI Support Inbox is categorized under Support & Service Management and uses an install path we have not confirmed yet. Weav belongs to Support & Service Management and uses a remote HTTP/SSE transport. Pick Muro Live Chat & AI Support Inbox for support & service management work and Weav for support & service management.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Muro Live Chat & AI Support Inbox has no confirmed install command yet — follow its own setup instructions.
Muro Live Chat & AI Support Inbox has no declared pricing — check the project's own site. Weav has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add muro-live-chat-ai-support-inbox and weav as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Muro Live Chat & AI Support Inbox has a quality signal of 38/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Weav has 47/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.