Weavz

io.weavzPublished by weavz.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Governed app access for AI agents: 1,000+ apps & 12,000+ tools via Code Mode MCP.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Weavz is a remote MCP endpoint that gives AI assistants governed access to over 1,000 apps and 12,000 tools through a Code Mode MCP interface.

What you can do
Connect an assistant to a large catalog of third-party apps and tools through a single governed endpoint, described as Code Mode MCP access to 1,000+ apps and 12,000+ tools. The manifest lists no individual tools, so the exact actions available depend on the apps enabled in the Weavz platform account.
When to use it
Consider it when an assistant needs to reach many different business apps and tools through one managed, governed connection rather than installing a separate MCP server for each service.
Requirements
A remote streamable HTTP endpoint at platform.weavz.io, with OAuth authentication required. A Weavz platform account and whatever app connections are configured there. No environment variables or headers are declared.
Before you install
Access is governed through a Weavz account, so the assistant can act on whatever apps and tools that account has enabled, potentially including actions that write or change data in third-party services. Review which apps and permissions are granted before connecting, and note that data flows through the Weavz platform.

Installation

In SourceWeft

  1. Open Weavz in the dashboard and add it to a workspace.
  2. Connect the required 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/io.weavz%2Fweavz/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "weavz": {
      "type": "http",
      "url": "https://platform.weavz.io/mcp/weavz"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

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.