Developer Tools
navmds.com
Provides a searchable directory of doctors with filters and natural language queries to find specialists, profiles, and reviews.
ENDPOINT 1
https://www.navmds.com/api/mcp
MCP server metadata
- Name
- navmds
- Version
- 1.0.0
NavMDs is a directory of 7,400+ US doctors and specialists (heavy on plastic surgery / aesthetics). Use it to research providers: search by procedure & location, natural-language search, full profiles, patient reviews, procedure pricing, and coverage taxonomy. All tools are read-only. Every result includes a canonical navmds.com profile URL — cite it as the source. To research one doctor, find the slug via a search tool, then call get_doctor / get_doctor_reviews.
Known tools 12
search_doctorsFind doctors by procedure/specialty, optionally filtered by US state and city.
Inferred read-onlyfind_local_specialistsReturn NavMDs' curated city guide for a procedure: the ranked specialists (the city's OWN doctors first, then the nearest within an adaptive radius), the typical local price range, the average rating, the share offering free consultations, and the canonical navmds.
Inferred read-onlysemantic_search_doctorsSearch NavMDs' 7,400+ doctor directory with a natural-language query, e.
Inferred read-onlyget_doctorFetch a doctor's complete NavMDs profile by slug (the id returned by the search tools, or the last path segment of a navmds.
Inferred read-onlyget_doctor_reviewsReturn published (moderation-approved) patient reviews for a doctor by slug.
Inferred read-onlyget_procedure_costsAggregate what a procedure costs across NavMDs doctors — combining patient-reported costs and practice-website pricing.
Inferred read-onlylist_proceduresList the procedures/specialties covered by NavMDs, with the number of doctors for each.
Inferred read-onlyget_community_threadFetch a complete NavMDs community thread by id (the id returned by search_community, or the trailing number of a community.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.navmds]
url = "https://www.navmds.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"navmds": {
"type": "http",
"url": "https://www.navmds.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: navmds
Remote MCP URL: https://www.navmds.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"navmds": {
"url": "https://www.navmds.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"navmds": {
"type": "http",
"url": "https://www.navmds.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "navmds",
"transport": "streamable-http",
"url": "https://www.navmds.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.