Licensing data for AI workflows.
Licensy AI's MCP server gives AI applications structured access to physician and physician assistant licensing data through defined tools — inside controlled workflows, with human review where it matters.
Tools available today.
Look up all licenses for a provider by NPI.
Retrieve status and expiration for a license.
Fetch a preserved screenshot of the official record, where available.
Resolve licensing data for a set of providers in one call.
Disciplinary signals and point-in-time history are in beta.
Add the server to your MCP client.
- Open Settings → Connectors — or go to
claude.ai/customize/connectors. - Click Add custom connector.
- Paste
https://mcp.licensy.ai/mcpand click Add. - Click Connect and sign in in the browser window that opens.
- No API key to copy — you just sign in.
- Add it once in the desktop app or on the web — no terminal, no config files.
- On Team / Enterprise plans, a workspace admin adds it once for everyone.
Using Cursor or another client you configure by file? Add the server URL to your MCP config — it opens a browser to sign in on first use, no API key needed.
{
"mcpServers": {
"licensy": {
"url": "https://mcp.licensy.ai/mcp"
}
}
}For scripts, cron, or clients without a browser, authenticate with your API key instead of signing in.
{
"mcpServers": {
"licensy": {
"url": "https://mcp.licensy.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_LICENSY_API_KEY"
}
}
}
}Copy your key from Settings → API Keys and paste it in place of YOUR_LICENSY_API_KEY. The same key works for the REST API and MCP — IP restrictions apply to the REST API only.
The MCP server is a delivery method for structured licensing data used within defined, reviewed workflows — not autonomous credentialing.
Bring licensing data into your AI workflows.
Licensy AI provides licensing information derived from official public sources. Customers remain responsible for determining how the information is used within their credentialing, compliance, legal, or operational workflows.