Buildable MCP Server

Official MCP server for Buildable AI-powered development platform. Enables AI assistants to manage tasks, track progress, get project context, and

Local serverstdioTypeScript

What is the Buildable MCP server?

Buildable mcp server connects Buildable to AI assistants that speak the Model Context Protocol. 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.

What Buildable does

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.

Tools it exposes

Once connected, the assistant can call these 3 tools directly:

  • BuildPlannerMCPClient — The main client class for interacting with Buildable projects
  • Constructor — The Constructor tool exposed by this server
  • Methods — The Methods tool exposed by this server

Installing the buildable mcp server

The server is distributed via npm as @smithery/cli, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 4 environment variables: BUILDABLE_API_KEY, BUILDABLE_PROJECT_ID, BUILDABLE_AI_ASSISTANT_ID, BUILDABLE_API_URL. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Buildable sits in that group, and the shape of its toolset — BuildPlannerMCPClient, Constructor, Methods — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • Written in TypeScript.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the buildable mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
BuildPlannerMCPClientThe main client class for interacting with Buildable projects.
ConstructorThe Constructor tool exposed by this server.
MethodsThe Methods tool exposed by this server.

How to install the Buildable MCP server

{
  "mcpServers": {
    "bldbl": {
      "command": "npx",
      "args": ["-y", "@smithery/cli"],
      "env": {
        "BUILDABLE_API_KEY": "your-value",
        "BUILDABLE_PROJECT_ID": "your-value",
        "BUILDABLE_AI_ASSISTANT_ID": "your-value",
        "BUILDABLE_API_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
BUILDABLE_API_KEYCredential the server authenticates with.Yes
BUILDABLE_PROJECT_IDConfiguration value read at startup.Optional
BUILDABLE_AI_ASSISTANT_IDConfiguration value read at startup.Optional
BUILDABLE_API_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Buildable to BuildPlannerMCPClient.
  • Use Buildable to Constructor.
  • Use Buildable to Methods.

Frequently asked questions

It connects Buildable to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (BuildPlannerMCPClient, Constructor, Methods) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Buildable directly.