OrchestKit Docs MCP

What OrchestKit Docs MCP does

OrchestKit Docs MCP gives MCP-compatible agents read-only access to OrchestKit documentation through search and documentation retrieval tools. Its documented description centers on full-text search and Markdown fetching, while its exposed Context7-oriented tools can resolve library identifiers and query up-to-date documentation with code examples.

The server requires no authentication. It is intended for agents that need reference information rather than actions that modify repositories, documentation, or external services.

How it works

A typical request begins with resolve-library-id. The tool maps a package or product name to a Context7-compatible identifier such as /org/project or /org/project/version. Results include the candidate's name, description, available code-example count, source reputation, benchmark score, and versions.

After selecting an identifier, the agent calls query-docs to retrieve documentation and examples. If the user supplies a valid Context7 library ID in the query, the resolution step can be skipped. Version-specific requests should use one of the versions returned during resolution.

The resolver is intended to choose a relevant match by considering name similarity, documentation coverage, source reputation, benchmark score, and the request's intent. Ambiguous requests may require clarification. Tool usage is limited to three calls per question for both resolution and documentation querying.

Tools and capabilities

• resolve-library-id: Finds matching libraries and returns Context7-compatible IDs, descriptions, example counts, reputation indicators, benchmark scores, and available versions.
• query-docs: Retrieves current documentation and code examples for a resolved programming library or framework.
• Full-text documentation search: Searches the OrchestKit documentation corpus.
• Markdown retrieval: Fetches documentation in Markdown form.
• Language-aware queries: The documentation query can include a programming language so returned material better matches the user's development setup.
• Read-only access: Supports lookup and retrieval rather than write operations.

Limitations and notes

The Context7 query flow depends on a valid library identifier. Agents should resolve the identifier first unless the user already provides one in /org/project or /org/project/version format. When several candidates match, the resolver selects the best available result using relevance and documentation-quality signals; unclear requests may need clarification before lookup continues.

The server does not require authentication. Its tools are limited to documentation discovery and retrieval, so it is not suitable for modifying OrchestKit content or performing operational actions in a connected project.