Bilt

io.github.buildingapplicationsPublished by GitHub account buildingapplicationsv1.0.0Updated Oct 24, 2026

AI agents autonomously build and deploy mobile apps through natural language workflows

VerifiedSSEWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Bilt's hosted MCP server lets an AI assistant create and manage mobile app projects and drive their build workflows by natural language.

What you can do
  • List and inspect mobile app projects owned by the authenticated user
  • Create new projects from a name and optional description
  • Read session and workflow state, including whether builds are active or paused
  • Send build instructions or answer paused workflow questions
  • Cancel an active workflow and read a project's conversation history
When to use it
Use it when you want an AI client to scaffold and iterate on mobile apps through Bilt, or to check on and steer existing Bilt build workflows without leaving the chat.
Requirements
A remote Streamable HTTP endpoint at mcp.bilt.me/mcp and a Bilt API token created in the Bilt account, sent as an Authorization Bearer header. Clients without custom header support need the mcp-remote stdio bridge via npx (Node.js). OAuth is not supported.
Before you install
The token is a live credential placed in client configuration files; keep it out of shared configs. The server creates projects, sends build instructions and cancels workflows, so assistant actions change real project state. Some workflow steps require opening a returned project URL to enter secrets or a Supabase connection outside the chat. The hosted server is proprietary.

Installation

In SourceWeft

  1. Open Bilt in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.buildingapplications%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "bilt": {
      "type": "sse",
      "url": "https://mcp.bilt.me/mcp/sse"
    }
  }
}

README

Bilt MCP Server

Connect an MCP-compatible AI client to Bilt to create and manage mobile app projects.

Connection details

SettingValue
URLhttps://mcp.bilt.me/mcp
TransportStreamable HTTP
AuthenticationAuthorization: Bearer <Bilt API token>

Create an API token at Bilt API keys. The legacy /mcp/sse endpoint is no longer available.

Client setup

Claude Desktop

Claude Desktop launches local MCP commands from claude_desktop_config.json. Use mcp-remote to bridge stdio to Bilt and attach the API-key header:

json
{  "mcpServers": {    "bilt": {      "command": "npx",      "args": [        "-y",        "mcp-remote",        "https://mcp.bilt.me/mcp",        "--transport",        "http-only",        "--body-timeout",        "0",        "--header",        "Authorization:${BILT_AUTH_HEADER}"      ],      "env": {        "BILT_AUTH_HEADER": "Bearer bilt_live_YOUR_TOKEN_HERE"      }    }  }}

Keep Authorization:${BILT_AUTH_HEADER} as one argument, without a space after the colon. On Windows, if Claude resolves npx through a broken Program Files path, set command to the absolute npx.cmd path or its 8.3 short-path equivalent.

Do not add Bilt through Claude's custom connector UI unless it supports a static Authorization header. Without that header, it may attempt OAuth, which Bilt does not currently support.

Cursor

Add this to .cursor/mcp.json:

json
{  "mcpServers": {    "bilt": {      "url": "https://mcp.bilt.me/mcp",      "headers": {        "Authorization": "Bearer bilt_live_YOUR_TOKEN_HERE"      }    }  }}

OpenClaw

Add this to ~/.openclaw/openclaw.json:

json
{  "mcp": {    "servers": {      "bilt": {        "url": "https://mcp.bilt.me/mcp",        "transport": "streamable-http",        "headers": {          "Authorization": "Bearer bilt_live_YOUR_TOKEN_HERE"        }      }    }  }}

Restart the OpenClaw gateway after changing the configuration.

For another client, use native Streamable HTTP only if the client supports custom Authorization headers. Otherwise, use the same mcp-remote stdio bridge shown for Claude Desktop. Client configuration field names are not universal.

Available tools

Bilt exposes seven tools:

ToolPurpose
bilt_list_projectsList projects owned by the authenticated user
bilt_get_projectGet one project by projectId
bilt_create_projectCreate a project from a name and optional description
bilt_get_sessionGet session and workflow state for a projectId
bilt_send_messageSend build instructions or answer paused workflow questions
bilt_cancel_workflowCancel the active workflow for a projectId
bilt_get_messagesGet conversation history for a projectId

All public input fields use camelCase. bilt_send_message accepts a projectId and either a message or structured question answers. Question answers are passed as a JSON string and require the paused response's workflowId:

json
{  "projectId": "project-id",  "workflowId": "workflow-id",  "answers": "[{\"questionIndex\":0,\"selectedOptions\":[\"Option A\"]}]"}

There is no separate resume tool. If a workflow pauses for questions, answer them with bilt_send_message. If it pauses for secrets or a Supabase connection, open the returned projectUrl, complete the requested action there, and the workflow will resume automatically.

Queued workflows count as active. Before sending unrelated work, call bilt_get_session and wait until hasActiveWorkflows is false.

Raw HTTP

MCP clients must send Accept: application/json, text/event-stream:

bash
curl -N https://mcp.bilt.me/mcp \  -H 'Authorization: Bearer bilt_live_YOUR_TOKEN_HERE' \  -H 'Accept: application/json, text/event-stream' \  -H 'Content-Type: application/json' \  -H 'Mcp-Protocol-Version: 2025-03-26' \  --data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"curl","version":"1.0.0"}}}'

Use an MCP client for normal operation; the raw request is only a transport check.

Migration from legacy SSE

Existing configurations must:

  1. Change https://mcp.bilt.me/mcp/sse to https://mcp.bilt.me/mcp.
  2. Select Streamable HTTP and disable SSE fallback.
  3. Keep the Bearer token in the Authorization header.
  4. Update stale tool calls to the seven-tool camelCase contract above.

Documentation and support

The hosted Bilt MCP server is proprietary. This repository contains documentation, examples, and agent skill metadata under the terms in LICENSE.

Source: README.md at commit f9c9129

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.