delete_document — Antevo Mandates MCP Tool Mutating
delete_document
(delete document) is one of 24 tools on the
Antevo Mandates
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call delete_document from your client
- Claude Code Antevo Mandates delete_document run in your project directory
- Claude Desktop Antevo Mandates delete_document ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Antevo Mandates delete_document ~/.cursor/mcp.json
- VS Code Antevo Mandates delete_document .vscode/mcp.json
- Zed Antevo Mandates delete_document ~/.config/zed/settings.json
- Windsurf Antevo Mandates delete_document ~/.codeium/windsurf/mcp_config.json
- Cline Antevo Mandates delete_document ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Antevo Mandates delete_document ~/.gemini/settings.json
- Grok Antevo Mandates delete_document .mcp.json (in your project root)
- ChatGPT Antevo Mandates delete_document Settings → Connectors → Advanced → Developer mode
- Claude.ai Antevo Mandates delete_document Settings → Connectors → Add custom connector
- LangChain Antevo Mandates delete_document pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mandates https://api.antevo.ch/mcp/mandates/mcpOther tools on this server
- get_succession_scan
- generate_meeting_brief
- list_documents
- get_document_detail
- get_eam_clients
- get_client_dossier
- get_client_reviews_due
- get_client_team
- create_eam_client
- update_eam_client
- convert_prospect
- complete_review
- assign_team_member
- get_client_goals
- create_client_goal
- update_client_goal
- create_share_link
- upload_document
- update_document
- extract_document_data
- get_email_messages
- get_email_detail
- link_email_to_client
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.