MCP.Market

Weav MCP server

online · 100% uptime
by weav.com·com.weav/mcp·v1.3.0

Connect AI tools to Weav customer service. Triage conversations, reply, and manage your Help Center.

A97/100grade A
What users say
No reviews yet
Be the first
Safety scan
A97/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Weav yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Weav tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 314ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 18 days ago15/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace8/10
Overall 97/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Weav compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
97/100
higher than 98% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
278 ms
faster than 51% of 30,031 servers

Release history: 4 versions in the registry since 2026-08-27, latest 2026-10-12, typically one every 7 days.

Install Weav in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp https://mcp.weav.com/mcp
Add to Cursor

What the publisher says

From the Weav repository's README, as published. We do not edit it. Read it on GitHub

Weav.com Model Context Protocol (MCP)

Learn how to use the Model Context Protocol (MCP) to enable AI agents to securely access and interact with your Weav workspace.

The Weav MCP server is available for Weav workspaces.

This repository documents the workspace server (com.weav/mcp at https://mcp.weav.com/mcp). A separate public server answers pricing and product questions without login:

The public server cannot read inbox, customers, or knowledge base data. Source: dubdubdubco/weav-site-mcp.

What is Model Context Protocol?

MCP is a protocol that enables AI tools and applications to connect with Weav's data and services in a secure, standardized way. It provides a structured method for AI models to:

  • Find and retrieve Weav data (conversations, customers, knowledge base)
  • Access specific tools and functionality provided by Weav
  • Maintain context about your Weav workspace when working with AI assistants

How MCP Works

Weav hosts a remote MCP server that follows the authenticated remote MCP specification (docs). This server handles requests from AI tools and provides access to Weav data through a secure interface.

Connection URL:

  • Streamable HTTP: https://mcp.weav.com/mcp

When an AI tool or application needs to access Weav data:

  1. The tool connects to Weav's MCP server
  2. A workspace admin or owner completes OAuth consent in the browser
  3. The tool can then access relevant Weav data and functionality for that workspace
  4. The connection remains live until it is revoked

Benefits of Using MCP

  • Secure Access: All data access is authenticated and authorized. Only a workspace admin or owner can finish consent.
  • Standardized Interface: Consistent interaction pattern across different AI tools
  • Contextual Understanding: AI assistants maintain awareness of your Weav inbox, customers, and knowledge base
  • Increased Development Efficiency: Triage conversations, reply to customers, and update your knowledge base from the AI tools you already use

Available Tools

The Weav MCP server provides 11 tools for interacting with your workspace.

Conversations

searchconversations**

Search support conversations the same way the Weav inbox does.

Key Features:

  • Matches subject, customer name, or email
  • Only returns conversations that have at least one message
  • Spam is excluded unless spam is true
  • Optional filters: status (open, closed), channel (email, chat), limit (1–50)

getconversation**

Get a conversation, including recent messages.

Key Features:

  • Use the conversation UUID returned from search_conversations
  • Returns conversation metadata and recent message history

sendreply**

Post a reply to a conversation as a workspace teammate.

Key Features:

  • Requires conversation_id and content
  • Sends the reply in the connected workspace

updateconversation**

Update a conversation's status, priority, or assignee. Does not delete conversations.

Key Features:

  • status: open or closed
  • priority: low, normal, high, or urgent
  • assigneeid plus assigneetype (user or agent); omit to leave unchanged, send null to unassign

Customers

searchcustomers**

Search customers by name or email.

Key Features:

  • Optional query and limit (1–50)

getcustomer**

Get a customer profile, company, and recent conversations.

Key Features:

  • Use the customer UUID returned from search_customers

Knowledge base

searchtrainingdata

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Weav: common questions

Is Weav MCP server safe?
Yes, by our scan: it is graded A (97/100). Read the Weav safety report
How do I install Weav?
It runs remotely at mcp.weav.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Weav need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Weav maintained?
The last commit was 23 days ago (2026-10-12). The latest release is v1.3.0.
Is Weav up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Weav compare with other MCP servers?
safety score 97/100 (higher than 98% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 278 ms (faster than 51% of 30,031 servers). Full comparison.