remove_list_item — DataMerge MCP MCP Tool Mutating
remove_list_item
(remove list item) is one of 23 tools on the
DataMerge MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call remove_list_item from your client
- Claude Code DataMerge MCP remove_list_item run in your project directory
- Claude Desktop DataMerge MCP remove_list_item ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DataMerge MCP remove_list_item ~/.cursor/mcp.json
- VS Code DataMerge MCP remove_list_item .vscode/mcp.json
- Zed DataMerge MCP remove_list_item ~/.config/zed/settings.json
- Windsurf DataMerge MCP remove_list_item ~/.codeium/windsurf/mcp_config.json
- Cline DataMerge MCP remove_list_item ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DataMerge MCP remove_list_item ~/.gemini/settings.json
- Grok DataMerge MCP remove_list_item .mcp.json (in your project root)
- ChatGPT DataMerge MCP remove_list_item Settings → Connectors → Advanced → Developer mode
- Claude.ai DataMerge MCP remove_list_item Settings → Connectors → Add custom connector
- LangChain DataMerge MCP remove_list_item pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.datamerge.ai
Other tools on this server
- configure_datamerge
- start_company_enrichment
- get_company_enrichment_result
- start_company_enrichment_and_wait
- run_company_enrichment
- run_contact_enrich
- run_contact_search
- get_company
- get_company_hierarchy
- contact_search
- get_contact_search_status
- contact_enrich
- get_contact_enrich_status
- get_contact
- list_lists
- create_list
- get_list_items
- delete_list
- get_credits_balance
- health_check
- contact_search_unenriched
- run_contact_search_unenriched
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.