# Lahutchins91 Milestone MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.lahutchins91%2Fmilestone
Registry id: `mcp-registry/io.github.lahutchins91/milestone`
Status: live (checked 2026-11-22T16:13:51.628Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 846
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "lahutchins91-milestone-mcp-server": {
      "type": "http",
      "url": "https://milestone-continuity2.vercel.app/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http lahutchins91-milestone-mcp-server https://milestone-continuity2.vercel.app/mcp
```

## Tools (15)

- `accept_milestone_change`: Apply one suggested milestone change after the freelancer explicitly approves that change. Pass confirmed true only then. This is the path for an extra delivera
- `approve_milestones`: Approve the draft milestone definitions and acceptance criteria. Pass confirmed true only after the freelancer explicitly approves them. A draft is not a commit
- `declare_milestone_complete`: State that a milestone is complete. Refuses unless the milestones are approved and every saved acceptance criterion on that milestone was met. Do not tell the c
- `declare_next_payment_released`: State that the next payment for a milestone is released. Refuses unless the milestones are approved, every saved acceptance criterion on that milestone was met,
- `define_milestone`: Add one milestone to a draft set: a title and the definition of that milestone. After milestones are approved, a new milestone is refused until accept_milestone
- `list_milestone_sets`: List the signed-in freelancer's milestone sets. Use a returned id with read_milestone_set. Do not guess a set.
- `mark_work_done`: Mark one saved work item done. Refuses when the work item was not saved. Do not mark unsaved work done.
- `open_milestone_set`: Open a draft milestone set for one client project. Draft definitions are not an approved commitment until approve_milestones.
- `read_milestone_set`: Read the milestone set before answering. Quote only this record. mayTellClient and clientWording are what the assistant may tell the client. Do not say a milest
- `record_criterion_met`: Record that one saved acceptance criterion was met. The criterion must already be saved. This does not by itself tell the client the milestone is complete or th
- `save_acceptance_criterion`: Save one acceptance criterion, which is what done means for that milestone. After milestones are approved, a new criterion is refused until an accepted add_crit
- `save_deliverable`: Save one deliverable that belongs to a milestone. After milestones are approved, an extra deliverable is refused until an accepted add_deliverable suggestion. D
- `save_work_item`: Save one piece of work under a milestone so it can later be marked done. After milestones are approved, new work is refused until an accepted add_work_item sugg
- `suggest_milestone_change`: Record a suggested change. This does not change the milestones. kind add_milestone requires title and definition. kind add_criterion requires milestoneId and st
- `write_client_wording`: Record what the assistant may tell the client about milestones, what done means, completion, and payment release. After approval, different wording is refused u

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
