Skip to main content
Cursor supports remote Streamable HTTP servers and custom headers directly.

​
Configure Bilt

Create or edit one of these files:
  • Personal, all projects: ~/.cursor/mcp.json
  • Project-specific: .cursor/mcp.json
Use the personal file when it contains your API key. Do not commit a literal key in a project file.
Reload Cursor, then open Settings → Tools & Integrations → MCP. Bilt should be enabled and list seven tools.

​
Verify

In Agent chat, ask: “Use Bilt to list my projects.” Cursor asks for approval before tool calls unless your approval settings say otherwise.

​
Troubleshooting

Confirm the filename is mcp.json, not mcp_config.json, and that bilt is nested directly under mcpServers. Reload the Cursor window after saving.
Confirm the header value contains Bearer followed by the full key. Personal keys should start with bilt_live_.
Update Cursor. As a temporary fallback, use the mcp-remote stdio configuration from the Claude Desktop guide; Cursor accepts the same command, args, and env shape.

​
Migrating from legacy SSE

Replace /mcp/sse with /mcp and simplify the server entry to the top-level url and headers fields shown above. Do not retain a nested transport object.