MCP Project Manager

A custom MCP server exposing project-management tools (create_task, list_tasks, update_task) backed by SQLite. Built as the Day 1 lab for the Chiron AI Engineering onboarding program.

Tools

Related MCP server: Mini Task MCP Server

Project Layout

• server.py — MCP server definition (tools, handlers) with stdio transport, for local use with Claude Code

• server_sse.py — SSE transport wrapper around the same server, for remote/cloud deployment

• db.py — async SQLite persistence layer

Local Development

uv sync
uv run python server.py          # stdio transport (for Claude Code)
uv run python server_sse.py      # SSE transport on :8000 (for testing deployment locally)

Use with Claude Code

A .mcp.json is included pointing at the local stdio server. Restart Claude Code after cloning, then ask it to create/list/update tasks — it will call the MCP tools directly.

Deployment (Railway / Render)

The repo includes a Procfile (web: uv run python server_sse.py) that both platforms understand.

1. Connect this GitHub repo in the Railway or Render dashboard.

2. Set the DB_PATH environment variable (e.g. /data/tasks.db if using a persistent volume).

3. Deploy. The server listens on $PORT (defaults to 8000) and exposes GET /sse + POST /messages/.

4. Point .mcp.json at the deployed URL:

{
  "mcpServers": {
    "project-manager": {
      "type": "sse",
      "url": "https://<your-app>.up.railway.app/sse"
    }
  }
}

Database

SQLite file at $DB_PATH (default tasks.db, gitignored). Schema:

CREATE TABLE tasks (
    id          INTEGER PRIMARY KEY AUTOINCREMENT,
    title       TEXT NOT NULL,
    description TEXT DEFAULT '',
    priority    TEXT NOT NULL CHECK(priority IN ('low','medium','high','critical')),
    status      TEXT NOT NULL DEFAULT 'todo' CHECK(status IN ('todo','in_progress','done')),
    created_at  TEXT NOT NULL,
    updated_at  TEXT NOT NULL
);