Connect FUSE to your AI tools

Before you start

https://mcp.fusehealth.com/mcp

Every app connects the same way:

• The address above. If the app asks for a transport, choose Streamable HTTP (some apps just say HTTP).
• OAuth sign-in. Leave any client ID and client secret fields empty: FUSE registers the app automatically.
• Your brand portal login. When the Sign in with FUSE page opens, sign in as described in Connect. Don't use "Create a free developer account" for your real brand: that makes a separate sandbox.

Claude

On claude.ai and in the Claude desktop app. Once added, FUSE is also available in the Claude mobile apps.

Free, Pro and Max

1. Go to Customize → Connectors. In the desktop app, select Customize in the sidebar, then Connectors.
2. Choose Add custom connector, name it FUSE and paste the connector address.
3. Leave the OAuth client ID and secret empty. If Claude asks how to register its OAuth client, choose Register automatically.
4. Select Add, then Connect if the Sign in with FUSE page doesn't open on its own. In the desktop app it opens in your browser.

The Free plan allows one custom connector, so FUSE needs that slot to be free.

Team and Enterprise

Members can't add custom connectors themselves. An Owner or Primary Owner adds FUSE once for the organization (on Enterprise, so can anyone whose custom role lets them manage the organization's libraries):

1. Go to Organization settings → Connectors, select Add, then Custom. If asked for the type, choose Web.
2. Paste the connector address and select Add.
3. Each member then goes to Customize → Connectors, finds FUSE (it has a Custom label), selects Connect and signs in with their own FUSE login.

In a chat: select +, then Connectors, and check FUSE is switched on.

Claude Code

claude mcp add --transport http --scope user fuse https://mcp.fusehealth.com/mcp

--scope user makes FUSE available in all your projects. Leave it out to add FUSE to the current project only.

1. Start Claude Code and run /mcp.
2. Select fuse, then Authenticate. Your browser opens the Sign in with FUSE page.

You can also sign in from your shell with claude mcp login fuse. On a machine without a browser, add --no-browser: it prints the sign-in link, and you paste the address you end up on back into the terminal.

Already added FUSE on claude.ai? Claude Code picks it up when you're signed in with the same Claude account.

ChatGPT

FUSE isn't in ChatGPT's public directory, so you add it as a custom MCP server. Do this in ChatGPT on the web.

1. Go to Plugins (chatgpt.com/plugins), select +, then Add custom MCP server.
2. Name it FUSE. Under Connection, paste the connector address as the Server URL.
3. For authentication, choose OAuth.
4. Review the warning, select I understand and want to continue, then Create as a plugin.
5. In your personal plugins, open FUSE and select + to install it. Sign in with FUSE when ChatGPT asks.
6. In a chat, type @ and choose FUSE.

Business, Enterprise and Edu

Your workspace's permissions decide whether members can add custom MCP servers. If you don't see Add custom MCP server, ask a workspace admin.

To give the whole workspace FUSE, a workspace admin adds it as above, then on Plugins selects Personal, opens FUSE's ⋯ menu, selects Publish and chooses which workspace roles get it. Publishing keeps FUSE inside your workspace.

Codex

The Codex CLI, the Codex IDE extension and the ChatGPT desktop app share one MCP setup, so you add FUSE once.

codex mcp add fuse --url https://mcp.fusehealth.com/mcp
codex mcp login fuse

The second command opens the Sign in with FUSE page. To add it by hand instead, put this in ~/.codex/config.toml:

[mcp_servers.fuse]
url = "https://mcp.fusehealth.com/mcp"

In the ChatGPT desktop app: open Settings, select MCP servers, then Add server. Choose Streamable HTTP, paste the connector address, save and select Restart, then Authenticate.

Cursor

With Cursor installed, the button opens it with FUSE ready to add. Follow Cursor's prompts to install it and sign in with FUSE.

To add it by hand, put this in ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "fuse": { "url": "https://mcp.fusehealth.com/mcp" }
  }
}

In the Cursor CLI, sign in with agent mcp login fuse.

VS Code and GitHub Copilot

Needs VS Code 1.99 or later. The button opens VS Code with FUSE ready to install. To share FUSE with everyone on a project instead, add a .mcp.json file at the project root:

{
  "mcpServers": {
    "fuse": { "type": "http", "url": "https://mcp.fusehealth.com/mcp" }
  }
}

1. In Copilot Chat, select Agent.
2. The first time VS Code connects to FUSE, the Sign in with FUSE page opens in your browser.

On Copilot Business or Enterprise, an organization admin must turn on the MCP servers in Copilot policy first. It is off by default.

Lovable

Once connected, Lovable's agent can use FUSE in the project chat and in Chats while you build. It is not part of the app you publish. Available on all Lovable plans.

1. Open Connectors, select the + button at the top right of the catalog and choose MCP server.
2. Enter FUSE as the Server name and paste the connector address as the Server URL.
3. Keep OAuth and select Add & authorize, then sign in with FUSE.

If MCP server is greyed out, a workspace admin has turned off custom MCP servers.

Bolt

1. On the Bolt homepage, select the + in the chatbox, then Connectors, then Manage connectors.
2. Select Custom MCP server. Enter FUSE as the name, paste the connector address as the URL, and choose HTTP for the transport type and MCP OAuth for authentication.
3. Select Connect and sign in with FUSE.
4. Turn FUSE on for a project: in the project, select +, then Connectors, and switch it on. Or select Auto-enable for all projects.

Base44

Needs a Base44 Builder plan or higher. FUSE is then available in the editor chat while you build, not in your published app.

1. Select your workspace name at the bottom left, then Account preferences.
2. Select Builder, scroll to MCP Connections and select Add custom MCP.
3. Enter FUSE as the name, paste the connector address as the URL and choose OAuth.
4. Select Test, then Test & add, and sign in with FUSE.

Gemini CLI

gemini mcp add --scope user --transport http fuse https://mcp.fusehealth.com/mcp

Without --scope user, FUSE is added to the current project only. Then, inside Gemini CLI, run /mcp auth fuse to open the Sign in with FUSE page. Sign-in needs a browser on the same machine.

To add it by hand, put this in ~/.gemini/settings.json:

{
  "mcpServers": {
    "fuse": { "httpUrl": "https://mcp.fusehealth.com/mcp" }
  }
}

Microsoft Copilot Studio

This adds FUSE as a tool to one of your Copilot Studio agents.

1. On your agent's Tools page, select Add a tool, then New tool, then Model Context Protocol.
2. Enter FUSE as the Server name, a short Server description (for example "Manage our FUSE brand: programs, prices, coupons and storefront") and the connector address as the Server URL.
3. Choose OAuth 2.0, then Dynamic discovery. Select Create, then Next.
4. On Add tool, select Create a new connection, sign in with FUSE, then select Add to agent.

Power Platform data policies that cover connectors also cover FUSE.

n8n

Give an AI Agent node the MCP Client Tool as one of its tools, and set:

• Endpoint: the connector address.
• Server Transport: HTTP Streamable.
• Authentication: MCP OAuth2. Create a new MCP OAuth2 API credential, keep Use Dynamic Client Registration on, and sign in with FUSE from the credential.

Perplexity and Grok

• Perplexity (Pro, Max and Enterprise): in Account settings → Connectors, select + Custom connector, choose Remote, paste the connector address as the MCP Server URL, choose OAuth and Streamable HTTP, tick the acknowledgement and select Add. Then select the FUSE card to sign in. On Enterprise, an admin has to let members add custom connectors first.
• Grok: go to grok.com/connectors, select New Connector, choose Custom, paste the connector address and sign in. On Grok Business and Enterprise, a team admin has to add it first in the xAI console.

Any other app

Any AI app that can add a remote MCP server with OAuth sign-in should work: use the address above, choose Streamable HTTP and OAuth, and leave the client ID and secret empty. If your app only accepts a fixed client ID and secret, or something above no longer matches what you see, tell us which app you're using.