Bldbl MCP

What Chunkydotdev/bldbl-mcp MCP server does

Chunkydotdev/bldbl-mcp MCP server gives compatible AI assistants access to Buildable projects. Buildable is described as a development platform with project plans, tasks, dependencies, priorities, progress tracking, and human-AI collaboration features. The server lets an assistant read the project context, identify the next recommended task, manage task status, and communicate questions or blockers to people working on the project.

The package is intended for assistants working against an existing Buildable project rather than for general-purpose local task storage. A project-specific API key and project ID determine which Buildable project the assistant can use.

How it works

The server communicates with the Buildable API using configuration supplied through environment variables. Its default API endpoint is https://bldbl.dev/api, while the API URL can also be configured explicitly. API keys use the bp_ format described in the documentation.

An assistant can first call get_project_context to retrieve the project plan, tasks, and recent activity. It can then call get_next_task to obtain a recommendation based on task dependencies and priority. Work can be recorded with start_task, update_progress, and complete_task. When human guidance is needed, create_discussion creates a question or discussion for project collaborators. health_check verifies connectivity with Buildable.

The underlying client is written with TypeScript support and includes configurable request timeouts and retry behavior. The documented defaults are a 30-second timeout, three retry attempts, and a one-second delay between retries.

Setup and configuration

Install the package from npm with npm install @bldbl/mcp, or run it through npx. The documented MCP configuration uses npx -y @bldbl/mcp, which avoids an interactive install prompt when launched by a client.

Create an API key from a Buildable project under Project Settings, AI Assistants, and Generate API Key. Configure at least these values:

• BUILDABLE_API_KEY: the Buildable credential.
• BUILDABLE_PROJECT_ID: the target project.

BUILDABLE_AI_ASSISTANT_ID is recommended so Buildable can identify the assistant in project activity. BUILDABLE_API_URL is optional because the standard endpoint is automatically used when it is omitted.

Claude Desktop and Cursor configuration examples are provided. Cursor also has a documented one-click setup from a project’s Integrations page. Separate MCP entries can be created when an assistant needs to work with multiple Buildable projects.

Tools and capabilities

Chunkydotdev/bldbl-mcp MCP server exposes these documented operations:

• Retrieve full project context.
• Find the next task recommended by priority and dependencies.
• Start a task with an optional approach and time estimate.
• Record detailed task progress.
• Complete a task with completion notes.
• Create discussions for questions or blockers.
• Check Buildable API health.

The package also exposes a client class with cleanup through disconnect().

Limitations and notes

The documentation requires a Buildable API key and a target project ID; access is therefore tied to Buildable project configuration. The material does not describe local project file editing, code execution, repository operations, or integrations with source-control providers. The available operations focus on Buildable context, task lifecycle updates, progress tracking, discussions, and connectivity checks.

The README identifies the package as MIT-licensed and documents Claude Desktop and Cursor, but it does not provide client-specific setup for Windsurf or Cline.