Finish Grid is answering right now. Last checked moments ago. It exposes 3 tools.
A finishing tool, not a to-do list: file tasks, read today's plan, and work dispatched queues.
Today is the operative word: we check Finish Grid every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.
claude mcp add finish-grid --transport http https://thefinishgrid.com/mcp
{
"mcpServers": {
"finish-grid": {
"url": "https://thefinishgrid.com/mcp"
}
}
}
[mcp_servers.finish-grid]
url = "https://thefinishgrid.com/mcp"
{
"mcpServers": {
"finish-grid": {
"url": "https://thefinishgrid.com/mcp"
}
}
}
{
"mcpServers": {
"finish-grid": {
"url": "https://thefinishgrid.com/mcp"
}
}
}
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
about_finish_grid
how_to_connect
get_pricing
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://thefinishgrid.com/mcp | streamable-http | answering | 531 ms | 0 min ago |
Voice-first planning — notes, tasks, events and AI reports. 21 tools. iOS + Apple Watch.
Read-only search, todo listing, and daily note access for a WhyNote account
Read-only access to Australian NEM grid-scale battery performance, revenue, dispatch and FCAS data.
The deciding place: argue the call, decide, keep the reasons, get the work back as finished files.
Read and structure notes, projects, tasks, and pages in the xTiles visual workspace.
Split a task into plans with disjoint file boundaries; scaffold a git worktree per plan.
Ask batchwatch whether to batch a job and get the real measured queue evidence, not a guess.
Diagnoses pg-boss and graphile-worker job queues: retry storms, stuck workers, missed schedules.
Answers built from our own checks of this server.