You ask. Your AI builds. Beepflow runs it.

Connect Claude, Claude Code, Codex, Gemini CLI or any MCP-compatible assistant. Your API keys and secrets stay stored in Beepflow, so your AI can use them without ever seeing them.

Server URL https://beepflow.com/api/mcp

ClaudeClaude CodeCodexGemini CLIAny MCP client

Install

Pick your client. Setup takes a minute and signs in with your existing Beepflow account.

Claude on the web, desktop and mobile

Open Settings → Connectors in Claude.
Find Beepflow in the directory, or choose Add custom connector and paste the server URL.
```
https://beepflow.com/api/mcp
```
Choose Connect and sign in to Beepflow.
In a chat, turn Beepflow on from the tools menu and ask for what you need.

A connector added on claude.ai is also available in Claude Desktop and the Claude mobile apps.

Claude Code

Add the server:

claude mcp add --transport http beepflow https://beepflow.com/api/mcp

Start Claude Code, run /mcp, choose beepflow and sign in.

Add --scope user to use Beepflow in every project instead of only the current one.

Codex

Add the server:

codex mcp add beepflow --url https://beepflow.com/api/mcp

codex mcp list shows whether the server is signed in.

Gemini CLI

Add the server:

gemini mcp add --transport http beepflow https://beepflow.com/api/mcp

Start Gemini CLI, run /mcp auth beepflow and sign in.

Other MCP clients

Add a remote MCP server named beepflow with the server URL. It speaks Streamable HTTP and signs in with OAuth.
```
https://beepflow.com/api/mcp
```

Clients configured through a JSON file usually take an entry like this:

{
  "mcpServers": {
    "beepflow": {
      "url": "https://beepflow.com/api/mcp"
    }
  }
}

Connect, and your client opens the Beepflow sign-in page.

The client registers itself with Beepflow when it first connects, so there is no client id or API key to create.

How to use it

Describe the outcome you want in plain words. Your assistant does the building through the MCP server, and you stay in control of what goes live.

AskSay what you need, such as a report, a sync between two tools or a page for your team.
It buildsIt reads your workspace, picks the operators and connections it needs and wires up the blueprint or page.
It testsIt runs the result on sample data with side effects mocked, and fixes what breaks.
You turn it onReview it in Beepflow and start it. Your assistant asks before anything that deletes data or reaches outside Beepflow.

List the blueprints in my Marketing space and tell me which ones are running.
Build a blueprint that stores every new Shopify order in a warehouse collection.
Why did the last run of Ticket Analysis fail? Read its results and fix the node that broke.
Create a page that charts daily orders from my warehouse collection.
Every morning, email me the Shopify products with fewer than 10 units left.

What it can work with

Everything you can open in Beepflow, your assistant can read and edit on your behalf.

Workflows and agents

Create, edit, test and run blueprints, from scheduled jobs to webhooks and AI agents.

Pages and sites

Write pages, publish them on your domains and work through the notes left on them.

Data

Query warehouse collections, read run results and look up stored documents.

Integrations

Use your connections to Shopify, Google, Slack and the rest, with the credentials you stored.

Workspace

Organise spaces and tabs, and manage members, roles, domains and API keys.

Your own MCP servers

Publish webhook blueprints as the tools of your own MCP server, for your team or your customers.

Access and safety

Your assistant acts as you, with no more access than your own Beepflow account.

Sign-in

Connecting opens the Beepflow sign-in page, where you sign in with Google or with a code sent to your email. The server uses OAuth 2.1 with PKCE.
Every call acts as you and reaches only the spaces, tabs, connections and resources you can access. There are no separate scopes.
Google sign-ins renew automatically. Email sign-ins last 7 days, after which your client asks you to sign in again.
To disconnect, remove Beepflow from your client's MCP or connector settings.

Permissions

Read tools change nothing, so your client can run them without asking.
Write tools create or change workspace data.
Destructive tools delete or overwrite data, or reach outside Beepflow. Clients ask for your approval by default, and some refuse to run until you confirm.

Calling external services

Your assistant can call the endpoints of each integration through your connections, such as the Shopify Admin API or a Kafka cluster, with the credentials you stored in Beepflow.
Each call passes the same access checks as the Beepflow app, and reads, writes and deletions go through separate tools so your client can ask before the last two.
Every integration type documents its endpoints at https://beepflow.com/api/integrations.

Data and privacy

The server reads and writes only what each tool call asks for and never sees your conversations. When a client connects, Beepflow records its name and version with your user id, and it records each tool call with its tool name, outcome and duration, never its arguments or results. Read how the Privacy Policy covers the MCP server.

New to Beepflow?

Create a free workspace, then connect your assistant. Questions? [email protected]

Talk to us Start building