Skip to main content
Glama
esola-thomas

Documentation MCP Server

by esola-thomas

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DOCS_ROOTYesDocumentation root directory (required)
LOG_LEVELNoLogging level (default: INFO)INFO
MCP_DOCS_WEB_HOSTNoWeb server host (default: 127.0.0.1)127.0.0.1
MCP_DOCS_WEB_PORTNoWeb server port (default: 8123)8123
MCP_DOCS_CACHE_TTLNoCache TTL in seconds (default: 3600)3600
MCP_DOCS_SEARCH_LIMITNoMaximum search results (default: 10)10
MCP_DOCS_OPENAPI_SPECSNoComma-separated OpenAPI spec paths
MCP_DOCS_ENABLE_WEB_SERVERNoEnable/disable web server (default: true)true

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

CapabilityDetails
tools
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_documentationA

Search documentation with full-text search. Returns results with hierarchical context (breadcrumbs).

navigate_toA

Navigate to a specific URI in the documentation hierarchy. Returns navigation context with parent, children, and breadcrumbs.

get_table_of_contentsB

Get the complete documentation hierarchy as a table of contents tree.

search_by_tagsC

Search documentation by metadata tags and category.

get_documentA

Get full content and metadata for a specific document by URI.

get_all_tagsA

Get a list of all unique tags defined across the documentation. Optionally filter by category and include document counts per tag.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Documentation RootRoot of documentation hierarchy
your-docs-mcp# your-docs-mcp
Building a Hierarchical Documentation MCP: Complete Implementation Guide# Building a Hierarchical Documentation MCP: Complete Implementation Guide
your-docs-mcp# your-docs-mcp
Azure DevOps Pipeline Templates# Azure DevOps Pipeline Templates
CI/CD Pipeline Integration# CI/CD Pipeline Integration
Documentation Skills Plugin# Documentation Skills Plugin
Documentation Scripts# Documentation Scripts
your-docs-server# your-docs-server
Create Documentation File# Create Documentation File
Validate Documentation# Validate Documentation
Search Documentation# Search Documentation
Fix Documentation Frontmatter# Fix Documentation Frontmatter
Generate Table of Contents# Generate Table of Contents
Preview Documentation Structure# Preview Documentation Structure
Quick Documentation Lint# Quick Documentation Lint
Generate Documentation Template# Generate Documentation Template
Contributing Guide# Contributing Guide
Testing Guide# Testing Guide
CLI Commands Reference# CLI Commands Reference
Getting Started Guide# Getting Started with Hierarchical Documentation MCP
REST API Reference# REST API Reference
Architecture Overview# Architecture Overview
MCP Protocol Integration# MCP Protocol Integration
Vector Database Integration# Vector Database Integration
Configuration Guide# Configuration Guide
Installation Guide# Installation Guide
Authentication and Security# Authentication and Security

TDQS

A3.5/5.0

Scored across 6 tools

Disambiguation4/5

Most tools are clearly distinct: search_documentation is full-text, search_by_tags is metadata-based, get_document retrieves content, and navigation tools handle hierarchy. There is slight overlap between search_documentation and search_by_tags, but the descriptions clarify the different search modes.

Naming Consistency4/5

Tool names consistently use verb_noun pattern (search_documentation, navigate_to, get_table_of_contents, get_document, get_all_tags). search_by_tags follows the pattern, though 'navigate_to' is slightly less descriptive than the others but still consistent in style.

Tool Count5/5

Six tools is well-scoped for a documentation server, covering search, navigation, and metadata retrieval without unnecessary redundancy. Each tool serves a distinct purpose in the documentation workflow.

Completeness4/5

The surface covers core documentation needs: full-text search, tag search, navigation, TOC, and document retrieval. Minor gaps include no obvious way to get related documents or search within a specific subtree, but the core workflows are complete.

Maintenance

ActivityInactive
ResponsivenessUnresponsive