Skip to main content
Bilt exposes seven MCP tools at https://mcp.bilt.me/mcp over Streamable HTTP. Copyable client configurations and the Bilt Builder agent skill are available in the public Bilt MCP repository.

1. Create an API key

Open Bilt API Keys, generate a key, and copy it. Keys begin with bilt_live_ and are shown once.
Treat the key like a password. Do not commit it or include it in support logs.

2. Configure your client

Install Node.js 18 or newer, then add this to claude_desktop_config.json:
Fully quit and reopen Claude Desktop. See Claude Desktop setup for file locations and the Windows npx.cmd workaround.

3. Verify the tools

Your client should show these tools:
  • bilt_list_projects
  • bilt_get_project
  • bilt_create_project
  • bilt_get_session
  • bilt_send_message
  • bilt_cancel_workflow
  • bilt_get_messages
Start with a read-only check: “Use Bilt to list my projects.”

Migrating an older configuration

The legacy /mcp/sse endpoint has been removed. Change the URL to /mcp and select Streamable HTTP. Claude Desktop users must replace the old nested remote transport object with the mcp-remote stdio configuration above.

Troubleshooting

Confirm the header contains Bearer followed by the complete bilt_live_... key. Regenerate the key if it may have been exposed or revoked.
claude_desktop_config.json accepts a local command entry. It does not accept Bilt’s remote URL in a nested transport object. Use the mcp-remote configuration exactly as shown.
Keep --body-timeout 0 in mcp-remote, or configure a native client’s request timeout for at least 610 seconds. Bilt build requests can take up to ten minutes.