0bridge

dev.0bridgePublished by 0bridge.devOfficial publisherv0.2.8Updated Oct 24, 2026

Every service you connect, one MCP endpoint for all your AI tools. Sign in once.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

0bridge is a remote MCP endpoint that gives AI tools one shared connection point for every service you connect, with a single sign-in.

What you can do
Connect services to a single MCP endpoint shared across your AI tools, so assistants reach those connected services through one address rather than separate integrations. Sign in once to authorize access. The listing does not name the individual services or tools exposed, so the exact actions available depend on what you connect.
When to use it
Consider it when you use several AI tools and want them to reach your connected services through one endpoint instead of configuring each integration separately.
Requirements
A remote MCP connection to the provider's endpoint over streamable HTTP, plus OAuth sign-in. No packages, environment variables or headers are declared.
Before you install
Access is granted through OAuth sign-in, so review which services you authorize and what data they expose to the endpoint. The listing does not detail the tools or the data handling, so confirm scope and privacy terms before connecting sensitive services.

Installation

In SourceWeft

  1. Open 0bridge in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.0bridge%2F0bridge/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "0bridge": {
      "type": "http",
      "url": "https://0bridge.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.2.8LatestSep 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.