Zain Ahmed Documentation MCP Server

The three tools are mostly distinct: search_docs is keyword discovery, get_documentation_page fetches a known topic slug, and get_auth_protocol targets the auth contract specifically. The only overlap is that auth.md is itself a documentation page, so an agent could occasionally hesitate between get_documentation_page and get_auth_protocol, but descriptions clarify the intended split.

All names use snake_case with a verb_noun structure, which is predictable and readable. search_docs differs slightly from the get_* pattern used by the retrieval tools, but the naming remains consistent overall.

Three tools are minimal but reasonable for a read-only documentation server: search, fetch a page, and fetch the auth contract. The surface is tightly scoped rather than sprawling, though it sits near the thin edge.

The core documentation workflow is covered: discovery via search, retrieval by slug, and direct access to the auth protocol. Minor gaps include no explicit list/index operation for all topics or sections, though search can serve as a discovery mechanism.