The Bridge
dev.thebridgev1.0.0Updated Oct 2, 2026
Auth, billing, plans, feature flags and roles for your SaaS, set up from your coding agent.
Overview
AI-generated overview
Lets a coding agent set up authentication, billing, plans, feature flags, and roles for a SaaS product.
- What it does
- The Bridge is a remote MCP endpoint that a coding agent connects to in order to configure SaaS account infrastructure. According to its description, it covers authentication, billing, plans, feature flags, and roles. No individual tools are listed in the manifest, so the exact operations available are not documented here.
- When to use it
- Consider it when building or maintaining a SaaS application and you want an assistant to help wire up sign-in, subscription plans, entitlements, and role-based access rather than doing that setup by hand.
- Requirements
- A remote MCP connection to the endpoint at api.thebridge.dev over streamable HTTP. The manifest declares no authentication, environment variables, or headers, and no local package or runtime.
Before you install
The manifest declares no authentication, so anyone who can reach the endpoint may be able to use it; confirm how access is actually controlled before connecting. Because it manages billing, plans, and roles, changes could affect payments and user permissions. No credentials, keys, or write behavior are documented in the supplied material.
Installation
In SourceWeft
- Open The Bridge in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"bridge": {
"type": "http",
"url": "https://api.thebridge.dev/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestOct 2, 2026

