Fuse Health connects healthcare organizations with clinical and operational data, helping teams integrate patient records, streamline healthcare workflows, and improve access to information across healthcare systems.
VS Code
Encrypted at rest, isolated from the model
Resolved from an AES-256-GCM vault at the moment of the call and attached to the request — the model never sees the secrets.
Try asking
Starts going live — moving from the developer sandbox to a real FUSE brand that sells to real patients. Returns two choices, each with a private link that expires in 30 minutes: `choices.diy` (Build yourself: the person onboards themselves on the go-live page, about 4 minutes — company details, plan, the person who signs, then ID, agreements and payment in the brand portal) and `choices.guided` (Book a call with FUSE's team about a guided Growth launch or Partner). The person picks one and completes it on the page. Everything built in the sandbox carries over either way. An account that is already live gets an answer saying so and no links. This produces only the links; it submits nothing.
Explains this FUSE connection: what is real, what is simulated, what is blocked and why, and what changes on a paid account. Answers what FUSE is, why a call was refused, whether a price or a pharmacy name is real, and how to go live.
Returns the brand (clinic) this connection belongs to, its granted scopes and key kind.
List the products available to this brand. Products are the pharmacy-layer SKUs that programs are built from.
Fetch a single product by id, including its structured fields.
The brand's assembled catalog — what this brand can actually sell, resolved across products, programs and pharmacy coverage.
List this brand's programs. A program is the sellable offering a patient buys — it carries pricing, an intake questionnaire and a set of products.
Fetch a single program by id with its full configuration.
A summary across all of this brand's programs — useful for answering 'what do we sell' without paging through the full list.
The FUSE master program templates a new program can be created from — what this brand can sell. Shared across all brands, read-only. Returns one page of short summaries (id, name, description, intake form, product), 25 per page by default; `pagination.total` and `pagination.totalPages` give the full count, and later pages come from `page`. One template's full configuration comes from fuse_get_program_template.
Create a program for this brand. `templateId` (from fuse_list_program_templates) starts it from a FUSE master template, which is what gives the program its intake questionnaire; without one the program cannot take a checkout. The program is created unpublished; creating it does not make it sellable.
Rename an existing program.
Set which products a program sells, by GlobalProduct id (from fuse_get_program_products or fuse_list_program_templates). A program with NO products is not publicly viewable — the storefront returns 'Program is no longer available' — so this is required before a program can be published or take a checkout.
Make a program live on the brand's storefront, or take it down. Programs are created UNPUBLISHED — until this is called nobody can see the program, its intake, or a checkout for it. Requires the program to have products attached first.
The products attached to a program, with their effective pricing. This is the authoritative answer to 'what does this program cost'.
List this brand's treatments (the clinical categories programs sit under).
Set the price a patient pays for a product already attached to this program. A program with no price CANNOT be published (publishing returns PROGRAM_NOT_READY), and an unpriced product is hidden from patient intakes even on a published program.
Create a checkout session for one of this brand's own published programs and return the embed URL a patient would open. On a Developer Preview sandbox the session is marked simulated at creation, so the embed renders the sample intake and a simulated card form: no Stripe call, no charge, and no order is ever created (ADR-012). In a sandbox, test card 4242 4242 4242 4242 approves and 4000 0000 0000 0002 declines.
List this brand's discount coupons and their program scope.
Headline metrics for this brand — revenue, orders, patients, at a glance.
The webhook endpoints this brand has registered, and which events each takes.
Recent webhook delivery attempts with their status: the 'what did we fail to deliver to you' queue, for debugging a brand's integration without reading CloudWatch.
The pages on this brand's website, draft and published. Slugs are unique per brand. The page with `isHomepage: true` is the brand's HOMEPAGE and sorts first: its draft holds the Storefront design, which is built and published in the brand portal, and because `fuse_edit_page` replaces a draft wholesale, editing that page through this connector would destroy the design (KAN-2133). Other pages can be edited freely.
One page with its draft content. Edits replace draftContent wholesale rather than merging into it, so this is the current content an edit would overwrite. A page with `isHomepage: true` holds the brand's Storefront design, which is managed in the brand portal; replacing its draft would destroy that design (KAN-2133).
Create a DRAFT page. It is not visible to anyone until it is published, and publishing is not available through this connector — finish the draft here and publish from the brand portal. Which page is the HOMEPAGE is set in the brand portal too: this tool cannot make a page the landing page, because doing so demotes the existing homepage and would take the brand's Storefront design off the front of the site (KAN-2133). The slug is the page's web address: lowercase letters, numbers and hyphens, 2-100 characters, and it cannot be one of the platform's reserved words.
Edit a page's DRAFT. The live page does not change; publishing is a separate step this connector cannot do. `draftContent` REPLACES the whole draft rather than merging, so the content sent is the page's complete new draft (fuse_get_page returns the current one). This tool cannot change which page is the homepage, and editing the homepage itself would destroy the brand's Storefront design, which is stored as that page's draft (KAN-2133).
The brand site's header and footer menus.
Replace the site's header and/or footer menu. Unlike the rest of this API, a menu left out of the call is ERASED, not left alone, so changing one menu while keeping the other means sending both (fuse_get_navigation returns the current pair).
One coupon's configuration. Its redemption history is not available here.
Create a discount code for this brand. A discount only ever reduces what the CUSTOMER pays and what the BRAND earns — pharmacy, doctor, Stripe and merchant fees are never discounted. `overMarginBehavior` decides what happens when a discount would push a sale below cost: `reject` refuses it, `cap` limits the discount, `absorb` lets the brand carry the loss.
Change a coupon. Deactivating it with `isActive: false` stops new redemptions; it does not affect subscriptions that already carry it.
Everything blocking a program from being sold, in one answer: missing pricing, an unapproved questionnaire, no pharmacy in a shipping state. Explains why a program will not publish.
Per-product activation state for a program — what is on sale and what is not.
Per-product visibility for a program. A product can be active but hidden, so this and activation status answer different questions.
Copy a program. The copy is created INACTIVE and has never been published, so it is safe to make one and edit it before anything is visible to patients.
Sets the picture shown for a program on this brand's storefront, from the https address of a JPEG, PNG, WebP or GIF image (5 MB max). FUSE downloads the image and keeps its own copy, so the address can change later without affecting the storefront. The address must be a public website, must serve the image file itself (not a web page containing it) and must not redirect. It replaces the program's current picture. Products' catalog images are managed by FUSE and are not changed by this.
A template a program can be created from, with its configuration.
The catalog as the brand has configured it.
Products the platform has discontinued that this brand is still selling. These will stop being fulfillable, so this is a list worth acting on rather than noting.
The pharmacies that can fill a product and the states they cover. A product with no pharmacy in a patient's shipping state cannot be sold to them.
One treatment and the products attached to it.
Headline totals for this brand. Aggregates only.
One endpoint, the same key, whichever client you use.
~/Library/Application Support/Claude/claude_desktop_config.json (Mac) · %APPDATA%\Claude\claude_desktop_config.json (Windows)
Replace API_KEY with your own key.
Already have an "mcpServers" section in your config? Just add the server entry inside it.
Discovery, routing, credentials, tool scoping and execution logs all happen at the gateway→connections stay ACTIVE with no work from you
Fuse Health MCP runs through a gateway that holds the credentials, scopes the access and records every call.
Managed auth, hosted MCP servers, and every Gmail tool your agent needs.
Free to start.
