A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Milestone is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Approved freelance milestone definitions and what done means, shared with AI assistants over MCP.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http milestone-mcp https://milestone-continuity2.vercel.app/mcp
# 2 — ask your agent for something these tools do
# list_milestone_sets, open_milestone_set, read_milestone_set and 12 more
Milestone costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http milestone-mcp https://milestone-continuity2.vercel.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List the signed-in freelancer's milestone sets. Use a returned id with read_milestone_set. Do not guess a set.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| offset | integer | no | — |
Open a draft milestone set for one client project. Draft definitions are not an approved commitment until approve_milestones.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| clientName | string | yes | — |
| projectTitle | yes | — | |
| reference | string | yes | — |
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 milestone is complete unless complete is true. Do not say the next payment is released unless paymentReleased is true. Do not invent a deliverable. Do not mark unsaved work done. Proposed changes are not authorization.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| milestoneSetId | string | yes | — |
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_change applies an add_milestone suggestion.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| milestoneSetId | string | yes | — |
| title | string | yes | — |
| definition | string | yes | — |
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_criterion suggestion. This does not mark the milestone complete.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| milestoneSetId | string | yes | — |
| milestoneId | yes | — | |
| statement | string | yes | — |
Save one deliverable that belongs to a milestone. After milestones are approved, an extra deliverable is refused until an accepted add_deliverable suggestion. Do not invent a deliverable that was not saved.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| milestoneSetId | string | yes | — |
| milestoneId | yes | — | |
| title | string | yes | — |
| detail | string | yes | — |
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 suggestion. Unsaved work cannot be marked done.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| milestoneSetId | string | yes | — |
| milestoneId | yes | — | |
| title | string | yes | — |
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 that the next payment is released.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| milestoneSetId | string | yes | — |
| milestoneId | yes | — | |
| criterionId | yes | — |
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 client a milestone is complete when this tool refuses.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| milestoneSetId | string | yes | — |
| milestoneId | yes | — |
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, and the milestone is complete. Do not tell the client the next payment is released when this tool refuses.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| milestoneSetId | string | yes | — |
| milestoneId | yes | — |
Mark one saved work item done. Refuses when the work item was not saved. Do not mark unsaved work done.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| milestoneSetId | string | yes | — |
| milestoneId | yes | — | |
| workItemId | yes | — |
Record what the assistant may tell the client about milestones, what done means, completion, and payment release. After approval, different wording is refused until an accepted revise_client_wording suggestion. The assistant must not go beyond this wording and the facts in read_milestone_set.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| milestoneSetId | string | yes | — |
| wording | string | yes | — |
Approve the draft milestone definitions and acceptance criteria. Pass confirmed true only after the freelancer explicitly approves them. A draft is not a commitment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| milestoneSetId | string | yes | — |
| confirmed | boolean | yes | — |
Record a suggested change. This does not change the milestones. kind add_milestone requires title and definition. kind add_criterion requires milestoneId and statement. kind add_deliverable requires milestoneId, title, and detail. kind add_work_item requires milestoneId and title. kind revise_client_wording requires wording.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| milestoneSetId | string | yes | — |
| kind | string | yes | — |
| summary | string | yes | — |
| milestoneId | no | — | |
| title | string | no | — |
| definition | string | no | — |
| statement | string | no | — |
| detail | string | no | — |
| wording | string | no | — |
Apply one suggested milestone change after the freelancer explicitly approves that change. Pass confirmed true only then. This is the path for an extra deliverable, a new acceptance criterion, or new saved work after approval. Calling it is not a substitute for the freelancer's approval.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| milestoneSetId | string | yes | — |
| changeId | yes | — | |
| confirmed | boolean | yes | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Milestone or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.3.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Milestone can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.