Flow.Documentation
AdvancedAI Colleagues build what is on the BoardThe Board

Building from Claude Desktop and Claude Code (MCP)

6 steps± 4 minVideoVerified 22 Oct 2026
  1. Step 1 · Open your development environment
  2. Step 2 · Open MCP access
  3. Step 3 · Create a key with limited rights
  4. Step 4 · Store the key — you see it once
  5. Step 5 · What the app may and may not do
  6. Step 6 · Revoke the access

With MCP access you let an AI app build in your development environment: modules, tables, workflows, agents. The app acts as you and can never do more than your role, it cannot delete, and keys and security policies remain in human hands. You create a key with limited rights, see what the app may and may not do, and revoke the access again.

Watch the whole guide as a video6 steps in one film
Step 1 / 6

Open your development environment

An AI app only builds in Development (or Test). In Acceptance and Production it can at most read: what is there only arrives by publishing.

  1. Click Development
Open your development environment · Click Development
  1. Click Open ↗
Open your development environment · Click Open ↗
Step 2 / 6

Open MCP access

At the bottom of the explorer, under Workspace-wide, is MCP access (AI apps). At the top you find the MCP server's address and, per app, how to connect it. In Claude Desktop you add that address as a custom connector: Claude opens Flow, you sign in and choose what it may do.

  1. Click MCP access (AI apps)
Open MCP access · Click MCP access (AI apps)
Open MCP access · The MCP server's address, with the steps for Claude Desktop and Claude Code.
Step 3 / 6

Create a key with limited rights

For Claude Code you create a key. Give it a name that says where it lives, and only the rights it needs: Read and Build, but not Run. A key always expires; choose as short as is workable.

  1. Click ＋ New key
Create a key with limited rights · Click ＋ New key
  1. In Name, type Claude Code on Bram's laptop
Create a key with limited rights · In Name, type Claude Code on Bram's laptop
  1. Click Run and test Run workflows and try agents.
Create a key with limited rights · Click Run and test Run workflows and try agents.
  1. In Valid 1 day 7 days 14 days 30 days, choose 7 days
Create a key with limited rights · In Valid 1 day 7 days 14 days 30 days, choose 7 days
  1. Click Create key
Create a key with limited rights · Click Create key
Step 4 / 6

Store the key — you see it once

Flow shows the key now, and never again: it keeps only a fingerprint. Put it in an environment variable (FLOW_MCP_KEY), not in a chat or a file.

Store the key — you see it once · The warning that this is the only time (the key itself is covered up).
  1. Click Done
Store the key — you see it once · Click Done
Step 5 / 6

What the app may and may not do

The app only gets tools that match the key's rights. With Read and Build it creates modules, tables, knowledge bases, workflows, APIs, agents and widgets, and publishes through the same test as on screen. Run is not part of it now: if the app asks anyway, it gets no right. Every call counts and every change is in the audit log as via MCP.

What the app may and may not do · The key with Read, Build and the number of calls the app has made so far.
Step 6 / 6

Revoke the access

Done building, or lost the laptop? Revoking works at once: the app's next call is refused.

  1. Click Revoke
Revoke the access · Click Revoke
  1. Click Revoke
Revoke the access · Click Revoke
Revoke the access · The key shows as revoked.

This guide was carried out step by step on 22 Oct 2026 by an automated test on Flow (version 3e563176).