MCP getting started#

The remote Doctosan MCP server exposes the same published directory as the REST API through two read-only tools:

Tool	Purpose
`search_doctors`	Search a bounded page by country, city, text, verification, and WhatsApp reachability.
`get_doctor`	Fetch one current published record by its Doctosan id or canonical profile URL.
`show_doctor`	Show that same public profile in an inline MCP App card.
`show_doctor_search`	Show a bounded search page in an inline MCP App card.

Remote server#

https://mcp.doctosan.com/mcp

Create a key in the developer console, then supply it as a Bearer token in the MCP connection:

{
  "mcpServers": {
    "doctosan": {
      "type": "http",
      "url": "https://mcp.doctosan.com/mcp",
      "headers": {
        "Authorization": "Bearer dct_live_replace_me"
      }
    }
  }
}

Use your client's secret or environment-variable interpolation feature instead of committing the literal key to a configuration repository.

Local stdio transport#

The package can also run over stdio from this monorepo:

DOCTOSAN_API_KEY='dct_live_replace_me' \
  pnpm --dir doctosan/mcp exec node stdio.js

Tool behavior#

Tool results include concise Markdown for the model and bounded structured content for hosts. All tools call the versioned Doctosan REST API, so their authentication, field meanings, publication boundary, cursors, and rate-limit behavior match the Doctors API.

The two show_ tools reuse the same read handlers and require the same developer key. Their static ui://doctosan/ resources can be read by an MCP host before authentication; the resources contain no private data and do not make browser network requests. Hosts with MCP Apps support may display the profile and search cards inline. A host must support a configured Bearer header to call Doctosan tools. These resources do not establish a ChatGPT or Claude directory listing, and Doctosan does not currently offer MCP OAuth.

Outreach requests

An agent may use whatsappEligible to identify records for review. The MCP server does not send messages, establish consent, or approve outreach. Apply the outreach data boundary before acting on a result.