# OrchestKit Docs MCP [Health: Active]

**Category:** 🔎 Search & Data Extraction  
**Repository:** https://github.com/yonatangross/orchestkit  
**GitHub Stars:** 298  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/orchestkit-docs-mcp

## Description
Read-only MCP server for the OrchestKit docs: full-text search + Markdown fetch. No auth.

## Tools
Capabilities this server exposes over MCP:

- **resolve-library-id** — Resolves a package/product name to a Context7-compatible library ID and returns matching libraries.

You MUST call this function before 'Query Documentation' tool to obtain a valid Context7-compatible library ID UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query.

Each result includes:
- Library ID: Context7-compatible identifier (format: /org/project)
- Name: Library or package name
- Description: Short summary
- Code Snippets: Number of available code examples
- Source Reputation: Authority indicator (High, Medium, Low, or Unknown)
- Benchmark Score: Quality indicator (100 is the highest score)
- Versions: List of versions if available. Use one of those versions if the user provides a version in their query. The format of the version is /org/project/version.

For best results, select libraries based on name match, source reputation, snippet coverage, benchmark score, and relevance to your use case.

Selection Process:
1. Analyze the query to understand what library/package the user is looking for
2. Return the most relevant match based on:
- Name similarity to the query (exact matches prioritized)
- Description relevance to the query's intent
- Documentation coverage (prioritize libraries with higher Code Snippet counts)
- Source reputation (consider libraries with High or Medium reputation more authoritative)
- Benchmark Score: Quality indicator (100 is the highest score)

Response Format:
- Return the selected library ID in a clearly marked section
- Provide a brief explanation for why this library was chosen
- If multiple good matches exist, acknowledge this but proceed with the most relevant one
- If no good matches exist, clearly state this and suggest query refinements

For ambiguous queries, request clarification before proceeding with a best-guess match.

IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best result you have.
- **query-docs** — Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework.

You must call 'Resolve Context7 Library ID' tool first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query.

Do not call this tool more than 3 times per question.

If you know the programming language the user is working in, pass it as `language` so the results match their setup.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/orchestkit-docs-mcp/readme_