AgentHub - Lean MCP Orchestrator

io.github.propstreetPublished by GitHub account propstreetv1.1.1Updated Oct 24, 2026

Enables coding agents to coordinate edits, reviews, and escalations without file locking conflicts

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Lets coding agents coordinate edits, reviews, and escalations so they can work on the same codebase without file-locking conflicts.

What you can do
AgentHub is a lean MCP orchestrator for coding agents. According to its registry description, it enables agents to coordinate edits, reviews, and escalations without file locking conflicts. It runs as a local stdio process, and the manifest lists no tools, so the concrete operations it exposes are not documented in the supplied material.
When to use it
Consider it when several coding agents work on the same repository and you want them to hand off edits, request reviews, or escalate conflicts instead of colliding over files. It is a desktop-only local process, so it is not meant for browser or hosted use.
Requirements
Runs as a local process on the user's machine over stdio, distributed as the npm package @propstreet/agenthub, so a Node.js runtime is needed. The manifest declares no authentication, environment variables, or headers.
Before you install
The manifest declares no credentials, but the server is described as coordinating edits to code, so agents using it may change files in your working tree. Review what it writes before trusting it on an important repository. No tool list is published, so verify its actual behavior after installing.

Installation

In SourceWeft

  1. Open AgentHub - Lean MCP Orchestrator 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.

Tools

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

Version history

1
  1. v1.1.1LatestSep 16, 2026

Score

25% 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

    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.