document-a-recording — Easy Scribe MCP Prompt
document-a-recording
is one of 1 prompt on the
Easy Scribe
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke document-a-recording from your client
- Claude Code Easy Scribe Prompt/document-a-recording run in your project directory
- Claude Desktop Easy Scribe Prompt/document-a-recording ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Easy Scribe Prompt/document-a-recording ~/.cursor/mcp.json
- VS Code Easy Scribe Prompt/document-a-recording .vscode/mcp.json
- Zed Easy Scribe Prompt/document-a-recording ~/.config/zed/settings.json
- Windsurf Easy Scribe Prompt/document-a-recording ~/.codeium/windsurf/mcp_config.json
- Cline Easy Scribe Prompt/document-a-recording ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Easy Scribe Prompt/document-a-recording ~/.gemini/settings.json
- Grok Easy Scribe Prompt/document-a-recording .mcp.json (in your project root)
- ChatGPT Easy Scribe Prompt/document-a-recording Settings → Connectors → Advanced → Developer mode
- Claude.ai Easy Scribe Prompt/document-a-recording Settings → Connectors → Add custom connector
- LangChain Easy Scribe Prompt/document-a-recording pip install langchain-mcp-adapters
Easy Scribe also offers 1 resource — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 11 November 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.