The value is the loop rather than any single call: get_next_task decides what to do, start_task and update_progress make that visible on the dashboard while it happens, and create_discussion gives the agent a way out when a requirement is unclear. The plan itself lives on Buildable, so this earns its place only if that is already where your roadmap is.
An MCP client for Buildable, a hosted build-planning platform. It gives an assistant the project's plan and task list, and a way to write progress back to the same dashboard a human is watching.
- get_project_context — the whole project in one call: plan, tasks and recent activity
- get_next_task — the task to work on next, chosen by priority and dependencies
- start_task to claim a task, with an optional approach note and a time estimate
- update_progress for a percentage and a status line partway through
- complete_task to close a task out with notes on what was done
- create_discussion to ask a human a question instead of guessing
- health_check to confirm the connection before a long run
A Buildable account with a project, and an API key generated from that project's settings. The server also needs to know which project it is working on and which assistant is calling; both are supplied through your client config. Runs on Node.
One command plus a key — npx @bldbl/mcp, then supply credentials