MCP Client

Server vs. client

MCP Server covers what Fimaflow exposes — the tools an assistant can call, what they return, what they're scoped to. This page covers the other half: what you configure on your side so an agent can actually reach that server in the first place. There's nothing to install — an MCP client is a capability most AI tools already have, off by default until you give it a server to talk to.

Getting a connection URL

Open a workflow in the builder, click MCP in the left sidebar, then New connection. You get one URL, shown once — it's the only credential your client needs, so save it somewhere before closing the panel.

Configuring your client

Every MCP client expects the same shape — a server entry with a URL, no separate token or header to add:

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

Where that JSON goes, and the exact click path in the UI, differs per client:

• • Claude Desktop / Claude Code — claude_desktop_config.json or .claude/mcp.json.
• • Cursor — Settings → MCP, add a new server.
• • ChatGPT — connector settings, added as a custom connector (plan-dependent).
• • JetBrains AI — Settings → Tools → AI Assistant → MCP.

See Integrations for the full click-by-click steps and troubleshooting per client — this page stays at the "what is a client, what does it need" level.

Verifying the connection

Restart the client — most don't pick up MCP config changes live — then ask it directly: "What Fimaflow tools do you have access to?" A working connection lists the tools from MCP Server — about_fimaflow, list_workflows, get_workflow, and the rest.

Not the same as the MCP Client node

The builder also has an MCP Client node, which lets one of your own workflows call out to a different MCP server — the reverse direction from everything above, where an assistant calls into Fimaflow. See Nodes for that node's config fields.

Limitations

• • The connection URL is the only credential — anyone with it has whatever access that connection grants. Treat it like a password, and revoke it from the workflow's MCP panel if it leaks.
• • Almost every client requires a restart (or an explicit "reload MCP servers") after editing its config — it won't pick up a new connection live.
• • One connection is scoped to one workflow's project (or its whole workspace) — connect several workflows and your client sees a separate server entry for each.