openemr-wiki-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_openemr_wikiA | Search the OpenEMR wiki for documentation on any topic. Returns page titles, summaries, and URLs. Falls back to title search automatically if full-text search returns no results. Use this first to find relevant pages before fetching full content. |
| get_openemr_wiki_pageA | Fetch the plain-text content of an OpenEMR wiki page. Optionally fetch a single section by heading name to avoid the 8000-character truncation limit on long pages. |
| get_users_guide_tocA | Fetch the table of contents from the OpenEMR 8.0.0 Users Guide. Use this to orient yourself before fetching a specific section. |
| get_openemr_api_docsA | Fetch developer API documentation from the OpenEMR GitHub repository. Covers the REST and FHIR APIs that are NOT documented on the wiki. Use this for anything related to FHIR, REST endpoints, authentication, or SMART on FHIR. |
| list_wiki_pages_by_categoryA | List all wiki pages in a given category. Use this when search returns no results — browse by topic area instead. Useful categories: 'Developer Guide', 'User Guide', 'Configuration Guide', 'Clinic Work Flow', 'Features', 'Installation', 'Security', 'Frequently Asked Questions', 'Backup', 'User Documentation'. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct role: search (discovery), get_page (content retrieval), get_toc (orientation), get_api_docs (developer reference), and list_by_category (browse fallback). There is mild overlap between search_openemr_wiki and list_wiki_pages_by_category as discovery mechanisms, but descriptions clearly explain when to prefer each.
All tools follow a consistent snake_case verb_noun pattern (search_, get_, get_, get_, list_). The naming is predictable and readable throughout, with no mixing of conventions.
Five tools is well-scoped for a read-only documentation retrieval server, with each tool earning its place (search, fetch, TOC, API docs, browse). No redundant or filler tools.
The surface covers discovery, content fetching, section-level fetching, API docs, and category browsing, which is solid for a documentation server. A minor gap is the lack of a generic way to list a single page's section headings, though the Users Guide TOC partially mitigates this.