Connect FindDoc via MCP

Use cases for your agent

FindDoc gives your agent structured, freshness-stamped access to Ontario health-navigation data. A few things that get unlocked — or get strictly better — once the MCP is connected:

• Summarize doctor or clinic reviews by the criteria you care about

  get_clinic_reviews, get_clinic_signals, and get_doctor_signals return per-dimension review signals — a strength score and a strong/moderate/mixed/weak band for things like wait times, communication, and staff — alongside the raw reviews. Your agent reasons over structured signal, not just a star average.

• Plan a visit to a family doctor, end to end

  search_doctors finds family doctors taking patients near you; get_doctor returns the clinic's address, phone, and accepting status — so your agent can tell you exactly who to call and where to go. (FindDoc surfaces how to reach the clinic; it doesn't book the appointment for you.)

• Find a clinic near you that's accepting new patients

  search_clinics returns nearby clinics taking patients, each with the languages its doctors speak — so your agent can narrow to, say, a French-speaking clinic in Scarborough.

• Check every week for clinics that have started accepting patients

  Point a scheduled agent at search_clinics and have it remember last week's list — it can tell you which clinics are newly accepting since the last run. FindDoc provides the live, freshness-stamped data; your agent owns the schedule and the diff.

Every availability answer carries a freshness timestamp, and each tool reminds the agent to surface how current the data is — so it can always tell you to confirm with a phone call before relying on it.

1. Install the CLI

The config blocks below run the server with npx, so a global install is optional — but installing it once makes startup faster.

npm install -g @find-doc/finddoc-mcp
# or run it on demand, no global install:
npx @find-doc/finddoc-mcp

2. Add FindDoc to your client

Pick your client below. Each snippet registers the same finddoc stdio server; you only need one.

Replace YOUR_API_KEY in each snippet with a key from API keys.

claude mcp add --env FINDDOC_API_KEY=YOUR_API_KEY --transport stdio finddoc \
  -- npx @find-doc/finddoc-mcp

{
  "mcpServers": {
    "finddoc": {
      "command": "npx",
      "args": ["@find-doc/finddoc-mcp"],
      "env": {
        "FINDDOC_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

[mcp_servers.finddoc]
command = "npx"
args = ["@find-doc/finddoc-mcp"]
env = { FINDDOC_API_KEY = "YOUR_API_KEY" }

{
  "mcpServers": {
    "finddoc": {
      "command": "npx",
      "args": ["@find-doc/finddoc-mcp"],
      "env": {
        "FINDDOC_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

3. Start using it

Restart the client (Claude Code and Codex pick up the server on the next session; quit and reopen Claude Desktop). The finddocserver should show up in the client's MCP list. Ask something like "find a family doctor in Scarborough accepting patients" — it will call FindDoc directly.

Tool reference

The server registers 10 tools. Your agent picks the right one on its own, but the required arguments are worth knowing — search_doctors requires a specialty, so call list_specialties if you are not sure a name is accepted.