MCP server

Run your telehealth brand from a conversation

Connect Claude, Cursor or any MCP client to your Bask account. Your agent builds sites, intake flows and catalog with the same operations your team uses in Studio.

Connect an agent
bask-agent
Claude Code

bask · streamable HTTP · your API key

Create a weight-loss intake for Lumen with a clinical assessment, the GLP-1 programme and checkout.

  1. baskMCP server connected · 180+ toolsRead bask://guides/getting-started
  2. flows.createGraphWeight-loss intake · entry and checkout
  3. flowGraph.createNodeWithStepGoals & BMI · Medical history
  4. flows.ensureMedicalAssessmentClinical assessment before plan selection
  5. flowGraph.createTransitionBMI under 27 → alternatives
  6. flows.setStoreProductsGLP-1 programme offered at plan selection
  7. flows.validateNo dead ends, no orphan steps
  8. Draft intake ready to preview · nothing is live until you publish.
Connect your AI

Connect Bask to Claude Code, Cursor, Codex and more

Three steps and an API key. Nothing to install on your side, nothing to host.

  1. claude mcp add --transport http bask \
    https://api.bask.health/api/headless/v1/admin/mcp \
    --header "Authorization: Bearer ak_live_…"

    1. Add the Bask server

    Run the install command for your client with an API key from your Bask admin. One line in Claude Code or Codex, one file in Cursor.

  2. claude mcp list
    bask: …/headless/v1/admin/mcp (HTTP)
    ✓ Connected

    2. Check the connection

    List your servers and confirm bask is connected. The agent now sees every tool your key is allowed to use.

  3. > Build a site for Lumen, our weight-loss
    brand, with an intake and a checkout.

    3. Write your first prompt

    Describe the brand, the treatment and the market. The agent reads Bask’s playbook, builds a draft, and shows you a preview before anything goes live.

FAQ

What an agent can do on your account, and what it can’t do without you.

A remote Model Context Protocol server that exposes Bask’s admin operations as tools. Connect an AI agent to it and the agent can build sites, themes, intake flows and catalog, and read flow analytics, on your account.

Any client that supports remote MCP servers over streamable HTTP. That includes Claude Code, Cursor and Codex, which is what the setup steps on this page cover.

Pricing releases, fulfillment changes and product archival are two-phase. The first call returns a preview and writes nothing; the change only happens when it is confirmed, and agents are instructed to show you that preview rather than confirm it themselves.

The agent authenticates with an API key you issue from your Bask admin. Give it its own key so you can revoke it on its own, and every call is logged against the key that made it.

Yes. Everything the agent creates is a normal Bask site, flow and catalog. Open it in Studio and carry on by hand, or keep going from the agent.

It is the same platform underneath. Every MCP tool is also a Studio action and a REST endpoint, so what an agent does, your team or your own code can do too.

Give your agent a telehealth platform

Pharmacy, prescribing and payments are already wired. Your agent only has to build the brand.