MCP App Store
by KeenEthics
Domino Docs icon

Domino Docs MCP Server for Claude

By Domino

Overview

The Domino docs MCP server provides agents with a search tool and browsable interface to the Domino public documentation. It also provides a feedback tool that allows agents to communicate issues they run into where the docs could be improved. This feedback is acted upon automatically once per week to improve the documentation.

How to connect

  1. Claude: Open the Domino Docs listing in the Claude connectors directory and choose Connect. Claude listing Domino Docs exposes 3 tools here.

Tools

query_docs_filesystem_domino

Claude
Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at / that contains ONLY the Domino documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its .mdx path to head or cat — a page at the URL path /some/page lives at /some/page.mdx. To search the docs with exact keyword or regex matches, use rg. To understand the docs structure, use tree or ls. Paths are specific to this site — never guess them. Discover real paths with tree / -L 2, ls /, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use rg -il "keyword" / to find where it is covered. Workflow: Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run --help on any command for usage. Each call is STATELESS: the working directory always resets to / and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with && or pass absolute paths (e.g., cd /some-directory && ls or ls /some-directory). Do NOT assume that cd in one call affects the next call. Examples (replace the placeholder paths with real ones from tree or search): - tree / -L 2 — see the top-level directory layout - rg -il "rate limit" / — find all files mentioning "rate limit" - rg -C 3 "apiKey" /some-directory/ — show matches with 3 lines of context around each hit - head -80 /some/page.mdx — read the top 80 lines of a specific page - head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx — read multiple pages in one call - cat /some/page.mdx — read a full page when you need everything - cat /openapi/api-specs/cloud/public-api.json | jq '.paths | keys' — list OpenAPI endpoints OpenAPI specs for this site are mounted at: /openapi/api-specs/cloud/public-api.json, /openapi/api-specs/6.3/public-api.json, /openapi/api-specs/cloud/workspace-file-audit-trail-api.json, /openapi/api-specs/6.3/workspace-file-audit-trail-api.json, /openapi/api-specs/cloud/flyte-native-api.json, /openapi/api-specs/cloud/flyte-extensions-api.json, /openapi/api-specs/6.3/flyte-native-api.json, /openapi/api-specs/6.3/flyte-extensions-api.json. Use them to answer questions about endpoints, request/response schemas, parameters, and authentication. Output is truncated to 30KB per call. Prefer targeted rg -C or head -N over broad cat on large files. To read only the relevant sections of a large file, use rg -C 3 "pattern" /path/file.mdx. Batch multiple file reads into a single head or cat call whenever possible. When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the .mdx extension. For example, /some/page.mdx becomes /some/page.

search_domino

Claude
Search across the Domino knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Domino, 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. a result at /some/page is read with head -200 /some/page.mdx).

submit_feedback

Claude
Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant.

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/domino-docs"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/domino-docs)