BitsWeave

com.bitsweavePublished by bitsweave.comOfficial publisherv1.0.0Updated Oct 24, 2026

Read and write shared BitsWeave context, projects, tasks, and work sessions through MCP.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

BitsWeave lets an assistant read and write shared context, projects, tasks, and work sessions through a remote MCP endpoint.

What you can do
BitsWeave is a remote MCP server that connects an assistant to shared BitsWeave context, projects, tasks, and work sessions. According to the registry description, it supports both reading and writing this shared data. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when you want an assistant to work with shared project and task data in BitsWeave, for example to look up context or update tasks and work sessions as part of a team workflow.
Requirements
A remote MCP connection to the BitsWeave endpoint over streamable HTTP. OAuth authentication is required, so you need a BitsWeave account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
The server can write as well as read shared context, projects, tasks, and work sessions, so assistant actions may change data other people rely on. Access is granted through OAuth; review which account and permissions you authorize. No tool-level details are published, so confirm what each operation does before relying on it.

Installation

In SourceWeft

  1. Open BitsWeave 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/com.bitsweave%2Fbitsweave/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": {
    "bitsweave": {
      "type": "http",
      "url": "https://bitsweave.com/api/mcp"
    }
  }
}

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 19, 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.