Put AI to work for your business.

BridgeMCP lets the AI apps your team already uses, like Claude and ChatGPT, do everyday jobs in your tools: Slack, Notion, Stripe, Zendesk and more. Connect each tool once, then hand the routine work to agents that run on a schedule or when something happens.

Request early access

Continue with Google or GitHub. We'll email you when BridgeMCP opens.

01 A hundred small jobs 0:00 / 0:49
Read the transcript
A hundred small jobs
Running a startup is a hundred small jobs: customer tickets, team questions, the weekly numbers, launch content.
Your tools
BridgeMCP lets AI do them in the tools your team already uses, like Slack, Notion, Stripe and Zendesk. Connect once, and everyone just signs in.
Ask for the numbers
Ask Claude or ChatGPT how sales are going. It checks your latest Stripe payments and posts a summary to Slack.
Images and video
Need a launch graphic or a promo video? Make it in the same chat.
Bridge Agents
Then hand the routine work to Bridge Agents. They run on a schedule, or the moment something happens, even overnight.
The agent's route
Write the goal in plain words, no code. The agent decides the steps itself, like answering your team's questions in Slack.
Control and the log
You choose what AI can touch. Switch off anything risky, like refunds, and see every action it takes.
BridgeMCP
BridgeMCP. Put AI to work for your business. Head over to bridgemcp.io to get started.

Works from the AI apps you already use

Setup snippets for 9 clients. The others connect to the same remote URL.
  • Claude Code
  • OpenCode
  • Codex
  • Claude.ai
  • Cursor
  • VSCode
  • Claude Desktop
  • Windsurf
  • Gemini CLI
  • ChatGPT
  • GitHub Copilot
  • JetBrains AI Assistant
  • Zed
  • Warp
  • Cline
  • Kilo Code
  • Goose
  • Kiro
  • Amp
  • LM Studio
  • Mistral Vibe
  • Factory Droid
  • Hermes Agent
  • OpenClaw
The gateway

Connect your tools once

Add each tool once, group tools into Virtual MCPs and give every AI app one URL. Each Virtual MCP decides which tools it exposes and how clients sign in.

  • GitHub Repos, issues, PRs
  • Slack Channels, threads
  • Google Workspace Gmail, Calendar, Drive
  • fal.ai FLUX, Kling, Veo
  • OpenAI Media GPT-Image, Sora
  • Your MCP server Any remote server
BridgeMCP
Virtual MCP
research-and-media
/api/v1/mcp/01JZ8Q4T7M…
OAuth API key Tool filters
  • Claude Code claude mcp add
  • Cursor mcp.json
  • OpenCode opencode.json
  • Codex config.toml

One endpoint per Virtual MCP

Every client uses the same remote URL across MCP protocol versions 2024-11-05 through 2026-07-28.

OAuth or API keys

Clients sign in with OAuth, including dynamic client registration, or send a key that only works for that Virtual MCP.

Tool-level control

Switch individual tools on or off, separately for each Virtual MCP. Clients cannot list or call a tool you switch off.

In practice

Ask. Create. Automate.

Ask about your numbers, make graphics and video in the same chat, and hand routine work to agents. Each card links to its part of the film or to the page that covers it.

Virtual MCPs

The right tools for each workflow

Group connectors into a Virtual MCP and switch individual tools on or off. A research endpoint can search mail and the web while the tools that send or delete stay off.

Explore the gateway
Media generation

Images and video from your client

Built-in OpenAI Media, Google Media, fal.ai and Higgsfield connectors add generate_image and generate_video tools to any Virtual MCP. The image above came from one such call.

  • GPT-Image
  • Sora
  • Nano Banana
  • Veo
  • FLUX
  • Kling
Agents

Automate on the same tools

Package an agent as an AGENTS.md file plus skills. Run it as an async job, on a cron schedule, or from verified webhooks sent by Stripe, GitHub, Slack, 15 other providers or your own systems.

Explore agents
Custom tools

Your APIs, as agent tools

Point a custom HTTP tool at your endpoint. BridgeMCP POSTs each call as JSON, signs it in X-Bridge-Signature when you set a secret, and returns your response to the agent as the tool result.

Explore agents
Observability

See every tool call

The activity log records the tool, Virtual MCP, connector, latency and status of every call to a connector, whether it came from a client or an agent job. The dashboard charts 30 days of volume and connector mix.

Quickstart

Set up in three steps

  1. 01

    Connect your tools

    Add built-in connectors such as Slack, Google Workspace and fal.ai, third-party templates such as GitHub, or any remote MCP server.

  2. 02

    Build a Virtual MCP

    Pick connectors, switch off the tools a workflow should not have, and get one endpoint URL.

  3. 03

    Add it to your client

    Paste the generated snippet. Clients sign in with OAuth, or send an API key for headless use.

terminal
claude mcp add --transport http --scope user research-and-media https://bridgemcp.io/api/v1/mcp/01JZ8Q4T7M2X9C5V3N6B1K0HRD
  1. Run the command to add this remote HTTP server for your user.
  2. Open /mcp in Claude Code and complete OAuth if prompted.

Start with the tools
you already use.

BridgeMCP is in early access. Continue with Google or GitHub to join, and we'll email you when the platform opens.

Request early access Read the docs
Request early access