MCP Server
Connect any MCP client — Intercom Fin, Claude, Cursor — to the live provider directory.
The public provider directory is also available as an MCP server, so an
AI assistant can look up providers, insurance, states, and live openings
mid-conversation. It's the same data as the REST API, served over the same
no-auth policy — no key, no Authorization header.
Endpoint
https://developer.mymenopauserx.com/api/mcpStreamable HTTP transport. No API key, no Authorization header.
Use /api/mcp
The legacy SSE transport is not currently enabled — connect clients to
/api/mcp.
Tools
| Tool | What it answers | Key inputs |
|---|---|---|
list_states | Which states we serve | none |
list_insurances | Which plans we accept | state (optional) |
search_providers | Which clinicians match a state, insurance, type, or gender | state, insurance, providerType, gender, limit, offset (all optional) |
get_provider | A specific clinician's full public profile | slug (required) |
list_appointment_types | What kinds of visits we offer | state (optional) |
check_availability | When a customer can be seen | state (required), appointmentType, provider, horizonDays, limit (optional) |
Connecting
In Fin, go to Settings → Custom MCP connector, paste the endpoint URL above, and leave auth blank. Enable the six tools.
Fin makes one connector call per turn, so start broad — list_states or
list_insurances — before drilling into search_providers or
check_availability.
claude.ai: Settings → Connectors → Add custom connector → paste the endpoint URL.
Claude Code:
claude mcp add --transport http mymenopauserx https://developer.mymenopauserx.com/api/mcpAdd to ~/.cursor/mcp.json:
{
"mcpServers": {
"mymenopauserx": {
"url": "https://developer.mymenopauserx.com/api/mcp"
}
}
}What it returns
Read-only. Each tool returns exactly what the public REST API returns — nothing patient-specific, no booking. When a lookup fails, the tool returns a short plain-language message instead of an error body, so it's safe to relay to an end user verbatim.
More
See Using the MCP for worked examples — real customer questions mapped to tool calls — and how to test the server by hand. See the API reference for the underlying REST endpoints. Have a use case this doesn't cover? Talk to partnerships.