read_doc

6 registry entries were observed exposing a tool named read_doc — none of them flagged as a privileged capability.

Spelled read_doc, read-doc in the wild — all one tool for the purposes of this page.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 8,470 of 26,658 scannable entries (32%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

  1. @dasasian/gdocs-mcp
    trust 60/100 · BMCP serverobserved · static extraction
    Treat a Google Doc like a local file: content editing, tracked-changes review, comments, tables.
  2. @merchinary/docs-mcp
    trust 60/100 · BMCP serverobserved · static extraction
    MCP server exposing Merchinary's product knowledge (Bulk Product Editor + Image Editor for Shopify) — search docs, read how-to guides, and d
  3. com.branderux/mcp
    trust 60/100 · BMCP serverobserved · static extraction
    Turns any agent into a full agentic application — branded, interactive screens generated at runtime.
  4. feishu-user-plugin
    trust 60/100 · BMCP serverobserved · static extraction
    Feishu/Lark MCP server + CLI tool. 85 tools, 3 auth layers. Send as user via cookie+protobuf.
  5. io.github.CleanSlice/mcp
    trust 60/100 · BMCP serverobserved · static extraction
    Architecture docs and patterns for NestJS + Nuxt full-stack apps
  6. io.github.deckbase/deckbase-mcp-server
    trust 60/100 · BMCP serverobserved · static extraction
    MCP server for Deckbase - exposes docs, template blocks, and project context

All indexed toolsSearch the registry for read_doc