oci-documentation-mcp-server

Features

• Read Documentation: Fetch and convert OCI documentation pages to markdown format.
• Search Documentation: Search OCI documentation using a search engine.

Tools

1. search_documentation

   Search OCI documentation using the OCI Documentation Search API.

   ## Usage
   
   This tool searches across all OCI 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 service names to narrow results (e.g., "OCI Object Storage bucket versioning" instead of just "versioning")
   - Use quotes for exact phrase matching (e.g., "Using Instance Configurations and Instance Pools")
   - Include abbreviations and alternative terms to improve results
   
   ## Result Interpretation
   
   Each result includes:
   - score: The relevance score (higher is more relevant)
   - url: The documentation page URL
   - description: A brief excerpt or summary
   - body: Related text snippets
   
   Args:
       ctx: MCP context for logging and error handling
       search_phrase: Search phrase to use
       limit: Maximum number of results to return
   
   Returns:
       List of search results with URLs, titles, and context snippets
   

2. read_documentation

   Fetch and convert an OCI documentation page to markdown format.

   ## Usage
   
   This tool retrieves the content of an AWS 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 https://docs.oracle.com/ domain
   - Must end with .html or .htm
   
   ## Example URLs
   
   - https://docs.oracle.com/en-us/iaas/Content/Object/Concepts/objectstorageoverview.htm
   - https://docs.oracle.com/en-us/iaas/Content/Compute/References/bestpracticescompute.htm
   
   ## 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 AWS 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 AWS documentation