toolweave

io.github.andreysparishPublished by GitHub account andreysparishv1.0.0Updated Oct 24, 2026

One MCP endpoint for Claude, GPT & Gemini: 100+ tools + no-code connectors + agent workers.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A remote MCP endpoint that gives assistants access to a large shared tool library, no-code connectors and agent workers.

What you can do
Access a shared library of more than 100 tools through a single MCP endpoint, intended for use with Claude, GPT and Gemini. Use no-code connectors to link external services without writing integration code. Run agent workers as part of the same endpoint. The manifest lists no individual tools, so the exact capabilities are not documented here.
When to use it
Consider it when you want one hosted endpoint that covers many tools across several assistant platforms, and prefer no-code connectors over building integrations yourself. Check the provider's own documentation first, since the available tools are not listed.
Requirements
A remote connection to the hosted endpoint at toolweave.dev over streamable HTTP. OAuth authentication is required. No environment variables or headers are declared.
Before you install
Access is granted through OAuth, so review which permissions the provider requests before authorizing. The server is hosted by a third party, so tool inputs and outputs pass through it. The manifest lists no tools, so what the tools can read, write or send cannot be verified from this listing.

Installation

In SourceWeft

  1. Open toolweave 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.github.andreysparish%2Ftoolweave/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": {
    "toolweave": {
      "type": "http",
      "url": "https://toolweave.dev/mcp"
    }
  }
}

README

This repository has no README.

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

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.