Docs MCP

This site is also an MCP server. Connect it to your AI tool and the tool can search these pages, read any of them in full, and read the OpenAPI document — so it answers from the current documentation rather than from memory.

https://build.practicehub.io/mcp

This is the documentation server, not the clinic. It is public, needs no login, and knows only what is published on this site. It cannot see any clinic’s data. Connecting an assistant to a clinic’s own patients, diary and invoices is the PracticeHub MCP server on the clinic’s domain, which a team member connects with OAuth.

What the tool gets

Tool	What it does
`search_practice_hub_api`	Full-text search across the site; returns snippets with titles and links
`query_docs_filesystem_practice_hub_api`	A read-only virtual filesystem of every page and the OpenAPI document (`/openapi/openapi.json`), queried with `rg`, `tree`, `ls`, `cat`, `head`, `jq`
`submit_feedback`	Reports a page that is wrong, outdated or unclear to the docs team

It also serves the skill file as an MCP resource, so an agent connected this way learns how to use the API, not just where the pages are.

Connect it

claude mcp add --transport http practicehub-docs https://build.practicehub.io/mcp

Add --scope user to make it available in every project. Check it with claude mcp list.

Open Settings → Connectors (web or desktop) and click Add custom connector.
Name it PracticeHub docs and enter https://build.practicehub.io/mcp.
Click Add. No login is needed.
In a conversation, open the attachments menu (the plus icon) and enable the connector.

Open Settings → Connectors and enable Developer mode under Advanced if it is not already on.
Click Create, name it PracticeHub docs, enter https://build.practicehub.io/mcp and choose No authentication.
Enable it in a chat from the tools menu.

Add to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "practicehub-docs": {
      "url": "https://build.practicehub.io/mcp"
    }
  }
}

Add to .vscode/mcp.json in the workspace (or run MCP: Add Server from the command palette):

{
  "servers": {
    "practicehub-docs": {
      "type": "http",
      "url": "https://build.practicehub.io/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "practicehub-docs": {
      "serverUrl": "https://build.practicehub.io/mcp"
    }
  }
}

Streamable HTTP, no authentication. Point the client at https://build.practicehub.io/mcp, or let it discover the server from https://build.practicehub.io/.well-known/mcp.

curl -X POST https://build.practicehub.io/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Skill file

A skill file is a capability summary written for agents: what they can do with the API, what inputs it needs and what rules apply. Ours is at https://build.practicehub.io/skill.md, and agents connected to the MCP server above get it automatically as a resource. To install it into an agent that isn’t connected:

npx skills add https://build.practicehub.io

Page index for LLMs

https://build.practicehub.io/llms.txt lists every page with a one-line description, and https://build.practicehub.io/llms-full.txt is the whole site as one Markdown file. Any page is available as Markdown by adding .md to its URL.

Want an assistant that works inside a clinic — its patients, diary and invoices — rather than one that reads these docs? That is the PracticeHub MCP server, connected by a team member with OAuth.

Getting started

Concepts

Working with the API

Ship it

Resource guides

Importing your data

What the tool gets

Connect it

Skill file

Page index for LLMs

​What the tool gets

​Connect it

​Skill file

​Page index for LLMs

What the tool gets

Connect it

Skill file

Page index for LLMs