Beta — This feature is subject to change. The MCP specification and our implementation may evolve.
The Endpoint Directory MCP server enables AI assistants to search and validate health insurance and healthcare provider endpoints programmatically. Unlike the patient data MCP server, the directory server is public and does not require authentication.
Use it to build payer or provider selection flows, validate endpoint support for specific plan types, or let AI agents help users find their health insurance company or healthcare provider.
POST https://api.flexpa.com/mcp/directory
No authentication required. The directory server is read-only and exposes only public endpoint metadata.
Add the directory as a custom connector:
https://api.flexpa.com/mcp/directory
No authorization flow is required — the directory is public.
claude mcp add flexpa-directory \ --transport http \ https://api.flexpa.com/mcp/directory
The directory server provides four tools for discovering and validating endpoints.
Search for health insurance payers and healthcare providers by name, brand, acronym, or state.
Returns up to 10 matching endpoints with organization details, connection status, and supported lines of business.
Search query — payer name, provider name, brand, acronym, or state. Examples: "Aetna", "BCBS Illinois", "Mayo Clinic"
"Aetna"
"BCBS Illinois"
"Mayo Clinic"
Blue Cross Blue Shield is a federation of independent companies per state. If a user says "BCBS", the tool's instructions guide the AI to ask which state before searching.
{ "name": "search_endpoints", "arguments": { "query": "Aetna" } }
Get detailed information about a specific endpoint, including supported lines of business with authentication flow info, connection status, and features like inactive member access and 2FA requirements.
The endpoint ID from search_endpoints results
search_endpoints
{ "name": "get_endpoint_details", "arguments": { "endpointId": "abc-123" } }
Validate whether an endpoint supports a specific line of business (plan type) and determine the correct authentication flow.
Lines of business:
medicaid
medicare_advantage
chip
aca_on_exchange
aca_off_exchange
employer
original_medicare
veterans
The endpoint ID from search_endpoints
One of the line of business types listed above
{ "name": "check_lob_support", "arguments": { "endpointId": "abc-123", "lineOfBusiness": "employer" } }
The response includes pass/fail validation, the authentication flow type (OAuth or Credentials), and recommended next steps.
List all endpoints in the directory, optionally filtered by status or line of business.
Filter by connection status. Default: CONNECTED
CONNECTED
Filter by line of business support
Maximum results to return (default 50, max 100)
{ "name": "list_endpoints", "arguments": { "lobType": "medicaid", "limit": 20 } }
The directory server includes three prompts that guide AI assistants through common workflows.
find_insurance
find_provider
explore_directory
{ "method": "prompts/get", "params": { "name": "find_insurance" } }
AI-powered endpoint selection — Let an AI assistant guide users through finding their health insurance company (find_insurance) or healthcare provider (find_provider). The insurance prompt handles BCBS state disambiguation, Medicaid regional plans, and plan type identification automatically.
Endpoint validation — Before initiating a patient authorization, validate that the endpoint supports the user's plan type and determine whether to use the OAuth or Credentials flow.
Directory exploration — Build tools that help operations teams browse available payer and provider endpoints, filter by line of business, and understand coverage gaps.