Skip to main content
Glama
Sign In
deenesjakoruzh
Signal MCP

Signal MCP

by b-1000R4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
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: Agent Task List MCP Server

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    This server cannot be deployed

    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Resources

    Related MCP Connectors

    Related MCP Servers

    • 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.
      56 npm
      2
      Apache 2.0
    • AgentTasker

      AgentTaskerofficial

      BadbotAI
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to create, query, update, claim, hand off, and complete tasks on a local SQLite-backed, project-namespaced kanban board through stdio MCP tools, including filtering for ready/blocked/stale work and exchanging task attachments. It also lets agents list projects and manage statuses, ownership, and evidence without any server or accounts.
      MIT