Skip to main content
Glama
Sign In
dassader

steps-mcp

by dassader
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Steps MCP

Steps MCP is an agent-friendly task planning and execution MCP server with durable SQLite storage and a browser UI for reviewing plans and following progress.

Steps MCP workflow board

The board makes the execution state visible at a glance while the MCP surface gives agents compact tools, durable resources, and an explicit next safe action.

Run with Docker

docker run -d \
  --name steps-mcp \
  --restart unless-stopped \
  -v steps-mcp-data:/app/data \
  -p 3001:3001 \
  ghcr.io/dassader/steps-mcp:latest

The /app/data volume stores plans, steps, notes, transitions, attachments, and workflow state.

The latest image is published for linux/amd64 and linux/arm64, so Docker selects the correct platform automatically.

After the container starts:

  • MCP endpoint: http://localhost:3001/mcp

  • User interface: http://localhost:3001/

  • Health check: http://localhost:3001/health

Connect an MCP client to the Streamable HTTP endpoint above. Call server.get_started for the built-in workflow guide, then use the returned prompts, tools, and resource URIs to plan and execute work.

Related MCP server: ContextForge MCP Lab

Workflow

Steps MCP keeps planning, review, execution, verification, and blockers explicit:

  1. Create a draft plan and detailed steps.

  2. Review the plan in the browser UI and record explicit approval.

  3. Start the server-selected next step.

  4. Add durable notes and attachments while work progresses.

  5. Move completed implementation through verification, or record an honest blocker.

Tool responses include the current state, relevant identifiers, and the next safe action so an agent does not need the entire state machine in tool descriptions.

Explicit plan approval before execution

Durable work evidence

Every status transition creates an audit note. Agents can also add standalone notes and attach text, binary evidence, or links without changing step status.

Step description, notes, attachment, and status history

Configuration

Variable

Default

Purpose

HOST

0.0.0.0 in Docker

HTTP bind address

PORT

3001

Container HTTP port

PUBLIC_URL

http://localhost:3001

Base URL returned in browser review links

MCP_ENDPOINT

/mcp

Streamable HTTP MCP path

MCP_STATEFUL

true

Enables stateful MCP sessions

MCP_JSON_RESPONSE

false

Returns JSON responses instead of opening SSE streams

DB_PATH

/app/data/steps.db in Docker

SQLite database path

ALLOWED_ORIGINS

empty

Additional comma-separated browser origins

Local development

Requires Node.js 20 or newer.

npm ci
npm run typecheck
npm test
npm run build
npm start

The default local database is steps.db. Copy .env.example to .env to customize local settings.

License

ISC

This server cannot be deployed

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Maintenance

ActivityStale
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • mcp-tasks-server

    kanaparthikiran
    A
    license
    Not graded
    quality
    D
    maintenance
    A small Model Context Protocol server that exposes a personal task tracker to any MCP-compatible client. Tasks live in a local SQLite database; no cloud, no surprises.
    MIT

  • ContextForge MCP Lab

    dotdigitize
    A
    license
    Not graded
    quality
    D
    maintenance
    A local MCP-style server for managing task records and seeded documents through controlled tool functions, using SQLite and JSON seed data.
    MIT

  • TaskMCP

    CCLucky-uu
    A
    license
    Not graded
    quality
    D
    maintenance
    A personal task management MCP server that allows LLM clients to create, read, update, and delete tasks with projects, labels, and comments, using a local SQLite database that can also be accessed via a web UI.
    MIT