Nuora / Requested page
Nuora is waiting for the requested page to respond.
Agentic access
Connect Nuora to the assistant you already use. Explore services, prepare the next step and keep consent visible at every stage.
Connect your assistant
Both paths ask you to review the connection. Nothing is silently installed or approved on your behalf.
Capabilities
Nuora separates public information from account access, so you can start exploring before you decide what to share.
Public information
Your explicit consent
OAuth scope by scope
How access works
Use the guided setup for Claude or ChatGPT. Every connection starts with you reviewing the endpoint and permissions.
OAuth asks for the access needed for each action. You can revoke consent later from the connected account.
Your assistant can help with the admin around care; clinical decisions and prescribing remain with registered pharmacists.
Safety & consent
Nuora only uses the access you authorise. Patient actions are audited, consent can be withdrawn, and every prescribing decision stays with a GPhC-registered pharmacist.
Developers
For Codex, Claude Code and other MCP clients, use the transport endpoint directly and keep your key in the client’s secret store.
{
"mcpServers": {
"nuora": {
"url": "https://sssanglcqfnciyipjngx.supabase.co/functions/v1/mcp-server",
"headers": {
"X-Nuora-API-Key": "nuora_pk_..."
}
}
}
}Register for a key via POST https://app.nuorahealth.com/api/v1/auth/register.
openapi.yamlFull REST contractagents.jsonCanonical provider and service factsagent.jsonA2A agent cardmcp/server.jsonMCP server metadataoauth-authorization-serverOAuth server discoveryllms.txtMachine-readable site map for agentsQuestions about integrating? Email support@nuorahealth.com.