Weav logo

Weav

Connects AI clients to an authenticated Weav workspace for conversations, customers, training data, and Help Center management.

Install Weav

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://mcp.weav.com/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Overview

The Weav MCP server connects AI clients to an authenticated Weav workspace through the remote Streamable HTTP endpoint at https://mcp.weav.com/mcp. It provides tools for searching and updating conversations, looking up customers, managing agent training data, and maintaining Help Center content. Workspace administrators or owners authorize access through OAuth, making it suitable for support operations, knowledge maintenance, and customer-service workflows.

Use cases

  • Search and triage support conversations
  • Reply to customers from an AI client
  • Update conversation status, priority, or assignment
  • Manage agent training sources
  • Create and maintain Help Center articles

Key features

  • OAuth-authenticated remote MCP connection
  • Conversation search, replies, and updates
  • Customer and conversation lookup
  • Agent training-data management
  • Help Center article and revision management
  • Multilingual article and SEO field support

Tools3

What Weav lets your agent do. Expand a tool for its parameters.

Self-reported~24 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

9/9 checks healthy over the last 51d

Supply-chain signal

1 high-severity advisory on record for this package. Most advisories affect transitive dependencies and may not be exploitable in this server's actual usage — this is a directional signal, not a security audit.

Critical 1High 0Medium 0Low 0

Scanned 9/7/2026 via OSV.dev · https://mcp.weav.com/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit20d agoMost recent push to the default branch.
Tools exposed3Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Weav works

What Weav MCP server does

The Weav MCP server gives MCP-compatible AI applications access to a Weav workspace. Its 32 tools cover four areas: conversations, customers, agent training data, and the public Help Center knowledge base.

Conversation tools can search inbox content, retrieve recent messages, send replies as a workspace teammate, and change status, priority, or assignment. Customer tools search by name or email and return profiles, company information, and recent conversations.

Training-data tools work with the material used by Weav AI agents. They can find, retrieve, add, delete, and resync items. New sources may be text, question-and-answer content, or website URLs. Help Center tools cover categories, articles, translations, revisions, improvement proposals, publishing state, and soft deletion.

How it works

Weav hosts the remote MCP service at https://mcp.weav.com/mcp using Streamable HTTP. An AI client connects to that endpoint, then a Weav workspace administrator or owner completes OAuth consent in a browser. Once authorized, the client can call tools against the connected workspace until the authorization is revoked.

The workspace server documented here is different from Weav's unauthenticated public server at https://weav.com/mcp. The public server answers pricing and product questions but cannot access inboxes, customers, training data, or Help Center data.

Setup and configuration

Configure an MCP client with the Streamable HTTP URL:

text
https://mcp.weav.com/mcp

Authentication is handled through OAuth, and consent must be completed by a workspace admin or owner. After connection, the client can retain access until the authorization is revoked.

Tools and capabilities

The Weav MCP server exposes these functional groups:

  • Conversation search and retrieval, customer replies, and conversation updates.
  • Customer search and profile retrieval.
  • Agent training-data search, retrieval, creation, deletion, and URL resynchronization.
  • Help Center overview, category and article listing, article search, and full article retrieval.
  • Article revision listing, retrieval, and restoration.
  • Read-only improvement-proposal listing and retrieval.
  • Help Center article creation, updates, publishing, unpublishing, soft deletion, and translation deletion.

Many list and search operations support pagination or limits from 1 to 50. Conversation searches can filter by status and channel, while Help Center searches can filter by locale, publication status, category, or uncategorized state. Article changes may use an expected version, and editing existing translation content creates a revision.

Limitations and notes

Access is limited to the authorized Weav workspace and depends on the permissions granted through OAuth. Sending a reply changes a real conversation, and training-data additions are automatically available to every agent in the workspace. Deleting URL training data also removes its discovered URLs and chunks.

Agent training data and Help Center content are separate systems. The *_training_data tools manage sources used by Weav AI agents; the kb_* tools manage public Help Center articles and categories. Conversation updates do not delete conversations, and Help Center article deletion is described as a soft delete.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Weav

Weav is an MCP server that connects AI clients to an authenticated Weav workspace. Its main tools search and update conversations, look up customers, manage agent training data, and create, revise, publish, or delete Help Center content through the remote Streamable HTTP endpoint.

Configure your MCP client to use https://mcp.weav.com/mcp. The server is remote and uses Streamable HTTP, so no local installation or environment variables are specified. A Weav workspace administrator or owner must complete the OAuth consent flow in the browser.

It authenticates with OAuth through the hosted Weav MCP endpoint. A workspace admin or owner completes consent in a browser, after which the connected client can access authorized workspace data until the connection is revoked.

It manages conversations, customers, agent training data, and Help Center content. Available operations include searching conversations and customers, sending replies, changing conversation metadata, adding or deleting training sources, and creating or updating Help Center articles.

No. This workspace server uses OAuth at https://mcp.weav.com/mcp and can access workspace data. The public server at https://weav.com/mcp does not require login but cannot read inbox, customer, training-data, or Help Center information.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewWeav AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/weav?style=directory)](https://allmcps.com/mcp/weav)
HTML Embed
<a href="https://allmcps.com/mcp/weav"><img src="https://allmcps.com/api/badge/weav?style=directory" alt="Weav on AllMCPs" /></a>