A
licenseA
qualityD
maintenanceEnables AI agents to browse, search, and fetch documentation from any public Zendesk Help Center via a read-only API.
9
MIT
Jamf Docs MCP Server
Related Servers
Alternatives to Jamf Docs MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to search and read Azure documentation using full-text search and section filtering, with content retrieval from Microsoft's official Azure docs repository.2MIT
- AlicenseBqualityFmaintenanceProvides AI assistants with access to Apple's Human Interface Guidelines and technical API documentation across all Apple platforms (iOS, macOS, watchOS, tvOS, visionOS), enabling unified search of design principles and implementation details.23119 npm21MIT
- AlicenseAqualityDmaintenanceProvides access to Apple's official developer documentation, frameworks, APIs, and WWDC session transcripts across all Apple platforms. It enables AI assistants to search technical guides, sample code, and platform compatibility information using natural language queries.181,171 npm1,385MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to search and fetch documentation content from Adobe Experience League, allowing natural language queries to retrieve Adobe product documentation and articles.-
- AlicenseAqualityDmaintenanceEnables AI agents to search and retrieve jam-nodes documentation, including node info, API references, and guides, via MCP tools without loading everything into context.51MIT
TDQS
A4.4/5.0
Scored across 6 tools
Disambiguation4/5
Each tool occupies a distinct role in the docs workflow: catalogue listing, search, single fetch, batch fetch, TOC browsing, and glossary lookup. The only mild overlap is between jamf_docs_list_products (catalogue of products/publications/filters) and jamf_docs_get_toc (navigation structure), but the descriptions explicitly clarify that one is discovery metadata and the other is document hierarchy. jamf_docs_get_article vs jamf_docs_batch_get_articles is unambiguous given the batch's explicit concurrency/bulk framing.
Naming Consistency4/5
All tools share a clear jamf_docs_ prefix and are snake_case, which is strong. Most follow verb_noun (list_products, get_article, get_toc), but glossary_lookup inverts to noun_verb and batch_get_articles inserts a modifier prefix, so it is not perfectly uniform.
Tool Count5/5
Six tools is well-scoped for a documentation server: discovery, search, retrieval (single and bulk), structure browsing, and glossary each earn their place. No redundant or filler tools are present.
Completeness4/5
The doc lifecycle is well covered: discover products/publications, list versions via list_products or error hints, browse TOC, search, fetch single or batch articles, and look up glossary terms. Minor gaps include no dedicated version-listing or category-browsing operation, but agents can work around these via list_products and the TOC.
Maintenance
ActivityActive
ResponsivenessResponsive