droplink_delete_document — Ouro Tools MCP Tool
droplink_delete_document
(droplink delete document) is one of 19 tools on the
Ouro Tools
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call droplink_delete_document from your client
- Claude Code Ouro Tools droplink_delete_document run in your project directory
- Claude Desktop Ouro Tools droplink_delete_document ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Ouro Tools droplink_delete_document ~/.cursor/mcp.json
- VS Code Ouro Tools droplink_delete_document .vscode/mcp.json
- Zed Ouro Tools droplink_delete_document ~/.config/zed/settings.json
- Windsurf Ouro Tools droplink_delete_document ~/.codeium/windsurf/mcp_config.json
- Cline Ouro Tools droplink_delete_document ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Ouro Tools droplink_delete_document ~/.gemini/settings.json
- Grok Ouro Tools droplink_delete_document .mcp.json (in your project root)
- ChatGPT Ouro Tools droplink_delete_document Settings → Connectors → Advanced → Developer mode
- Claude.ai Ouro Tools droplink_delete_document Settings → Connectors → Add custom connector
- LangChain Ouro Tools droplink_delete_document pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http ouro-tools https://ouro.tools/mcpOther tools on this server
- droplink_publish_document
- droplink_read_document
- hookbox_create_inbox
- hookbox_read_inbox
- hookbox_delete_inbox
- chartlink_create_chart
- chartlink_get_chart
- cleanread_read_page
- sourcecheck_check_sources
- printkit_create_pdf
- tablelift_extract_tables
- collect_create_form
- collect_read_form
- collect_submit_response
- collect_read_responses
- collect_close_form
- collect_delete_form
- feedform_normalize_feed
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.