Skip to main content
Glama
Sign In
project-manager

project-manager

by charlesribeiro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Day 1 — Claude Code Mastery & Context Engineering Lab

This repository implements a custom Model Context Protocol (MCP) server for project task management and integrates it with Claude Code.

What This Project Demonstrates

  • A custom MCP server built in TypeScript

  • SQLite persistence

  • Three MCP tools:

    • create_task

    • list_tasks

    • update_task

  • Claude Code integration through .mcp.json

  • A structured CLAUDE.md

  • Project-scoped Claude Code permissions

  • Two custom Claude commands

  • A PostToolUse hook that typechecks TypeScript changes

  • An end-to-end Claude Code -> MCP -> SQLite workflow

Related MCP server: Mini Task MCP Server

Architecture

Claude Code
    |
    | stdio / MCP
    v
src/index.ts
    |
    v
src/server.ts
    |
    v
src/db.ts
    |
    v
SQLite (tasks.db)

Project Structure

.
├── .claude/
│   ├── commands/
│   │   ├── task-summary.md
│   │   └── verify-project.md
│   ├── hooks/
│   │   └── typecheck-on-ts-edit.sh
│   └── settings.json
├── .mcp.json
├── CLAUDE.md
├── README.md
├── src/
│   ├── db.ts
│   ├── index.ts
│   └── server.ts
├── package.json
└── tsconfig.json

MCP Tools

create_task

Creates a task.

Inputs:

  • title: string, required

  • description: string, optional

  • priority: low | medium | high | critical

list_tasks

Lists tasks with optional filters.

Inputs:

  • status: todo | in_progress | done

  • priority: low | medium | high | critical

update_task

Updates the status of an existing task.

Inputs:

  • id: positive integer

  • status: todo | in_progress | done

SQLite Schema

Tasks contain:

  • id

  • title

  • description

  • priority

  • status

  • created_at

  • updated_at

The database file is tasks.db and is intentionally ignored by Git.

Setup

Install dependencies:

npm install

Typecheck:

npm run typecheck

Build:

npm run build

Start the MCP server directly:

npm run dev

The process will wait for MCP messages over stdio.

Claude Code Integration

The project registers the MCP server in .mcp.json.

Verify it with:

claude mcp list

Then start Claude Code from the repository root:

claude

Claude Code should discover the project-manager MCP server.

End-to-End Workflow

Example prompts used to verify the MCP integration:

Create a task called "Set up CI/CD pipeline" with high priority

List all tasks

Update task 2 to in_progress

Show me all high priority tasks that are still todo

These prompts exercise the full flow:

Claude Code
-> project-manager MCP
-> MCP tool handler
-> SQLite
-> MCP result
-> Claude Code

Context Engineering

CLAUDE.md

CLAUDE.md documents:

  • project purpose

  • architecture

  • development commands

  • MCP tool contracts

  • database safety

  • code-change workflow

  • completion criteria

It is intentionally concise and structured rather than a large unorganized prompt.

Custom Commands

Two project commands are included.

/task-summary

Uses the MCP tools to summarize the current task database.

/verify-project

Checks:

  • TypeScript typechecking

  • project build

  • MCP configuration

  • exact MCP tool contract

  • Git ignore rules

PostToolUse Hook

.claude/hooks/typecheck-on-ts-edit.sh

The hook runs after Claude edits or writes TypeScript files under src/.

It automatically executes:

npm run typecheck

A successful typecheck exits normally. A failure returns the typecheck output to Claude.

Grading Criteria Mapping

Criterion 1 — Custom MCP Server + Workflow

Implemented by:

  • src/server.ts

  • src/db.ts

  • src/index.ts

  • .mcp.json

Verified through an end-to-end create/list/update workflow in Claude Code.

Criterion 2 — Context Engineering Configuration

Implemented by:

  • CLAUDE.md

  • .claude/settings.json

  • .claude/commands/task-summary.md

  • .claude/commands/verify-project.md

  • .claude/hooks/typecheck-on-ts-edit.sh

The configuration was tested directly inside Claude Code.

Verification

Run:

npm run typecheck
npm run build
claude mcp list
git status

Expected result:

  • typecheck passes

  • build passes

  • project-manager is connected

  • Git working tree is clean

Available Tools

3 tools
create_taskA

Create a new project task with a title, optional description, and priority. Use this when the user wants to add work to the project task list.

Inputs: title (required), priority (required), description.

list_tasksA

List project tasks, optionally filtering by status and/or priority. Use this when the user wants to inspect, search, or summarize existing tasks.

Inputs: status, priority.

update_taskA

Update the status of an existing project task by numeric ID. Use this when work begins, completes, or otherwise changes state.

Inputs: id (required), status (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    Deploy Server
    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

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct action on the task domain: creating, listing, and updating status. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a clear verb_noun pattern in snake_case: create_task, list_tasks, update_task. The only minor deviation is the plural 'tasks' for list, but it is a common convention and does not break consistency.

    Tool Count4/5

    Three tools is on the lean side but appropriate for a focused task-management server covering create, read, and status update. It is not so sparse as to feel trivial, and the tightly scoped surface is easy to navigate.

    Completeness3/5

    The server covers the core create/list/update-status workflow, but lacks delete functionality and does not allow updating fields like title, description, or priority after creation. This is a notable gap for full task management, but agents can still complete basic workflows with workarounds.

    Resources

    Related MCP Connectors

    Related MCP Servers