FlowLibs MCP Server

Connect Claude — or any client that speaks the Model Context Protocol — to the FlowLibs cloud-flow catalog. Once connected, you can ask your assistant to discover Power Automate templates, pull their setup steps, map connectors to your stack, and customize a ready-to-import solution — all in conversation. The server speaks Streamable HTTP at https://www.flowlibs.com/api/mcp and requires a FlowLibs Pro or Team plan — generate a personal access token and add it to your client. Every tool checks your entitlement live on each call.

Get an access token

Authentication uses a personal access token. On a Pro or Team plan, open your profile → MCP access tokens, generate a token (set a name and expiry), and copy it — it's shown once. Every client below uses that token in an Authorization: Bearer header. You can revoke it anytime from the same place.

Set up your client

Generate a token first (above), then follow your client. Replace flowlibs_pat_xxxxxxxx with your real token, and keep exactly one space after Bearer.

Claude Code

Adds the server over HTTP with the token as a header — one command.

Run the command below (paste your token after Bearer ).
Confirm with /mcp inside Claude Code — the flowlibs tools should be listed.

bash

claude mcp add --transport http flowlibs \
  https://www.flowlibs.com/api/mcp \
  --header "Authorization: Bearer flowlibs_pat_xxxxxxxx"

Claude Desktop

Desktop's “Add custom connector” only supports OAuth, not a static header, so bridge with mcp-remote.

Open Settings → Developer → Edit Config to open claude_desktop_config.json.
Add the flowlibs entry below, putting your token in the FLOWLIBS_AUTH env value.
Save and fully restart Claude Desktop.

json

{
  "mcpServers": {
    "flowlibs": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://www.flowlibs.com/api/mcp",
        "--header", "Authorization:${FLOWLIBS_AUTH}"
      ],
      "env": { "FLOWLIBS_AUTH": "Bearer flowlibs_pat_xxxxxxxx" }
    }
  }
}

The header is passed via an env var (Authorization:${FLOWLIBS_AUTH}) because mcp-remote splits --header on the first space — a literal "Authorization: Bearer …" argument can be mangled.

OpenAI Codex

In the desktop app, add the server by URL and set the token as a header.

Settings → MCP servers → add a server with URL https://www.flowlibs.com/api/mcp.
Under Headers, add key Authorization with value Bearer flowlibs_pat_…, then Save.
Fully quit and relaunch Codex (from the tray / Task Manager, not just the window).

bash

# Set the token in your environment first, then:
codex mcp add flowlibs --url https://www.flowlibs.com/api/mcp \
  --bearer-token-env-var FLOWLIBS_PAT

Use the Headers field, not the “Bearer token env var”field — if Codex can't resolve that env var it silently drops the whole server. The CLI equivalent is shown above (the env var must be set in Codex's environment).

Cursor

Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project).

Add the flowlibs entry below with your token.
Open Settings → MCP and confirm flowlibs is enabled; refresh if needed.

json

{
  "mcpServers": {
    "flowlibs": {
      "url": "https://www.flowlibs.com/api/mcp",
      "headers": { "Authorization": "Bearer flowlibs_pat_xxxxxxxx" }
    }
  }
}

Keep the token out of the file with "Authorization": "Bearer ${env:FLOWLIBS_PAT}" and set FLOWLIBS_PAT in your environment.

VS Code (GitHub Copilot)

Create .vscode/mcp.json in your workspace — note the servers key and type: "http".

Add the config below with your token.
Open Copilot Chat in Agent mode → Tools, and start the flowlibs server.

json

{
  "servers": {
    "flowlibs": {
      "type": "http",
      "url": "https://www.flowlibs.com/api/mcp",
      "headers": { "Authorization": "Bearer flowlibs_pat_xxxxxxxx" }
    }
  }
}

For a secret prompt instead of a hardcoded token, define an inputs entry and reference it in the header.

Cline

Open the Cline panel → MCP Servers → Remote Servers (or “Configure MCP Servers” for JSON).

Add the flowlibs entry below to cline_mcp_settings.json with your token.
The tools appear once the server connects.

json

{
  "mcpServers": {
    "flowlibs": {
      "url": "https://www.flowlibs.com/api/mcp",
      "headers": { "Authorization": "Bearer flowlibs_pat_xxxxxxxx" },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Some Cline versions had a bug that dropped the Authorization header — update to the latest if tools return “authentication required”.

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json — note the field is serverUrl, not url.

Add the flowlibs entry below with your token.
In Cascade, open the MCP panel and refresh servers.

json

{
  "mcpServers": {
    "flowlibs": {
      "serverUrl": "https://www.flowlibs.com/api/mcp",
      "headers": { "Authorization": "Bearer flowlibs_pat_xxxxxxxx" }
    }
  }
}

Tools

All tools require a FlowLibs Pro or Team token. Five catalog tools are exposed — four read-only, plus customize_template:

`search_templates`

Search the cloud-flow catalog.

Parameters: query?, connector?, category?, complexity?, accessLevel? (free|paid), limit? (1–50)
Returns: Lightweight result cards: slug, title, summary, connectors, access level.
Try: “Find a flow that posts Microsoft Forms responses to Teams.”

`get_template`

Full detail for one flow by slug.

Parameters: slug
Returns: Overview, use case, requirements, connectors, environment variables, customizations, and a download link for the solution zip.
Try: “Get the template for the Org Chart Builder to SharePoint flow.”

`get_setup_steps`

An ordered, guided setup checklist for a flow.

Parameters: slug
Returns: Prerequisites, connections to create, environment variables to set, the flow architecture as numbered import steps, recommended customizations, and an estimated setup time.
Try: “Walk me through setting up that flow in my environment.”

`list_connectors`

The connectors used across the catalog.

Parameters: query?
Returns: Connector name, description, and how many flows use each — handy for mapping your stack to templates.
Try: “Which FlowLibs templates use Dataverse?”

`customize_template`

Generate a personalized, importable copy of a flow’s solution.

Parameters: slug, values? (env-var schema name → value), solutionName?
Returns: A short-lived link to a solution zip with your environment-variable values (and an optional new name) baked in. Requires a Pro or Team plan; the package is never returned inline, and connections still bind at import.
Try: “Customize the Bulk Job Progress Tracker with my values and give me the download.”

Entitlements

The MCP server requires a FlowLibs Pro or Team plan — every tool, including discovery and the developer guides, checks your entitlement on each call. Generate a token from your profile and add it to your client; the token resolves your entitlement live, so a downgrade takes effect immediately. Solution downloads are always served from the gated flow page or as a short-lived link — your assistant never receives the file bytes.

Troubleshooting

“Authentication required” or an “upgrade to Pro or Team”message. The request isn't carrying a valid token on a Pro or Team account. Re-check the Authorization: Bearer header (one space after Bearer, no quotes around the token), that the token isn't expired or revoked, and that your plan is Pro or Team.

Server doesn't appear at all. Confirm your client supports remote (Streamable HTTP) MCP servers and the URL is exactly https://www.flowlibs.com/api/mcp (note the www). After editing a config file or env var, fully restart the client.

Rate limited (HTTP 429). The endpoint is capped per client. Wait for the window in the Retry-After header and retry.

FlowLibs MCP Server

Get an access token

Set up your client

Generate a token first (above), then follow your client. Replace flowlibs_pat_xxxxxxxx with your real token, and keep exactly one space after Bearer.

Claude Code

Adds the server over HTTP with the token as a header — one command.

Run the command below (paste your token after Bearer ).
Confirm with /mcp inside Claude Code — the flowlibs tools should be listed.

bash

claude mcp add --transport http flowlibs \
  https://www.flowlibs.com/api/mcp \
  --header "Authorization: Bearer flowlibs_pat_xxxxxxxx"

Claude Desktop

Desktop's “Add custom connector” only supports OAuth, not a static header, so bridge with mcp-remote.

Open Settings → Developer → Edit Config to open claude_desktop_config.json.
Add the flowlibs entry below, putting your token in the FLOWLIBS_AUTH env value.
Save and fully restart Claude Desktop.

json

{
  "mcpServers": {
    "flowlibs": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://www.flowlibs.com/api/mcp",
        "--header", "Authorization:${FLOWLIBS_AUTH}"
      ],
      "env": { "FLOWLIBS_AUTH": "Bearer flowlibs_pat_xxxxxxxx" }
    }
  }
}

The header is passed via an env var (Authorization:${FLOWLIBS_AUTH}) because mcp-remote splits --header on the first space — a literal "Authorization: Bearer …" argument can be mangled.

OpenAI Codex

In the desktop app, add the server by URL and set the token as a header.

Settings → MCP servers → add a server with URL https://www.flowlibs.com/api/mcp.
Under Headers, add key Authorization with value Bearer flowlibs_pat_…, then Save.
Fully quit and relaunch Codex (from the tray / Task Manager, not just the window).

bash

# Set the token in your environment first, then:
codex mcp add flowlibs --url https://www.flowlibs.com/api/mcp \
  --bearer-token-env-var FLOWLIBS_PAT

Cursor

Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project).

Add the flowlibs entry below with your token.
Open Settings → MCP and confirm flowlibs is enabled; refresh if needed.

json

{
  "mcpServers": {
    "flowlibs": {
      "url": "https://www.flowlibs.com/api/mcp",
      "headers": { "Authorization": "Bearer flowlibs_pat_xxxxxxxx" }
    }
  }
}

Keep the token out of the file with "Authorization": "Bearer ${env:FLOWLIBS_PAT}" and set FLOWLIBS_PAT in your environment.

VS Code (GitHub Copilot)

Create .vscode/mcp.json in your workspace — note the servers key and type: "http".

Add the config below with your token.
Open Copilot Chat in Agent mode → Tools, and start the flowlibs server.

json

{
  "servers": {
    "flowlibs": {
      "type": "http",
      "url": "https://www.flowlibs.com/api/mcp",
      "headers": { "Authorization": "Bearer flowlibs_pat_xxxxxxxx" }
    }
  }
}

For a secret prompt instead of a hardcoded token, define an inputs entry and reference it in the header.

Cline

Open the Cline panel → MCP Servers → Remote Servers (or “Configure MCP Servers” for JSON).

Add the flowlibs entry below to cline_mcp_settings.json with your token.
The tools appear once the server connects.

json

{
  "mcpServers": {
    "flowlibs": {
      "url": "https://www.flowlibs.com/api/mcp",
      "headers": { "Authorization": "Bearer flowlibs_pat_xxxxxxxx" },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Some Cline versions had a bug that dropped the Authorization header — update to the latest if tools return “authentication required”.

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json — note the field is serverUrl, not url.

Add the flowlibs entry below with your token.
In Cascade, open the MCP panel and refresh servers.

json

{
  "mcpServers": {
    "flowlibs": {
      "serverUrl": "https://www.flowlibs.com/api/mcp",
      "headers": { "Authorization": "Bearer flowlibs_pat_xxxxxxxx" }
    }
  }
}

Tools

All tools require a FlowLibs Pro or Team token. Five catalog tools are exposed — four read-only, plus customize_template:

`search_templates`

Search the cloud-flow catalog.

Parameters: query?, connector?, category?, complexity?, accessLevel? (free|paid), limit? (1–50)
Returns: Lightweight result cards: slug, title, summary, connectors, access level.
Try: “Find a flow that posts Microsoft Forms responses to Teams.”

`get_template`

Full detail for one flow by slug.

Parameters: slug
Returns: Overview, use case, requirements, connectors, environment variables, customizations, and a download link for the solution zip.
Try: “Get the template for the Org Chart Builder to SharePoint flow.”

`get_setup_steps`

An ordered, guided setup checklist for a flow.

Parameters: slug
Returns: Prerequisites, connections to create, environment variables to set, the flow architecture as numbered import steps, recommended customizations, and an estimated setup time.
Try: “Walk me through setting up that flow in my environment.”

`list_connectors`

The connectors used across the catalog.

Parameters: query?
Returns: Connector name, description, and how many flows use each — handy for mapping your stack to templates.
Try: “Which FlowLibs templates use Dataverse?”

`customize_template`

Generate a personalized, importable copy of a flow’s solution.

Parameters: slug, values? (env-var schema name → value), solutionName?
Returns: A short-lived link to a solution zip with your environment-variable values (and an optional new name) baked in. Requires a Pro or Team plan; the package is never returned inline, and connections still bind at import.
Try: “Customize the Bulk Job Progress Tracker with my values and give me the download.”

Entitlements

Troubleshooting

Rate limited (HTTP 429). The endpoint is capped per client. Wait for the window in the Retry-After header and retry.