MCP server · DexCare

DexCare (candidate MCP server)

DexCare publishes no Model Context Protocol server. Searched the DexCare developer portal (developers.dexcarehealth.com), dexcare.com, the DexCare GitHub organization (8 public repos, none MCP-related) and the npm registry; no hosted endpoint and no stdio package exists. The tools below are DERIVED from the six OpenAPI definitions DexCare publishes on its own developer portal, as a candidate surface only. Nothing here is an endpoint an agent can call today.

View descriptor → DexCare provider profile

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

⚠ Proposed MCP surface. No official hosted MCP server was found for DexCare. The tools below are a candidate set derived from this provider's API, and the link points at the source descriptor rather than a live server. If DexCare publishes an official server, this page will update to it on the next build.

Provider: DexCare Type: Candidate descriptor Transport: Host: raw.githubusercontent.com

Descriptor

https://raw.githubusercontent.com/api-evangelist/dexcare/refs/heads/main/mcp/dexcare-mcp.yml

Candidate descriptor · transport

Tools

search_care_options — Retrieve aggregated in-person and virtual appointment slots via GET /availability/slots.
search_care_options_advanced — Retrieve aggregated availability with a filter body via POST /availability/slots.
find_available_providers — Find providers with availability matching the supplied criteria via POST /availability/providers.
get_provider_timeslots — Retrieve open timeslots for a single provider by NPI via GET /providers/{npid}/timeslots.
search_slots — Search slot availability across departments and visit types via POST /slots/search.
create_visit — Create a virtual visit via POST /visits. Requires a patient JWT.
get_visit_wait_time — Get the estimated wait time for an existing virtual visit via GET /visits/{visitId}/waittime.
get_visit_summary — Retrieve a visit summary via GET /visits/{visitId}/summary. Requires a staff JWT.
get_region_wait_times — Retrieve virtual-care availability and wait times for all regions via GET /regions/waittimes.
get_region_wait_times_by_code — Retrieve availability and wait times for one region via GET /regions/{regionCode}/waittimes.
list_modalities — List supported visit modalities via GET /modalities.
list_assignment_qualifiers — List provider assignment qualifiers via GET /assignmentqualifiers.
create_queued_guest_visit — Book a queued guest visit via POST /booking/queued-guest-visit.
query_provider_entities — Batch-query provider data management entities by type via POST /pdm/batch.
get_provider_entity_schema — Retrieve the JSON Schema for a PDM entity via GET /pdm/schema/{namespace}/{name}.
omni_search — Execute a natural-language care search via GET /api/OmniSearch/{version}.
omni_get_data — Retrieve clinician or department records by identifier via GET /api/OmniData/{version}.
omni_search_facets — Retrieve available search facets via GET /api/OmniSearchFacets.
omni_synonyms — Retrieve clinical synonyms for a keyword via GET /api/OmniSynonyms.

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.