Any app

Connect any MCP server to your AI

Paste the address of any remote MCP server, your own or a vendor’s, and its tools join your other apps at the one Flowplane address your assistants already use. You look at every tool before it is used and decide what each kind may do; Flowplane keeps watch when the server adds or changes tools, and every call is in the log. A server in your own network is reached through a Flowplane tunnel.

Tools
Whatever your server lists
Sign-in
Own account or shared key
Approval, by default
Changes wait for you
MCP server
Yours, behind Flowplane
What it can do

What your assistant can do in your MCP server

The tools are the ones your server lists, and you tick the ones you want when you add it. By default reads are allowed, changes wait for the person’s approval and deletes are blocked; your workspace’s rules decide.

Reads allowed

Looking things up runs straight away, within what the account you connected may see.

Changes asks first

Creating, changing or deleting waits for your approval in the browser, unless your workspace’s rules say otherwise.

How it connects

Sign-in

Flowplane finds out how the server signs in: no sign-in at all, a pasted access token, or OAuth on the server’s own sign-in page, where Flowplane registers itself when the server allows it. The workspace signs in once for everyone, or each person signs in with their own account so the assistant acts as them and sees only the tools their account has. Flowplane keeps the login sealed; the assistant never sees it.

In Flowplane: In the Flowplane console, add a custom app (MCP), paste the server’s https address and sign in if it asks. Then tick the tools you want and add it.

MCP

Any MCP server and MCP

This entry is for MCP servers themselves: you bring the server, Flowplane puts it behind the same address, sign-in, rules and log as your other apps. Nothing is installed on your assistants, and the server only ever sees its own login, never your assistants’ keys.

Try it

Things to ask

  • “List the open tickets in our internal helpdesk server.”
  • “Use our pricing server to quote 40 licences for Acme.”
  • “Search our product documentation server for how to reset a device.”
  • “Create a deployment ticket for release 2.4 in our ops tool.”
Your assistant

Connect your assistant to your MCP server

One Flowplane address works in every assistant below, with the same rules and the same log. Step-by-step setup for each:

FAQ

Questions

What may the assistant do with the server’s tools by default?
Each tool is a read, a change or a delete, taken from the server’s own hints, and a tool without hints counts as a delete. By default reads are allowed, changes wait for approval and deletes are blocked. An admin can change the rule for each kind, and set an exception for one tool.
What happens when the server adds or changes a tool?
A new tool stays off until someone reviews it, unless the setting to use tools the server adds later is on: then it follows its kind’s rule. A tool whose name, description, inputs or hints change is suspended at once until someone looks at the difference and approves it again.
Does it work with a local MCP server?
It takes a remote server at an https address. One that runs in your own network is reached through a Flowplane tunnel; one that only runs on a laptop is not reachable.
Which AI assistants can use your MCP server through Flowplane?
Claude, Claude Code, ChatGPT, Cursor, Codex, GitHub Copilot and Mistral Le Chat, and any other client that supports remote MCP servers with sign-in. They all reach your MCP server through the same Flowplane address.
What does it cost?
Free for one person, with up to three apps and five assistants. Personal Pro is €9 a month including VAT; companies start at €99 a month for ten active users. Prices are indicative; see the pricing page.

Pricing

Let your AI work with your data. Safely, from today.

Free for yourself, set up in a minute. For your team or company, we’re happy to help you get started.