MCP Marketplace

Give your agents more tools. Cloud servers connect over https; credentials stay in your environment and are never written to the project config.

SupabaseCloud

Manage Postgres, migrations, edge functions and logs for a Supabase project.

Supabase · databasebuilde mcp install supabase

GitHubCloud

Repositories, issues, pull requests and Actions runs.

GitHub · codebuilde mcp install github

Context7Cloud

Up-to-date library documentation and code examples for the agent.

Upstash · docsbuilde mcp install context7

FirebaseLocal

Firebase projects, Firestore, Auth, hosting and security rules via the Firebase CLI.

Google · cloudbuilde mcp install firebase

PlaywrightLocal

Drive a real browser to test and inspect the app you are building.

Microsoft · browserbuilde mcp install playwright

Connect a cloud MCP server

Point Builde at any https MCP endpoint. The bearer token is read from the environment variable you name, at connect time.

builde mcp add my-server --url https://mcp.example.com/mcp --token-env MY_SERVER_TOKEN

Over HTTP: POST /api/mcp/servers to add, POST /api/mcp/connect to test the connection and list its tools. Both need BUILDE_ADMIN_TOKEN.

Build an MCP server

Generates a TypeScript project with your tools wired to the MCP SDK. Add --http for a bearer-protected cloud endpoint.

builde mcp new server weather --http

Build an MCP client

Generates a small client that connects to your servers, lists their tools and calls them from the terminal.

builde mcp new client my-client --url https://mcp.example.com/mcp

Describe tools once, generate everything

The builder endpoint takes a full spec — every tool and parameter — and returns the project files, or writes them under mcp-servers/ without overwriting anything.

POST /api/mcp/build { "kind": "server", "spec": { … }, "write": true }