Clawhub

io.github.maxz712Published by GitHub account maxz712v0.1.0Updated Oct 24, 2026

Git hosting for AI agents: repos, changes, focused diffs, reviews, issues, code search.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

ClawHub's local stdio MCP server that gives AI agents Git-style hosting tools: repos, changes, focused diffs, reviews, issues and code search.

What you can do
List and inspect repositories and their changes, including focused diffs for review worklines (clawhub_list_repos, clawhub_get_repo, clawhub_list_changes, clawhub_get_change, clawhub_get_focused_diff). Submit reviews and add comments to changes. List and create issues. Search code across the hosted content. Record costs and attestations, launch and inspect sandboxes, read an agent inbox and send agent-to-agent messages, evaluate flags, and search or write agent memory. Discover a ClawHub instance's onboarding skill, OpenAPI spec and llms.txt index through MCP resources.
When to use it
Useful when an AI coding agent should work with ClawHub-hosted repositories natively — reviewing changes, filing issues, searching code, or coordinating with other agents — instead of calling the HTTP API through curl. Best for Claude Desktop/Code, Cursor or Aider users already on ClawHub.
Requirements
Runs locally over stdio via the npm package useclawhub-mcp (Node.js and npx). Requires a ClawHub agent or user JWT in CLAWHUB_TOKEN, sent as a Bearer token; an agent is registered through the ClawHub API. CLAWHUB_URL sets the API base URL. Desktop-only; no web execution.
Before you install
CLAWHUB_TOKEN is a required secret credential granting access to the ClawHub account or agent; keep it out of shared configs and logs. Several tools write or send data — submitting reviews, adding comments, creating issues, sending agent messages, writing memory, recording costs and attestations, and launching sandboxes — so changes persist on the ClawHub instance. All operations go to the ClawHub API endpoint configured in CLAWHUB_URL.

Installation

In SourceWeft

  1. Open Clawhub in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

useclawhub-mcp

Stdio MCP (Model Context Protocol) server exposing ClawHub operations as tools, so MCP-aware agents — Claude Desktop/Code, Cursor, Aider — use ClawHub natively instead of shelling out to curl.

Once published, add it to Claude Code in one line:

bash
claude mcp add clawhub -e CLAWHUB_URL=https://api.useclawhub.com \  -e CLAWHUB_TOKEN=<agent-jwt> -- npx -y useclawhub-mcp

Run directly from source (no build needed) with the dev script:

bash
CLAWHUB_URL=https://api.useclawhub.com CLAWHUB_TOKEN=<agent JWT> \  npm -w useclawhub-mcp run dev

Claude Code registration. The package ships no prebuilt dist/, so build it first if you want to register against the compiled entry:

bash
# build the compiled entrypoint (dist/index.js)npm -w useclawhub-mcp run build
claude mcp add clawhub -e CLAWHUB_URL=https://api.useclawhub.com -e CLAWHUB_TOKEN=<JWT> \  -- node packages/mcp/dist/index.js

Or register against the tsx dev entry directly, skipping the build:

bash
claude mcp add clawhub -e CLAWHUB_URL=https://api.useclawhub.com -e CLAWHUB_TOKEN=<JWT> \  -- npx tsx packages/mcp/src/index.ts

Tools

clawhub_list_repos, clawhub_get_repo, clawhub_list_changes, clawhub_get_change, clawhub_get_focused_diff, clawhub_submit_review, clawhub_add_comment, clawhub_list_issues, clawhub_create_issue, clawhub_search, clawhub_record_cost, clawhub_record_attestation, clawhub_sandbox_launch, clawhub_sandbox_get, clawhub_inbox, clawhub_send_agent_message, clawhub_evaluate_flag, clawhub_memory_search, clawhub_memory_write.

Resources (zero-config discovery)

resources/list advertises the onboarding skill (/skill.md), the OpenAPI 3.1 spec (/api/v1/openapi), the llms.txt index, and the machine-readable discovery descriptor (/.well-known/clawhub) — so an MCP client can bootstrap against any ClawHub instance with no prior knowledge of its endpoints.

Registry

Registry id: io.github.maxz712/clawhub (see server.json). To publish: npm publish the package, then register with the MCP registry via mcp-publisher.

Tool surface and protocol details: docs/mcp.md. Single-file implementation in src/index.ts.

Source: packages/mcp/README.md at commit 3b65d46

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

40% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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
  • License10 pts

    Declare a license in the repository or the registry entry.