Integrations

Why connect an assistant here

Without a connection, an assistant only knows what you paste into the chat — a snippet of code, a copied error message. Connected, it can look things up itself: list your workflows, inspect one's nodes and edges, check its run history, spot structural issues — all without you leaving your editor or chat window to switch into the builder. You stay the one deciding what it does — see Permissions & safety.

Claude Desktop & Claude Code

Claude Desktop: add the server to claude_desktop_config.json, then restart the app. Claude Code: one command instead of a file — see Connecting Claude Code. For Claude Desktop:

{
  "mcpServers": {
    "fimaflow": {
      "url": "https://mcp.fimaflow.com/<connection-secret>/<workflow-id>"
    }
  }
}

No separate token or header — the URL itself is the credential. Copy it from the MCP panel in the builder's sidebar (see Setting it up) — it's shown once, at creation.

Ask Claude to list your tools to confirm the connection: "What Fimaflow tools do you have access to?"

Cursor

Open Settings → MCP and add a new server with the same URL. Cursor lists the connected tools under the agent panel — enable the ones you want available in a given chat.

ChatGPT

Add Fimaflow as a custom connector from ChatGPT's connector settings, using the same URL. Custom connectors are available on ChatGPT plans that support them — check your plan if you don't see the option.

JetBrains AI

Across the JetBrains IDE family, add the server from Settings → Tools → AI Assistant → MCP. The same URL works everywhere — one connection per workflow you want to expose, not one per IDE.

If the assistant can't see your tools

• • Restart the assistant after adding or editing the config — most don't pick up MCP changes live.
• • Check the connection hasn't been revoked from the workflow's MCP panel.
• • Confirm you copied the whole URL — it's the only credential, and it only works for the project it was generated for.