Classic MCP servers expose one operation per tool call — search a type, wait, introspect it, wait, build a query, wait. Dev Assist 2.0 changes this with a code execution model: your AI writes a small TypeScript program that performs all steps in a single turn.

Example: "Find all appointment mutations and show me what createAppointment takes" — previously 3+ tool calls. In 2.0:

const mutations = await healthie.search("appointment", { kind: "mutation" });
const details = await healthie.introspect("createAppointmentInput");
return { mutations, details };

Done in one execution.

Your AI has access to a single healthie object inside a sandboxed Node.js environment (no filesystem, network, or shell access — only these methods):

// Search the schema by keyword
healthie.search(query: string, options?: { kind: "query" | "mutation" | "type" }) → SearchResult[]

// Get full details on any type, query, or mutation
healthie.introspect(typeName: string, options?: { depth: number }) → TypeDetails

// Execute a GraphQL query
healthie.query(graphql: string, variables?: Record<string, unknown>) → any

// Execute a GraphQL mutation
healthie.mutate(graphql: string, variables?: Record<string, unknown>) → any

git clone https://github.com/healthie/healthie-dev-assist.git
cd healthie-dev-assist
npm install

cp .env.example .env

Edit .env:

HEALTHIE_API_KEY=your-api-key-here

Schema search and introspection work without a key. query and mutate require one.

npm run regenerate-schema

Fetches Healthie's GraphQL schema and caches it locally. Re-run after API updates.

npm run setup

claude mcp add healthie -- npx tsx /path/to/healthie-dev-assist/src/server.ts

{
  "mcp": {
    "servers": {
      "healthie-dev-assist": {
        "command": "npx",
        "args": ["tsx", "/path/to/healthie-dev-assist/src/server.ts"]
      }
    }
  }
}

npm run build

Run this single command in your terminal:

curl -fsSL https://raw.githubusercontent.com/healthie/healthie-dev-assist/main/upgrade.sh | bash

This will automatically:

• Find your existing installation
• Download the latest version
• Preserve your API key
• Update your Claude Desktop configuration

Restart Claude Desktop after it completes.

Other platforms: Pull the latest code manually, then run npm run setup from the project directory.

Once connected, ask your AI naturally:

• "Find all patient-related queries and show me what fields are available"
• "What arguments does createAppointment take?"
• "Fetch the last 5 appointments for patient ID 123"
• "Show me all mutations related to billing"

The AI handles schema exploration and API calls in one or two turns.

To run separate staging instances (e.g. different API keys):

cp environments.example.json environments.json

Edit environments.json:

{
  "staging": {
    "apiUrl": "https://staging-api.gethealthie.com/graphql",
    "apiKey": "your-staging-key"
  }
}

Add one MCP server entry per environment, passing HEALTHIE_ENV:

{
  "mcpServers": {
    "healthie-staging": {
      "command": "npx",
      "args": ["tsx", "/path/to/healthie-dev-assist/src/server.ts"],
      "env": { "HEALTHIE_ENV": "staging" }
    }
  }
}

Use staging only. Do not connect this tool to a production Healthie environment. Most AI platforms do not have a Business Associate Agreement (BAA) in place, and production data contains PHI.

• GitHub Issues
• Healthie API Docs