FUSE
Developers/Docs connector
MCP · Public

Build with FUSE docs connector

A public MCP server that gives your AI coding tool FUSE's developer docs and API reference, so it can write correct integration code. No sign-in, no account, read-only.

What it is

Docs connector address
https://docs.mcp.fusehealth.com/mcp

The docs connector answers questions about building on FUSE: which API operation to call, what a request and response look like, how API keys, the sandbox, checkout links, embeds and webhooks work. It reads only FUSE's public documentation.

It is separate from the FUSE AI connector, which signs in to your brand account and makes changes. Use this one while you build; use the AI connector to run your brand.

What it can look up

  • Search FUSE developer docs: full-text search across the guides and the API reference.
  • List FUSE API operations and Get a FUSE API operation: the endpoint, authentication, required key permission, parameters, request body, responses and an example request.
  • Get a FUSE API schema: one named schema, such as Program or CheckoutSession.
  • Get a FUSE integration guide: getting started and API keys, the sandbox and going live, checkout links and the checkout embed, the intake embed, webhooks, and AI connector setup.
  • Get FUSE AI connector info: how to connect the signed-in FUSE AI connector.

Every tool is read-only.

Connect

Add the address above as a remote MCP server (Streamable HTTP). There is no sign-in step: if your app asks about authentication, choose None.

  • Claude: Customize → Connectors → Add custom connector, name it FUSE Docs and paste the address. On Team and Enterprise, an Owner adds it in Organization settings → Connectors.
  • Claude Code: claude mcp add --transport http fuse-docs https://docs.mcp.fusehealth.com/mcp
  • Cursor: Add to Cursor, or add "fuse-docs": { "url": "https://docs.mcp.fusehealth.com/mcp" } under mcpServers in ~/.cursor/mcp.json.
  • VS Code: Install in VS Code.
  • Other apps: see Connect your AI tools and use the docs connector address instead, with no sign-in.

Prompts to try

  • "Using the FUSE docs, how do I create a checkout link for a program from my server?"
  • "What does a FUSE webhook delivery look like, and how do I verify its signature?"
  • "Write a Next.js page that lists my FUSE programs and links each one to checkout."

Privacy and limits

The docs connector serves public documentation only. It has no sign-in, reads no account data and keeps no record of your questions; only standard hosting logs exist. Patient, order and customer endpoints are not documented here. FUSE's privacy policy applies.

To work on a real brand, use an API key or the AI connector. For help, email support@fusehealth.com.