OpenTelemetry Documentation MCP Server

Fetch and convert a OpenTelemetry documentation page to markdown format.

Usage

This tool retrieves the content of a OpenTelemetry documentation page and converts it to markdown format. For long documents, you can make multiple calls with different start_index values to retrieve the entire content in chunks.

URL Requirements

• Must be from the opentelemetry.io domain

• Must be a documentation page

Example URLs

• https://opentelemetry.io/docs/concepts/observability-primer/

• https://opentelemetry.io/docs/instrumentation/

• https://opentelemetry.io/docs/collector/

Output Format

The output is formatted as markdown text with:

• Preserved headings and structure

• Code blocks for examples

• Lists and tables converted to markdown format

Handling Long Documents

If the response indicates the document was truncated, you have several options:

1. Continue Reading: Make another call with start_index set to the end of the previous response

2. Stop Early: For very long documents (>30,000 characters), if you've already found the specific information needed, you can stop reading

Args: ctx: MCP context for logging and error handling url: URL of the OpenTelemetry documentation page to read max_length: Maximum number of characters to return start_index: On return output starting at this character index

Returns: Markdown content of the OpenTelemetry documentation

Search OpenTelemetry documentation using Google Custom Search.

Usage

This tool searches across OpenTelemetry documentation for pages matching your search phrase. Use it to find relevant documentation when you don't have a specific URL.

Search Tips

• Use specific technical terms rather than general phrases

• Include OpenTelemetry concepts to narrow results (e.g., "tracing instrumentation" instead of just "tracing")

• Use quotes for exact phrase matching (e.g., "SDK configuration")

• Include abbreviations and alternative terms to improve results (e.g., "OTEL collector")

API Limits

The search uses Google's Custom Search API which has usage limits:

• Free tier: 100 queries per day

• Results are limited to 10 per page

Result Interpretation

Each result includes:

• rank_order: The relevance ranking (lower is more relevant)

• url: The documentation page URL

• title: The page title

• context: A brief excerpt or summary (if available)

Args: ctx: MCP context for logging and error handling search_phrase: Search phrase to use limit: Maximum number of results to return (will be capped at 10 due to API limitations)

Returns: List of search results with URLs, titles, and context snippets