clinicalleader.guide
Read-only MCP registry of published clinical leadership guides and their taxonomy
clinicalleader.guide is an MCP server for learning resources. It runs as a hosted remote server, so there is nothing to install locally.
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
Similar MCP servers
Install
Run in a terminal
claude mcp add --transport http guide-registry https://clinicalleader.guide/mcpAdd to Settings → Connectors → Add custom connector
https://clinicalleader.guide/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"guide-registry": {
"url": "https://clinicalleader.guide/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"guide-registry": {
"type": "http",
"url": "https://clinicalleader.guide/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"guide-registry": {
"serverUrl": "https://clinicalleader.guide/mcp"
}
}
}Add to Grok Bot desktop app → Connect apps → Add a custom connector
https://clinicalleader.guide/mcpEnter a Name (for example "clinicalleader.guide"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin.
Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"guide-registry": {
"type": "http",
"url": "https://clinicalleader.guide/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
About clinicalleader.guide
The Guide Registry is a read-only Model Context Protocol server that exposes the published guides from Clinical Leader Guide, a collection on leading clinical teams, quality and patient safety. According to its registry entry, it provides access to guides, homes, taxonomy and a capability spine, and it requires no authentication.
The server runs over streamable HTTP at the vendor's own endpoint, so an MCP-compatible client can connect to it directly without installing a local package. The website describes its content as organised by subject, with sections on leading teams and organisations and on leading in a specific field, and it lists topics such as standardized protocols and checklists and team communication.
It suits clinical leaders, quality and safety staff, and developers who want an AI assistant to look up guide material from this specific source. Its scope is limited to the published Clinical Leader Guide content.
What it does
- Read-only guide access
- Lets MCP clients read published guides without the ability to write or change content.
- No authentication required
- The registry entry states the server needs no auth, so it can be connected to directly.
- Streamable HTTP transport
- Served at a remote endpoint over streamable HTTP rather than as a local package.
- Subject taxonomy
- Content is organised by subject and includes a taxonomy for browsing the guides.
Good for
- Look up clinical quality and patient safety guidance from a published source
- Find guides on checklists, protocols and hand-offs for a clinical team
- Browse the guide taxonomy to locate material on team communication
- Give an AI assistant read access to Clinical Leader Guide content
clinicalleader.guide FAQ
Does the registry require an account or API key?
No. The registry entry says the server has no auth.
Can the registry modify guides?
No. It is described as read-only.
How do I connect to clinicalleader.guide?
It is a streamable HTTP remote at https://clinicalleader.guide/mcp.
How do I add clinicalleader.guide to Claude Code?
Run this command in your terminal: claude mcp add --transport http guide-registry https://clinicalleader.guide/mcp
What are the best alternatives to clinicalleader.guide?
The closest alternatives to clinicalleader.guide are babyname.guide, Bicycle, churchleader.guide, coachingleader.guide and constructionleader.guide.
Where this comes from
- Description: written from the project's website and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.