"Documentation for Libraries" matching MCP tools:

• microsoft_docs_fetch

  Microsoft Learn MCP

  Fetch and convert a Microsoft Learn documentation webpage to markdown format. This tool retrieves the latest complete content of Microsoft documentation webpages including Azure, .NET, Microsoft 365, and other Microsoft technologies. ## When to Use This Tool - When search results provide incomplete information or truncated content - When you need complete step-by-step procedures or tutorials - When you need troubleshooting sections, prerequisites, or detailed explanations - When search results reference a specific page that seems highly relevant - For comprehensive guides that require full context ## Usage Pattern Use this tool AFTER microsoft_docs_search when you identify specific high-value pages that need complete content. The search tool gives you an overview; this tool gives you the complete picture. ## URL Requirements - The URL must be a valid HTML documentation webpage from the microsoft.com domain - Binary files (PDF, DOCX, images, etc.) are not supported ## Output Format markdown with headings, code blocks, tables, and links preserved.

  Connector

• migrate_to_propelauth_frontend

  PropelAuth Integration MCP Server

  Returns instructions for migrating to PropelAuth in a frontend framework such as React, JavaScript, TypeScript, or when using Next.js for just the frontend (e.g. client-side rendered). Guidance includes migrating from several auth providers, such as Clerk or Auth0. Each guidance will include documentation from the auth provider and PropelAuth. It is important to follow the instructions carefully to ensure a successful integration. Make sure to use the 'Installation' guidance first. It is important to call every guidance to ensure a successful integration. Do not update a component/hook/etc from the auth provider until you receive guidance about that component/hook/etc. CRITICAL: If the current implementation uses a traditional OAuth/OIDC flow (e.g., via express-openid-connect, passport-auth0, or similar backend-managed session libraries), you MUST select 'OAuth' as the framework, regardless of the frontend library (React/Vue/etc.). Only select 'React' or 'Javascript' if the current implementation uses a frontend-only SDK (like @auth0/auth0-react) or if using fullstack Next.js.

  Connector

• search

  Ferritin — Rust documentation

  Search for items within a crate's documentation, or — without a crate — discover which crate to use.

  Connector

• search_documentation

  JobMojito

  Search ALL JobMojito documentation. This is the single entry point. One call searches both documentation sources in parallel and returns a merged, source-labeled list — you do not need to choose a source or call a separate tool: • "developer" — developer.jobmojito.com: API reference, request/response schemas, tables, webhooks, code examples, integration guides. • "help" — help.jobmojito.com: recruiter, candidate, and administrator product guides (how the platform behaves for end users). Use this whenever you need to understand how a feature, endpoint, field, or workflow works — including before calling an action tool you're unsure about. Then call `get_documentation(url)` with a returned URL to read the full page.

  Connector

• get_doc

  SukukFi

  Return a full SukukFi documentation page as markdown. Call search_docs first to find a slug, or pass a known slug such as "for-capital-providers/risk-considerations".

  Connector

• query_graph

  Gonka Second Opinion (multi-model)

  Search Gonka documentation. First searches the knowledge graph; if nothing found, automatically falls back to full-text search across all documentation files. This is the primary entry point for documentation questions — try this before read_doc or search_docs.

  Connector

• list_libraries

  Supericons

  List the free icon libraries available through the hosted Supericons MCP server. Use this before filtering by library or when a user asks which icon libraries are supported.

  Connector

• get_chat_info

  fast-mcp-telegram

  Load profile and metadata for one user, bot, group, or channel. Success: info dict; forum chats may include topics up to topics_limit. Full documentation: https://github.com/alexeyleshchenko/fast-mcp-telegram/blob/main/docs/Tools-Reference.md

  Connector

• avizo_about

  avizo-mcp

  Product overview of Avizo (avizo.ro): compliance-deadline tracking and alerting for Romanian SMEs — what it tracks, alert channels and cadence, post-expiry escalation, integrations, billing model, GDPR posture. Factual summary; use avizo_plans for pricing details and avizo_docs for user documentation.

  Connector

• search_api_docs

  Soracom Knowledge

  Search SORACOM API documentation, CLI references, and SAM permissions. Use for exact API endpoints, soracom-cli commands, or SAM permission strings. Use search_soracom_docs for service guides, console how-tos, pricing, or IoT recipes. Use get_document on `#/schema/<Name>` links in results to read full API schema fields.

  Connector

• docs_read

  GitHits

  Read a documentation page by page ID. Works for both hosted/crawled docs and repository-backed docs. Pass `start_line` / `end_line` to fetch only a slice when a page is too long — response carries `totalLines` so you can target the next slice. Repo-backed results additionally include exact file follow-up metadata for `code_read`.

  Connector

• ask_site

  agentready-mcp

  Query any website's documentation and get cited, multi-page answers in natural language. Use ask_site when you need: (1) answers that synthesize information across multiple pages of a site, (2) documentation from JS-rendered sites (React, Next.js, Vue SPAs) where web_fetch returns empty or partial HTML, (3) citations linking back to the exact source pages, (4) faster results than fetching and reading individual pages one by one. For sites not yet indexed, ask_site auto-crawls and answers in ~60s — no separate submit_site call needed.

  Connector

• list_docs

  Pine Script

  USE WHEN discovering what Pine Script v6 documentation is available. Returns a categorised list of doc file paths with one-line descriptions. AFTER calling this tool, call get_doc(path) for small files or list_sections(path) then get_section(path, header) for large files (ta.md, strategy.md, collections.md, drawing.md, general.md). Data sourced from bundled Pine Script v6 documentation.

  Connector

• get_doc

  Pine Script

  USE WHEN reading the full content of a Pine Script v6 documentation file. Returns the file content; when limit is set, a header shows the char range and offset to continue reading. AFTER calling this tool, use offset=<end> to continue if the header indicates more content is available. For large files (ta.md, strategy.md, collections.md, drawing.md, general.md), prefer list_sections() + get_section() instead. Data sourced from bundled Pine Script v6 documentation.

  Connector

• resolve-library-id

  xpay✦ DevTools Collection

  Resolves a package/product name to a Context7-compatible library ID and returns matching libraries. You MUST call this function before 'query-docs' 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. 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.

  Connector

• microsoft_docs_fetch

  xpay✦ DevTools Collection

  Fetch and convert a Microsoft Learn documentation webpage to markdown format. This tool retrieves the latest complete content of Microsoft documentation webpages including Azure, .NET, Microsoft 365, and other Microsoft technologies. ## When to Use This Tool - When search results provide incomplete information or truncated content - When you need complete step-by-step procedures or tutorials - When you need troubleshooting sections, prerequisites, or detailed explanations - When search results reference a specific page that seems highly relevant - For comprehensive guides that require full context ## Usage Pattern Use this tool AFTER microsoft_docs_search when you identify specific high-value pages that need complete content. The search tool gives you an overview; this tool gives you the complete picture. ## URL Requirements - The URL must be a valid HTML documentation webpage from the microsoft.com domain - Binary files (PDF, DOCX, images, etc.) are not supported ## Output Format markdown with headings, code blocks, tables, and links preserved.

  Connector

• redact

  concordance

  Strip PII (emails, SSNs, credit cards, IPs, URLs) from text to stable placeholders before you pass it onward; the mapping is returned so YOU reveal replies locally. For true privacy run this on a LOCAL/sovereign engine (the text never leaves your machine) or use the client libraries — the strip belongs at your edge. Deterministic; pair with verify for a receipt.

  Connector

• avizo_docs

  avizo-mcp

  Without arguments: lists every documentation page on avizo.ro/docs (quickstart, alert cadence, hierarchical escalation, SmartBill integration, API reference, troubleshooting) with slug and description. With {slug}: returns that page as markdown — the exact content the site renders. For programmatic integration read {slug: "api-reference"}.

  Connector

• search_honeydew_documentation

  Honeydew AI Documentation

  Search across the Honeydew Documentation knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Honeydew Documentation, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. `head -200 /api-reference/create-customer.mdx`).

  Connector

• get_data_model

  OpenDataModels MCP server

  Retrieve the complete JSON Schema and metadata for a specific Smart Data Model. Use this when the user already knows the model name and wants its full definition, required fields, attribute types, or documentation URL. Example: get_data_model({"model_name": "WeatherObserved", "include_examples": true})

  Connector