multi-agenttask-coordinationdeveloper-toolsnotificationsclaude-code
Coordinates coding-agent sessions through a local TaskSwarm server, live status page, notifications, CLI, and generic MCP tool.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Not yet automatically verified
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Choose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Overview
Use cases
Monitor parallel coding-agent sessions across repositories
Receive local alerts when an agent needs review or becomes blocked
Track lightweight development tasks from the CLI
Connect Claude Code lifecycle events to a shared local status page
Key features
Single generic MCP tool wrapping the CLI
Live status page with server-sent events
Local notifications for important session states
Claude Code hook installation
Bearer-token-gated loopback API
Stable JSON output for automation
Capabilities & Tool Schemas
Inspect callable tools, capabilities, and parameters exposed to AI agents by Taskswarm.
Extracted Tool Capabilities
Single generic MCP tool wrapping the CLI
Live status page with server-sent events
Local notifications for important session states
Claude Code hook installation
Bearer-token-gated loopback API
Stable JSON output for automation
How Taskswarm works
What taskswarm does
The taskswarm MCP server exposes the TaskSwarm command-line interface through a single generic MCP tool. TaskSwarm itself is a self-hosted event server for monitoring parallel coding-agent sessions across repositories. Agents can report states such as running, blocked, needs-review, failed, and done.
TaskSwarm maintains a live status page with each session’s repository, agent type, current state, and most recent event time. Updates are delivered with server-sent events, so an open page changes without manual refreshes. State history is also retained for tracked sessions.
When a session reaches a significant terminal or attention-needed state, TaskSwarm emits a local notification. macOS uses osascript; Linux and Windows use a console message and terminal bell. Optional ntfy.sh delivery exists, but it is disabled by default.
How it works
Start the local server with the TaskSwarm CLI, then send status events with agent report-status. The server listens on loopback by default and generates a bearer token on first use. The token is stored in ~/.taskswarm/config.json with restrictive file permissions, and the API plus live page require it. token rotate replaces the token.
The taskswarm MCP server provides an agent-facing route to the CLI rather than defining separate MCP tools for every TaskSwarm command. The underlying CLI returns machine-readable output with --json, including errors, which makes it suitable for automation that should not parse human-oriented terminal text.
Setup and configuration
TaskSwarm can be installed from npm or PyPI under the taskswarm-cli package name. The npm distribution supports a global installation followed by taskswarm start, or execution through npx. The Python distribution is started with the same command. Both distributions use the same event format and notification-deduplication behavior.
After starting the server, use the printed URL to open the status page. A reporting command needs a task identifier, repository path, and state, for example agent report-status --task my-fix --repo ./api --state running.
For Claude Code, hooks install claude-code writes Stop and Notification entries to the current project’s .claude/settings.json. The generated hooks use the installed Node binary and CLI path rather than resolving the package with npx on each invocation.
Tools and capabilities
- Expose the TaskSwarm CLI as one generic MCP tool.
- Start the local event server and print its live status URL.
- Report agent session status with task and repository metadata.
- Add and list local tasks independently of live session events.
- Install Claude Code
StopandNotificationhooks. - Produce stable JSON output for scripting.
- Protect the local API and status page with a bearer token.
Limitations and notes
The taskswarm MCP server’s supplied description does not document a separate MCP configuration format, transport choice, or per-command MCP tool mapping. The README describes the CLI and local event server, so MCP client setup may depend on the surrounding MCP host configuration.
Claude Code’s Stop hook runs after each turn, not only when a whole task is complete. As a result, a long multi-turn session can report done after individual turns. Native system notifications are available only on macOS; other supported desktop platforms use the local console and terminal bell unless an optional external notification path is enabled.
TaskSwarm is designed for local, self-hosted use. The default server binds to loopback, and ntfy.sh is not enabled unless explicitly configured.
Related MCP Servers
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
npm downloads
206
Package downloads in the last 30 days.
Last commit
14d ago
Most recent push to the default branch.
Directory activity
1 views
Config copies, upvotes, and views on AllMCPs.
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Taskswarm
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/taskswarm)HTML Embed
<a href="https://allmcps.com/mcp/taskswarm"><img src="https://allmcps.com/api/badge/taskswarm?style=directory" alt="Taskswarm on AllMCPs" /></a>Technical Specs & Signals
CategoryDeveloper Tools
8/8 checks healthy over the last 43d
43Quality signal: Fair · 43/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership10/20
Documentation & tools16/30
Adoption & activity6/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Supply-chain signal
No high-severity advisories surfaced by our automated scan.
Critical 0High 0Medium 0Low 0
Scanned 4d ago via OSV.dev · taskswarm-cli (npm)
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.