A
licenseNot graded
qualityD
maintenanceA SQLite-backed message queue system that enables multiple AI agents to communicate with each other via a simple HTTP interface.
4
Apache 2.0
Signal MCP
by b-1000R4
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Signal MCPCreate a work item to migrate the user data to the new schema"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Signal MCP
Signal is a lightweight MCP work queue for AI agents.
It provides a small set of tools for creating, claiming, starting, handing off, failing, completing, and reviewing durable work items through MCP.
Signal is intentionally simple.
v0.1.0
The first release provides a basic agent work lifecycle:
created
↓
claimed
↓
in_progress
↓
completedWith additional paths for:
handoff
failedRelated MCP server: agent-handoff-mcp
MCP Tools
Tool | Description |
| Check that Signal and SQLite are available |
| Create a new Signal work item |
| Retrieve a Signal by ID |
| List recent Signals |
| Assign a Signal to an agent |
| Mark a claimed Signal as in progress |
| Transfer a Signal to another agent |
| Mark a Signal as failed |
| Mark a Signal as completed |
Stack
TypeScript
Model Context Protocol
Streamable HTTP
SQLite
Docker
Docker Compose
Connect
Signal exposes an MCP endpoint at:
Run
cp .env.example .env
docker compose up -dBy default, Signal is exposed at:
http://localhost:3002/mcpThe container listens internally on port 3000.
Persistence
Signal stores work state in SQLite.
The Docker Compose setup mounts the database outside the container so work survives container replacement and restarts.
Status
v0.1.0 is intentionally small.
The goal of this release is to establish a simple, durable MCP work queue before adding more advanced features such as milestones, dependencies, events, artifacts, reviews, or workflow policies.
Those features will be shaped by actual agent usage rather than added in advance.
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues
Related MCP Connectors
- OctopadOAuthapp.octopad
The back-office workspace for your team's AIs: tasks, knowledge and context shared over MCP.
Durable background job execution, async task scheduling, and state persistence for AI agents.
MCP-first toolbox for agents: KV storage, auth, queue, and utility tools. Free in early access.
- llm-busOAuthcom.llm-bus
Coordinate multiple AI agents over MCP: atomic claims, leases, shared ledger, handoffs, tasks.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to exchange structured work items with an auditable lifecycle, supporting send, acknowledge, block, complete, and cancel operations via a shared SQLite-backed inbox.2Apache 2.0
- FlicenseNot gradedqualityCmaintenanceProvides a self-hosted shared work queue for AI agents via MCP, using a local SQLite database for task management.-
- AlicenseNot gradedqualityBmaintenanceEnables any MCP-compatible agent to manage coworker agents with task queues, human approvals, schema-validated handoffs, memory, and trace logging, with local-first storage in ~/.workerlane.10 npmMIT