Developer Tools
lucidui.dev
MCP server for Lucid Builder that pairs with the user's browser to run Lucid UI apps, read editor code, and report render status, errors, and diagnostics.
ENDPOINT 1
https://build.lucidui.dev/mcp
MCP server metadata
- Name
- lucid-hosted-bridge
- Version
- 1.0.0
Lucid UI hosted bridge. Call connect_builder and show the user the link to pair their Lucid Builder tab. Then call render with your code; it returns errors and Lucid diagnostics with fixes. Repeat until render reports no problems.
Known tools 4
connect_builderGet the link that pairs this conversation with Lucid Builder (build.lucidui.dev) in the user's browser.
Inferred read-onlyrenderRun a Lucid UI app in the user's paired Lucid Builder tab and get back the result: whether it mounted, runtime errors, console output, and Lucid diagnostics with their fixes.
Inferred read-onlyget_codeRead the code currently in the user's Lucid Builder editor, including any edits they made by hand.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.lucid-hosted-bridge]
url = "https://build.lucidui.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"lucid-hosted-bridge": {
"type": "http",
"url": "https://build.lucidui.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: lucid-hosted-bridge
Remote MCP URL: https://build.lucidui.dev/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"lucid-hosted-bridge": {
"url": "https://build.lucidui.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"lucid-hosted-bridge": {
"type": "http",
"url": "https://build.lucidui.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "lucid-hosted-bridge",
"transport": "streamable-http",
"url": "https://build.lucidui.dev/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.