Platform / Developers

Built to be built on.

Three steps to a real record. Reference docs live at https://docs.practicemcp.com. This marketing site is the map. The docs are the contract.

Get a key

Request access. Keys go out by email as workspaces are opened. The key is a bearer token.

Call search

Filter by state, specialty, ownership, and size. The first page is enough to see the shape.

Open the evidence

Add expand=evidence on a location, or point an MCP client at the same key.

curl "https://api.practicemcp.com/v1/practices?state=TX&specialty=dental&ownership=independent&provider_count_gte=3&has_booking=false" \
  -H "Authorization: Bearer $PRACTICEMCP_API_KEY"

Webhooks

Events, posted to you.

Available on Build and above. You name the URL and the event types. We sign the request. A missed delivery is retried, then surfaced, not silently dropped forever.

Create

curl -X POST "https://api.practicemcp.com/v1/webhooks" \
  -H "Authorization: Bearer $PRACTICEMCP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/hooks/practicemcp",
    "events": ["provider_added", "phone_changed", "website_found"]
  }'

Bulk

A file when a file is the interface.

CSV or Parquet for a filter, on Scale and National. The location id is the join key back to the API.

Export

curl -X POST "https://api.practicemcp.com/v1/exports" \
  -H "Authorization: Bearer $PRACTICEMCP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "format": "parquet",
    "filter": { "state": "TX", "specialty": "dental" }
  }'

What you get

REST reference at https://api.practicemcp.com/v1
MCP server and the six tools
OpenAPI and guides at docs.practicemcp.com
llms.txt for agents that read the site before they call it
SDKs in Python and TypeScript track the same parameters as the HTTP API

Start with one practice. Scale to all of them.

Get a key, read a record, and widen the query when the shape is right.

Get API key Talk to sales