Doktor MCP Server

MCP Server para buscar médicos verificados en México — doktor.mx. The doktor mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 10 defined tools rather than through you.

What it actually does

MCP Server para buscar médicos verificados en México a través de doktor.mx — el directorio médico más completo del país.

Its toolset

Everything the assistant can do here goes through one of these:

• buscar_doctor — Busca médicos por especialidad, ciudad, estado o nombre en doktor.mx
• ver_perfil — Obtiene el perfil completo de un médico incluyendo formación académica verificada, horarios, precios y reseñas
• verificar_cedula — Verifica si un médico tiene cédula profesional validada por la SEP
• buscar_por_padecimiento — The buscar_por_padecimiento tool exposed by this server
• buscar_por_sintoma — A partir de un síntoma, sugiere posibles padecimientos y especialistas. Incluye disclaimer médico
• buscar_por_seguro — The buscar_por_seguro tool exposed by this server
• especialidades_disponibles — Lista todas las especialidades médicas disponibles con el total de doctores en cada una
• ciudades_disponibles — Lista ciudades con médicos registrados, filtrable por estado
• estados_disponibles — The estados_disponibles tool exposed by this server
• buscar_articulo_salud — Busca artículos de salud sobre padecimientos, tratamientos y prevención

Configuration

You will need one environment variable: DOKTOR_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at doktor-mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Doktor's toolset — buscar_doctor, ver_perfil, verificar_cedula and 7 more — is a fair guide to whether it matches your workflow. It is maintained by vanguardiaai; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Doktor.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the doktor mcp server does with a few real requests.