[ MCP SERVER SUMMARY ]
Buildable MCP server summary
Buildable's MCP server helps AI assistants create and manage AI-assisted software projects. Bifrost governs project tools and keeps Buildable credentials off developer laptops.
| Property | Details |
|---|---|
| Company | Buildable |
| Connection type | STDIO |
| Authentication | Buildable API key (as documented) |
| Package or endpoint | bldbl-mcp |
| Capabilities | AI-assisted project workflows, Project management tools, Build orchestration hooks |
| Official documentation | Buildable MCP documentation |
Before you start
- Buildable access
- Follow the bldbl-mcp repository for setup
What you can do with Buildable
- Standardize Buildable MCP access for a product team via Bifrost
- Limit project-mutating tools to senior-engineer virtual keys
- Centralize API keys and rotate them without client churn
[ HOW TO CONNECT ]
Connect Buildable to Bifrost in three steps
Install Bifrost
Start the gateway locally or deploy in your VPC.
npx -y @maximhq/bifrost
Add Buildable in MCP Gateway
Open MCP Gateway in the Bifrost dashboard, click New MCP Server, and choose STDIO. Or register via the API below.
• Verify install command and auth env vars in https://github.com/chunkycodev/bldbl-mcp.
Point clients at Bifrost /mcp
Configure Claude Desktop, Cursor, or Claude Code to use your Bifrost endpoint with a virtual key instead of connecting directly to Buildable.
{
"mcpServers": {
"bifrost": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer vk_your_virtual_key"
}
}
}
}[ EXAMPLE CONFIG ]
Register Buildable via API
Add this MCP client with a POST to /api/mcp/client. See Connecting to MCP Servers for full options.
curl -X POST http://localhost:8080/api/mcp/client \
-H "Content-Type: application/json" \
-d '{
"name": "buildable",
"connection_type": "stdio",
"stdio_config": {
"command": "npx",
"args": [
"-y",
"bldbl-mcp"
],
"env": {
"BUILDABLE_API_KEY": "env.BUILDABLE_API_KEY"
}
},
"tools_to_execute": [
"*"
]
}'[ WHY BIFROST ]
Run Buildable through one governed gateway
Access control
Virtual keys, RBAC, and tool allowlists per team or agent.
Cost governance
Attribute MCP tool spend alongside LLM usage in one view.
Observability
Log every tool call with latency, server, and virtual key metadata.
Credential isolation
Upstream secrets stay in the gateway — not on every laptop.
[ FAQ ]
Common questions
What does the Buildable MCP server do?
Buildable exposes ai-assisted project workflows, project management tools, build orchestration hooks to MCP-compatible AI clients. Bifrost connects to it as an upstream MCP client and exposes approved tools through one governed /mcp endpoint.
How does Buildable authenticate when used with Bifrost?
Buildable uses Buildable API key (as documented). Store credentials in Bifrost's environment or credential configuration so they stay at the gateway instead of being copied into every AI client.
Can Claude Desktop, Cursor, or Claude Code use Buildable through Bifrost?
Yes. After registering Buildable in Bifrost, point any HTTP MCP-compatible client at the Bifrost /mcp endpoint and authenticate with a virtual key. The client sees only the tools allowed for that key.
[ RELATED SERVERS ]
