Skip to main content

Documentation Index

Fetch the complete documentation index at: https://isaree-cd4b6397.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Register an MCP server on the Community Hub so you and other clinicians can install it from the Isa Hub. Once installed, its tools are available to the Primary Agent in Patient Chat alongside the Primary Agent’s other tools.
Registering an MCP server is a technical workflow — you need to know the server’s transport URL and the configuration it requires. If you’re not sure where to start, ask in the Isaree Discord.
What “registering” means: the MCP server itself runs elsewhere — a public service you’re pointing to, or one you’ve deployed yourself. On the Community Hub you’re publishing a pointer to it: the transport URL, the configuration it needs, and the metadata that helps others discover it. You can register from scratch or duplicate an existing MCP server on the Community Hub and adapt it.

​
Prerequisites

  • A Community Hub account
  • An MCP server you can point to — public or self-hosted — reachable from the devices Isa runs on
  • The configuration the server expects (API keys, base URLs, tenant IDs) so you can declare it on the Community Hub

​
Open the form

Sign in to the Community Hub and register a new MCP server from the Build menu in the top navigation. The form opens with the MCP server’s fields ready to fill in.

​
Name your server

Your server’s name is how other clinicians find it in the Isa Hub — prefer something concrete like EMR Lab Lookup over My MCP Server.

​
Add a description

Write one or two sentences on what tools the server exposes and what system it connects to — that’s what other clinicians see when they find your MCP server in the Isa Hub.

​
Set the transport URL

Enter the endpoint where your MCP server lives — this is what the Primary Agent calls when it uses one of the server’s tools. 
https://your-mcp-server.example.com/mcp

​
Pick a category and add keywords

  • Category — Admin or Clinical.
  • Keywords — comma-separated tags that help others find your MCP server when searching. Add a few that match the system it connects to, the data it exposes, or the use case (e.g. lab, EMR, epic).

​
Define the configuration schema

Declare the values your MCP server needs to work — an API key, a base URL, a tenant ID, anything the server can’t infer on its own. Expose only what’s actually required. Add a config field for each value the server needs. Each field has:
  • Field Key — the key sent to the server. Use snake_case (api_key, not API Key).
  • Title — the label for the field.
  • Type — the data type (String, Number, Boolean).
  • Input Type — how the field is rendered (text, password, etc.).
  • Description — a short hint about what value to provide.
  • Placeholder — example text shown inside the empty field.
  • Default Value — pre-filled value if there’s a sensible default.
  • Secret — tick if the field holds a secret like an API key. Secrets are hidden in the UI and handled separately from non-secret values.
  • Required — tick if the server can’t run without this field.
  • Display Order — controls the order the fields appear.
The first Secret field is sent by default as an Authorization: Bearer <value> header. If your server uses a different scheme, map it under Advanced Settings.

​
Map custom headers

Most servers using bearer-token auth don’t need this — the first secret field is sent as Authorization: Bearer <value> automatically. Open Advanced Settings to map config fields to different HTTP headers if your server expects a custom scheme.

​
Register the server

Once the required fields — Server Name, Description, and Transport URL — are filled in, add the server. It now exists on the Community Hub and is ready to install from the Isa Hub.

​
See how the tools become available

Once a clinician installs your MCP server in Isa, its tools become available to the Primary Agent in Patient Chat. The user doesn’t invoke the MCP server directly — they chat with the Primary Agent, which picks up the tools automatically.
Only the Primary Agent can call MCP servers today — Agents cannot (yet). If you’re building an Agent that needs external tools, plan around the Primary Agent being the entry point.

​
Next

MCP servers

Understand what MCP servers are and how the Primary Agent reaches them.

Primary Agent

Set the agent in Isa that calls your MCP server’s tools.

Build an agent

Build an Agent for Patient Chat or Workspace.