Skip to main content

Overview

Connect Bilt MCP Server to Claude Desktop in under 5 minutes. Once configured, Claude can autonomously create, build, and deploy native mobile applications.
Claude Desktop supports MCP natively. No extensions or plugins required.

Platform Support

macOSFull support for macOS 11+
WindowsFull support for Windows 10+
Linux: Claude Desktop is not officially available on Linux

Prerequisites

  1. Claude Desktop installed - Download from claude.ai/download
  2. Bilt API token - Get one at bilt.me/sign-up

macOS Setup

Step 1: Locate Config File

The config file is located at:

Step 2: Edit Configuration

Open Terminal and run:

Step 3: Add Bilt Configuration

Paste this JSON:
Replace YOUR_TOKEN_HERE with your actual Bilt API token.

Step 4: Save and Restart

  1. Press Ctrl+X, then Y, then Enter to save
  2. Quit Claude Desktop completely (Cmd+Q)
  3. Reopen Claude Desktop

Step 5: Verify Connection

In Claude, ask:
You should see:

Windows Setup

Step 1: Locate Config File

The config file is located at:

Step 2: Create/Edit Configuration

  1. Press Win+R to open Run dialog
  2. Type: notepad %APPDATA%\Claude\claude_desktop_config.json
  3. Click OK
If the file doesn’t exist, Notepad will ask to create it - click Yes.

Step 3: Add Bilt Configuration

Paste this JSON:
Replace YOUR_TOKEN_HERE with your actual Bilt API token.

Step 4: Save and Restart

  1. Click File → Save
  2. Close Claude Desktop completely
  3. Reopen Claude Desktop

Step 5: Verify Connection

In Claude, ask:
You should see all 8 Bilt tools listed.

Configuration Options

Multiple Environments

Add separate entries for dev and production:
Then specify which to use:

Adding Other MCP Servers

You can connect multiple MCP servers:

Example Workflows

Create Your First App

Add Features to Existing App


Troubleshooting

Symptom: Claude doesn’t show Bilt toolsSolutions:
  1. Verify config file location is correct
  2. Check JSON syntax with jsonlint.com
  3. Ensure no extra commas or brackets
  4. Restart Claude completely (not just minimize)
  5. Check Claude’s MCP logs:
    • macOS: ~/Library/Logs/Claude/mcp.log
    • Windows: %APPDATA%\Claude\Logs\mcp.log
Symptom: “Invalid or expired API key”Solutions:
  1. Verify token format starts with bilt_live_
  2. Check for extra spaces before/after token
  3. Regenerate token at bilt.me/settings/api-keys
  4. Ensure token hasn’t expired
  5. Test token manually:
Symptom: “Cannot connect to MCP server”Solutions:
  1. Check internet connection
  2. Verify firewall allows HTTPS (port 443)
  3. Try from different network
  4. Check Bilt status at status.bilt.me
  5. Disable VPN temporarily
Symptom: Claude won’t open after adding configSolutions:
  1. Check JSON syntax - common errors:
    • Missing comma between entries
    • Extra comma after last entry
    • Unclosed brackets/braces
  2. Temporarily remove Bilt config
  3. Restart Claude to verify it works
  4. Re-add Bilt config carefully
Symptom: Claude takes long time to respondSolutions:
  1. This is normal for first request (cold start)
  2. Subsequent requests are faster
  3. Check your internet speed
  4. Try during off-peak hours

Advanced Configuration

Environment Variables (macOS only)

You can use environment variables for tokens:
  1. Add to ~/.zshrc or ~/.bash_profile:
  2. Launch Claude from terminal:
This method requires launching Claude from terminal each time

Debug Mode

Enable verbose logging:
Check logs:
  • macOS: tail -f ~/Library/Logs/Claude/mcp.log
  • Windows: Open %APPDATA%\Claude\Logs\mcp.log

Security Best Practices

Never commit tokensDon’t add config file to git repositories
Rotate regularlyGenerate new tokens every 90 days
Use dev tokensSeparate tokens for development and production
Monitor usageCheck API usage in Bilt dashboard

Next Steps

API Reference

Learn about all 7 tools