doc_read — meeting notes transcript summary MCP Tool
doc_read
(doc read) is one of 14 tools on the
meeting notes transcript summary
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call doc_read from your client
- Claude Code meeting notes transcript summary doc_read run in your project directory
- Claude Desktop meeting notes transcript summary doc_read ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor meeting notes transcript summary doc_read ~/.cursor/mcp.json
- VS Code meeting notes transcript summary doc_read .vscode/mcp.json
- Zed meeting notes transcript summary doc_read ~/.config/zed/settings.json
- Windsurf meeting notes transcript summary doc_read ~/.codeium/windsurf/mcp_config.json
- Cline meeting notes transcript summary doc_read ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI meeting notes transcript summary doc_read ~/.gemini/settings.json
- Grok meeting notes transcript summary doc_read .mcp.json (in your project root)
- ChatGPT meeting notes transcript summary doc_read Settings → Connectors → Advanced → Developer mode
- Claude.ai meeting notes transcript summary doc_read Settings → Connectors → Add custom connector
- LangChain meeting notes transcript summary doc_read pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http meeting-notes-transcript-summary https://mcp.zovo.one/mcp/meeting-notes-transcript-summaryOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.