Potencialize seu agente
A URL do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
https://mcp.bilt.me/mcp/sseO botão do Claude acima abre o Claude com o nome e a URL preenchidos. Você ainda precisa confirmar lá.
claude mcp add --transport http io.github.buildingapplications-mcp https://mcp.bilt.me/mcp/sseRun in a terminal.
{ "mcpServers": { "io.github.buildingapplications-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.bilt.me/mcp/sse" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
Connect an MCP-compatible AI client to Bilt to create and manage mobile app projects.
AI agents autonomously build and deploy mobile apps through natural language workflows
| Setting | Value |
|---|
| URL | https://mcp.bilt.me/mcp |
| Transport | Streamable HTTP |
| Authentication | Authorization: Bearer <Bilt API token> |
Create an API token at Bilt API keys. The legacy /mcp/sse endpoint is no longer available.
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:
{
"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.
Add this to .cursor/mcp.json:
{
"mcpServers": {
"bilt": {
"url": "https://mcp.bilt.me/mcp",
"headers": {
"Authorization": "Bearer bilt_live_YOUR_TOKEN_HERE"
}
}
}
}
Add this to ~/.openclaw/openclaw.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.
Bilt exposes seven tools:
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:
{
"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.
MCP clients must send Accept: application/json, text/event-stream:
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.
Existing configurations must:
https://mcp.bilt.me/mcp/sse to https://mcp.bilt.me/mcp.The hosted Bilt MCP server is proprietary. This repository contains documentation, examples, and agent skill metadata under the terms in LICENSE.
AI agents autonomously build and deploy mobile apps through natural language workflows
{ "mcpServers": { "io.github.buildingapplications-mcp": { "url": "https://mcp.bilt.me/mcp/sse", "headers": {} } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração http para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Bilt é acessado por HTTP.
Última verificação: 2026-11-09. AI agents autonomously build and deploy mobile apps through natural language workflows