{
  "markdown": "# Bilt MCP Server\n\nConnect an MCP-compatible AI client to Bilt to create and manage mobile app projects.\n\n## Connection details\n\n| Setting | Value |\n| --- | --- |\n| URL | `https://mcp.bilt.me/mcp` |\n| Transport | Streamable HTTP |\n| Authentication | `Authorization: Bearer <Bilt API token>` |\n\nCreate an API token at [Bilt API keys](https://bilt.me/settings/api-keys). The legacy `/mcp/sse` endpoint is no longer available.\n\n## Client setup\n\n### Claude Desktop\n\nClaude Desktop launches local MCP commands from `claude_desktop_config.json`. Use [`mcp-remote`](https://github.com/punkpeye/mcp-remote) to bridge stdio to Bilt and attach the API-key header:\n\n```json\n{\n  \"mcpServers\": {\n    \"bilt\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"mcp-remote\",\n        \"https://mcp.bilt.me/mcp\",\n        \"--transport\",\n        \"http-only\",\n        \"--body-timeout\",\n        \"0\",\n        \"--header\",\n        \"Authorization:${BILT_AUTH_HEADER}\"\n      ],\n      \"env\": {\n        \"BILT_AUTH_HEADER\": \"Bearer bilt_live_YOUR_TOKEN_HERE\"\n      }\n    }\n  }\n}\n```\n\nKeep `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.\n\nDo 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.\n\n### Cursor\n\nAdd this to `.cursor/mcp.json`:\n\n```json\n{\n  \"mcpServers\": {\n    \"bilt\": {\n      \"url\": \"https://mcp.bilt.me/mcp\",\n      \"headers\": {\n        \"Authorization\": \"Bearer bilt_live_YOUR_TOKEN_HERE\"\n      }\n    }\n  }\n}\n```\n\n### OpenClaw\n\nAdd this to `~/.openclaw/openclaw.json`:\n\n```json\n{\n  \"mcp\": {\n    \"servers\": {\n      \"bilt\": {\n        \"url\": \"https://mcp.bilt.me/mcp\",\n        \"transport\": \"streamable-http\",\n        \"headers\": {\n          \"Authorization\": \"Bearer bilt_live_YOUR_TOKEN_HERE\"\n        }\n      }\n    }\n  }\n}\n```\n\nRestart the OpenClaw gateway after changing the configuration.\n\nFor 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.\n\n## Available tools\n\nBilt exposes seven tools:\n\n| Tool | Purpose |\n| --- | --- |\n| `bilt_list_projects` | List projects owned by the authenticated user |\n| `bilt_get_project` | Get one project by `projectId` |\n| `bilt_create_project` | Create a project from a `name` and optional `description` |\n| `bilt_get_session` | Get session and workflow state for a `projectId` |\n| `bilt_send_message` | Send build instructions or answer paused workflow questions |\n| `bilt_cancel_workflow` | Cancel the active workflow for a `projectId` |\n| `bilt_get_messages` | Get conversation history for a `projectId` |\n\nAll 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`:\n\n```json\n{\n  \"projectId\": \"project-id\",\n  \"workflowId\": \"workflow-id\",\n  \"answers\": \"[{\\\"questionIndex\\\":0,\\\"selectedOptions\\\":[\\\"Option A\\\"]}]\"\n}\n```\n\nThere 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.\n\nQueued workflows count as active. Before sending unrelated work, call `bilt_get_session` and wait until `hasActiveWorkflows` is false.\n\n## Raw HTTP\n\nMCP clients must send `Accept: application/json, text/event-stream`:\n\n```bash\ncurl -N https://mcp.bilt.me/mcp \\\n  -H 'Authorization: Bearer bilt_live_YOUR_TOKEN_HERE' \\\n  -H 'Accept: application/json, text/event-stream' \\\n  -H 'Content-Type: application/json' \\\n  -H 'Mcp-Protocol-Version: 2025-03-26' \\\n  --data '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"initialize\",\"params\":{\"protocolVersion\":\"2025-03-26\",\"capabilities\":{},\"clientInfo\":{\"name\":\"curl\",\"version\":\"1.0.0\"}}}'\n```\n\nUse an MCP client for normal operation; the raw request is only a transport check.\n\n## Migration from legacy SSE\n\nExisting configurations must:\n\n1. Change `https://mcp.bilt.me/mcp/sse` to `https://mcp.bilt.me/mcp`.\n2. Select Streamable HTTP and disable SSE fallback.\n3. Keep the Bearer token in the Authorization header.\n4. Update stale tool calls to the seven-tool camelCase contract above.\n\n## Documentation and support\n\n- [Bilt MCP documentation](https://bilt.me/docs/quickstart-mcp)\n- [Integration examples](examples/)\n- [GitHub issues](https://github.com/buildingapplications/mcp/issues)\n- [support@bilt.me](mailto:support@bilt.me)\n\nThe hosted Bilt MCP server is proprietary. This repository contains documentation, examples, and agent skill metadata under the terms in [LICENSE](LICENSE).\n",
  "bytes": 5012,
  "sha": "81194848ec095cf2f0640018a8ad57e3ac23a340d0cd48395ad7d715053dbf22",
  "repo_slug": "buildingapplications/mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_buildingapplications_mcp_0816f47e/readme"
}