Skip to main content
Glama
deenesjakoruzh
b-1000R4

Signal MCP

by b-1000R4
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

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
  ↓
completed

With additional paths for:

handoff
failed

Related MCP server: bot-relay-mcp

MCP Tools

Tool

Description

signal.ping

Check that Signal and SQLite are available

signal.create

Create a new Signal work item

signal.get

Retrieve a Signal by ID

signal.list

List recent Signals

signal.claim

Assign a Signal to an agent

signal.start

Mark a claimed Signal as in progress

signal.handoff

Transfer a Signal to another agent

signal.fail

Mark a Signal as failed

signal.complete

Mark a Signal as completed

Stack

  • TypeScript

  • Model Context Protocol

  • Streamable HTTP

  • SQLite

  • Docker

  • Docker Compose

Connect

Signal exposes an MCP endpoint at:

http://localhost:3002/mcp

Run

cp .env.example .env
docker compose up -d

By default, Signal is exposed at:

http://localhost:3002/mcp

The 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 installed

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd
F
license - not found
Not graded
quality - not tested
C
maintenance

How are these scores calculated?

Maintenance

–Maintainers
–Response time
–Release cycle
–Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

  • bot-relay-mcp

    Maxlumiere
    A
    license
    A
    quality
    A
    maintenance
    MCP coordination primitive for multi-agent workflows. Lets multiple AI coding agents (Claude Code, Cursor, n8n, custom clients) discover each other and exchange messages and tasks via a shared SQLite-backed message bus.
    37
    70
    4
    MIT

  • Claude State MCP Server

    mfitzhenry
    F
    license
    Not graded
    quality
    D
    maintenance
    SQLite-backed MCP server for Claude Code session persistence and multi-agent coordination. Provides tools for session management, event logging, decision tracking, file locking, agent registry, and plan tracking.

  • agent-handoff-mcp

    SarutobiSasuke8
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables 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.
    2
    Apache 2.0

View all related MCP servers

Related MCP Connectors

  • llm-bus

    Coordinate multiple AI agents over MCP: atomic claims, leases, shared ledger, handoffs, tasks.

  • XMemo

    Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.

  • PlanWright

    Control plane for autonomous software labor. Agents claim objectives over MCP with audit trail.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/b-1000R4/signal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server