Buildable
Official MCP server for Buildable AI-powered development platform. Enables AI assistants to manage tasks, track progress, get project context, and collaborate with humans on software projects.
⚡Config Installation
Add this to your claude_desktop_config.json:
{
"mcpServers": {
"buildable": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-buildable"
]
}
}
}* Note: Requires restart of Claude Desktop app.
Deployment Infrastructure
Adoption Framework for Buildable
Before installing any skill, define a clear objective and measurable outcome. A useful implementation question is: what workflow becomes faster, safer, or more reliable after this skill is active? If that answer is vague, delay rollout and tighten scope first.
For most teams, a low-risk pattern is preview-first rollout with one owner, one test scenario, and one rollback plan. Capture failures in a structured log so quality decisions are evidence-based. This is especially important for skills that touch file systems, external APIs, or automation chains with downstream side effects.
- Define success metrics before installation.
- Validate permission scope against policy boundaries.
- Run one controlled pilot and document failure categories.
- Promote only after acceptance checks pass consistently.
Pre-Deployment Review Questions
Use these questions before enabling the skill in shared environments. They reduce surprise incidents and make approval decisions consistent across teams.
- What data can this skill read, write, or transmit by default?
- Which failures are recoverable automatically and which require manual stop?
- Do we have verifiable logs that prove safe behavior under load?
- Is rollback tested, documented, and assigned to a clear owner?
If any answer is unclear, keep rollout in preview and close the gap before production use.
Editorial Review Snapshot
This listing includes an editorial QA layer in addition to automated rendering. Review status is based on documentation depth, content uniqueness, and operational safety signals from the upstream repository.
- Last scan date: 2026-01-18
- README depth: 1190 words
- Content diversity score: 0.53 (higher is better)
- Template signal count: 0
- Index status: Index eligible
Recommendation: Pilot in a bounded environment first. Confirm observability and ownership before promoting to shared workflows.
Skill Implementation Board
Actionable utility module for rollout decisions. Use the inputs below to choose a deployment path, then execute the checklist and record an output note.
Input: Security Grade
B
Input: Findings
0
Input: README Depth
1190 words
Input: Index State
Eligible
| Decision Trigger | Action | Expected Output |
|---|---|---|
| Input: risk band moderate, docs partial, findings 0 | Run a preview pilot with fixed ownership and observability checkpoints. | Pilot can start with rollback checklist attached. |
| Input: page is index-eligible | Proceed with external documentation and team onboarding draft. | Reusable rollout runbook ready for team adoption. |
| Input: context tags/scenarios are missing | Define two concrete scenarios before broad rollout. | Clear scope definition before further deployment. |
Execution Steps
- Capture objective, owner, and rollback contact.
- Run one preview pilot with fixed test scenario.
- Record warning behavior and recovery evidence.
- Promote only if pilot output matches expected threshold.
Output Template
skill=buildable mode=B pilot_result=pass|fail warning_count=0 next_step=rollout|patch|hold
🛡️ Security Analysis
Clean Scan Report
Our static analysis engine detected no common vulnerabilities (RCE, API Leaks, Unbounded FS).
DocumentationREADME.md
@bldbl/mcp
Official MCP client for Buildable - AI-powered development platform that makes any project buildable
This package enables AI assistants (Claude, GPT, etc.) to work directly with Buildable projects using the Model Context Protocol (MCP). AI assistants can get project context, manage tasks, track progress, and communicate with human developers.
🌟 What is Buildable?
Buildable (bldbl.dev) is an AI-powered development platform that makes any project buildable. It provides:
- AI-Generated Build Plans: Comprehensive project roadmaps with implementation details
- Smart Task Management: Automated task breakdown with dependencies and priorities
- AI Assistant Integration: Direct integration with Claude, GPT, and other AI assistants
- Real-time Collaboration: Seamless human-AI collaboration on complex projects
- Progress Tracking: Live monitoring of development progress and blockers
🚀 Features
- Full Project Integration: Get complete project context, plans, and task details
- Autonomous Task Management: Start, update progress, and complete tasks
- Human Collaboration: Create discussions for questions and blockers
- Real-time Progress Tracking: Live updates and status monitoring
- Type-Safe API: Full TypeScript support with comprehensive type definitions
- Claude Desktop Ready: CLI interface for seamless Claude Desktop integration
📦 Installation
Installing via Smithery
To install @bldbl/mcp for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @buildable/bldbl-mcp --client claude
Manual Installation
npm install @bldbl/mcp
🚀 Quick Start
Step 1: Install the MCP Server
npm install -g @bldbl/mcp
Step 2: Get Your Buildable API Key
- Go to bldbl.dev and create an account
- Create or select a project
- Go to Project Settings → AI Assistants → Generate API Key
Step 3: Configure Your AI Assistant
🤖 For Claude Desktop:
Add this to your Claude Desktop config file (~/.config/claude/claude_desktop_config.json):
{
"mcpServers": {
"buildable": {
"command": "npx",
"args": ["-y", "@bldbl/mcp"],
"env": {
"BUILDABLE_API_KEY": "bp_your_api_key_here",
"BUILDABLE_PROJECT_ID": "your-project-id",
"BUILDABLE_AI_ASSISTANT_ID": "claude-desktop"
}
}
}
}
Minimal setup - only API URL is auto-detected.
✨ For Cursor AI:
Option 1: One-Click Setup (Recommended)
- Go to your project on bldbl.dev
- Navigate to Integrations
- Click "Add to Cursor" - Done! 🎉
Option 2: Manual Configuration Add this to your Cursor AI config file:
{
"mcpServers": {
"buildable": {
"command": "npx",
"args": ["-y", "@bldbl/mcp"],
"env": {
"BUILDABLE_API_KEY": "bp_your_api_key_here",
"BUILDABLE_PROJECT_ID": "your-project-id",
"BUILDABLE_AI_ASSISTANT_ID": "cursor-ide"
}
}
}
}
Minimal setup - only API URL is auto-detected.
Step 4: Start AI-Powered Development!
Once configured, your AI assistant has access to these powerful tools:
- 🏗️
get_project_context- Understand your entire project structure - 📋
get_next_task- Find what to work on next based on priorities - ▶️
start_task- Begin working on a specific task - 📊
update_progress- Report detailed progress updates - ✅
complete_task- Mark tasks finished with comprehensive notes - 💬
create_discussion- Ask questions when you need human input - 🔍
health_check- Verify connection to Buildable
💡 Example AI Conversation:
You: "What should I work on next in my project?"
AI: *calls get_project_context & get_next_task*
"I see you're building a React dashboard app. The next
high-priority task is 'Implement user authentication'.
Should I start working on it?"
You: "Yes, go ahead!"
AI: *calls start_task*
"Perfect! I'm starting the authentication task. I'll use
NextAuth.js with GitHub OAuth. Let me break this down:
1. Install dependencies
2. Set up NextAuth config
3. Create login/logout components
4. Add protected routes
I'll update you on progress as I work!"
[AI works and calls update_progress periodically]
AI: *calls update_progress*
"Progress update: 75% complete! I've implemented:
✅ NextAuth.js configuration
✅ GitHub OAuth provider setup
✅ Login/logout components
🔄 Currently working on: Protected route middleware
Should I continue with the remaining work?"
🔧 Advanced Configuration
Environment Variables
3 environment variables are recommended for proper AI assistant tracking:
export BUILDABLE_API_KEY="bp_your_api_key_here" # Your API key (required)
export BUILDABLE_PROJECT_ID="your-project-id" # Target project (required)
export BUILDABLE_AI_ASSISTANT_ID="my-ai-assistant" # AI Assistant ID (recommended)
# Optional (has smart default):
# export BUILDABLE_API_URL="https://bldbl.dev/api" # API endpoint (default)
Why AI Assistant ID matters: This helps you track which AI assistant is doing what work in your project dashboard.
CLI Usage
You can also run the MCP server directly:
# Install globally and use bldbl command
npm install -g @bldbl/mcp
bldbl
# Or run with npx (no installation needed)
npx @bldbl/mcp
Multiple Projects
To work with multiple Buildable projects, create different MCP server configs:
{
"mcpServers": {
"buildable-frontend": {
"command": "npx",
"args": ["-y", "@bldbl/mcp"],
"env": {
"BUILDABLE_API_KEY": "bp_frontend_key_here",
"BUILDABLE_PROJECT_ID": "frontend-project-id",
"BUILDABLE_AI_ASSISTANT_ID": "claude-frontend"
}
},
"buildable-backend": {
"command": "npx",
"args": ["-y", "@bldbl/mcp"],
"env": {
"BUILDABLE_API_KEY": "bp_backend_key_here",
"BUILDABLE_PROJECT_ID": "backend-project-id",
"BUILDABLE_AI_ASSISTANT_ID": "claude-backend"
}
}
}
}
🛠️ API Reference
BuildPlannerMCPClient
The main client class for interacting with Buildable projects.
Constructor
new BuildPlannerMCPClient(config: BuildPlannerConfig, options?: ClientOptions)
Config Parameters:
apiUrl: Buildable API URL (defaults to 'https://bldbl.dev/api')apiKey: Your Buildable API key (starts with 'bp_')projectId: Target project IDaiAssistantId: Unique identifier for your AI assistanttimeout: Request timeout in milliseconds (default: 30000)
Options:
retryAttempts: Number of retry attempts (default: 3)retryDelay: Delay between retries in ms (default: 1000)
Methods
getProjectContext(): Promise<ProjectContext>
Get complete project context including plan, tasks, and recent activity.
getNextTask(): Promise<NextTaskResponse>
Get the next recommended task to work on based on dependencies and priority.
startTask(taskId: string, options?: StartTaskOptions): Promise<StartTaskResponse>
Start working on a specific task with optional approach and timing estimates.
updateProgress(taskId: string, progress: ProgressUpdate): Promise<ProgressResponse>
Update progress on the current task with detailed status information.
completeTask(taskId: string, completion: CompleteTaskRequest): Promise<CompleteTaskResponse>
Mark a task as completed with detailed completion information.
createDiscussion(discussion: CreateDiscussionRequest): Promise<DiscussionResponse>
Create a discussion/question for human input when you need guidance.
healthCheck(): Promise<{status: string, timestamp: string}>
Check connectivity and health of the Buildable API.
disconnect(): Promise<void>
Properly disconnect and cleanup the client connection.
🔐 Authentication
- Generate API Key: Go to your Buildable project → AI Assistant tab → Generate API Key
- Secure Storage: Store your API key securely (environment variables recommended)
- Key Format: API keys start with
bp_followed by project and random identifiers
🐛 Error Handling
The client includes comprehensive error handling:
try {
const context = await client.getProjectContext();
} catch (error) {
if (error.code === 'UNAUTHORIZED') {
console.error('Invalid or expired API key');
} else if (error.code === 'PROJECT_NOT_FOUND') {
console.error('Project not found or access denied');
} else {
console.error('API error:', error.message);
}
}
🔄 Development Workflow
Typical AI assistant workflow with Buildable:
- Initialize - Connect to Buildable with API key
- Get Context - Understand the project structure and current state
- Find Work - Get the next priority task
- Start Task - Begin working with approach and estimates
- Progress Updates - Regular progress reports with details
- Ask Questions - Create discussions for blockers or decisions
- Complete Task - Finish with comprehensive completion notes
- Repeat - Continue with next tasks
📊 Usage Statistics
// Get usage statistics for your AI assis
...(truncated)