Sally Health Skills MCP

Sally exposes health-data and knowledge skills through an account-based MCP endpoint with bearer authentication for tool execution.

Remote serverstreamable-httpGo

What is the Sally Health Skills MCP Server?

Sally exposes health-data and knowledge skills through an account-based MCP endpoint with bearer authentication for tool execution.

Connect the account and skill catalogue

Sally's developer platform exposes health-context, nutrition, laboratory and knowledge workflows. The documented MCP route can publish a tool catalogue without authentication, while execution uses a Sally account key. Discovery and a successful billed result are different steps.

Data-dependent skills need connected data

Some skills can work with supplied inputs or the service's knowledge resources. Others depend on the account's connected glucose, wearable or health data. The documentation distinguishes those cases and describes a no-health-data error when a required source is absent. A console-only key should not be assumed to contain a person's biomarker history.

Review access and the output

Use a separate key for the intended agent and inspect the available schemas before enabling a workflow. Consider what health information a request sends to the service and which account it belongs to. Generated health interpretations require appropriate review and should not be represented as independently validated clinical decisions. The service's account, billing and data permissions determine the usable tool access.

Project documentation

Repository and setup guide

How to install the Sally Health Skills MCP Server

{
  "mcpServers": {
    "sally": {
      "url": "https://sally.a1c.io/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_SALLY_API_KEY"
      }
    }
  }
}

Configuration

A Sally Console account key and the data required by the selected skill. Tool execution follows service billing and account access.

Frequently asked questions

No. The documented interface distinguishes public lifecycle or discovery methods from bearer-authenticated tool execution.