campaign_member_delete — Outcomet MCP Tool
campaign_member_delete
(campaign member delete) is one of 107 tools on the
Outcomet
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call campaign_member_delete from your client
- Claude Code Outcomet campaign_member_delete run in your project directory
- Claude Desktop Outcomet campaign_member_delete ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Outcomet campaign_member_delete ~/.cursor/mcp.json
- VS Code Outcomet campaign_member_delete .vscode/mcp.json
- Zed Outcomet campaign_member_delete ~/.config/zed/settings.json
- Windsurf Outcomet campaign_member_delete ~/.codeium/windsurf/mcp_config.json
- Cline Outcomet campaign_member_delete ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Outcomet campaign_member_delete ~/.gemini/settings.json
- Grok Outcomet campaign_member_delete .mcp.json (in your project root)
- ChatGPT Outcomet campaign_member_delete Settings → Connectors → Advanced → Developer mode
- Claude.ai Outcomet campaign_member_delete Settings → Connectors → Add custom connector
- LangChain Outcomet campaign_member_delete pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.outcomet.app/mcpOther tools on this server
- server_status_get
- capability_update
- capability_create
- capability_reparent
- capability_retire
- capability_merge
- capability_link_change
- capability_unlink_change
- capability_link_opportunity
- capability_unlink_opportunity
- capability_search
- capability_get
- capability_list_children
- capability_list_relationships
- feedback_search
- feedback_get
- feedback_create
- campaign_create
- campaign_update
- company_search
- company_get
- contact_search
- contact_get
- contact_custom_fields_list
- campaign_search
- campaign_get
- campaign_list_members
- campaign_member_get
- playbook_search
- playbook_get
- campaign_interaction_list
- company_upsert
- company_create
- company_update
- contact_upsert
- contact_create
- contact_update
- campaign_interaction_create
- campaign_member_update
- campaign_member_create
- campaign_interaction_delete
- campaign_member_transfer
- initiative_link_capability
- initiative_link_change
- initiative_unlink_change
- initiative_link_feedback
- initiative_search
- initiative_get
- initiative_list_feedback
- evidence_search
- feedback_list_evidence
- evidence_get
- initiative_list_relationships
- initiative_create
- initiative_update
- initiative_get_goal_suggestions
- initiative_confirm_goal
- opportunity_search
- opportunity_get
- product_context_get
- strategy_overview_get
- pillar_search
- pillar_upsert
- opportunity_upsert
- bet_search
- bet_get
- bet_upsert
- wardley_map_search
- discovery_workspace_get
- hypothesis_search
- hypothesis_upsert
- experiment_search
- experiment_upsert
- initiative_command
- initiative_unlink_capability
- initiative_learning_promote
- initiative_decision_record
- decision_relationship_link
- decision_work_item_create
- decision_trace_get
- problem_create
- problem_search
- problem_get
- feedback_problem_review_get
- problem_proposal_approve
- problem_proposal_reject
- work_item_search
- work_item_get
- initiative_link_work_item
- initiative_unlink_work_item
- capability_link_work_item
- capability_unlink_work_item
- work_item_link_change
- work_item_unlink_change
- work_item_update
- feedback_update
- feedback_set_status
- feedback_link_change
- feedback_unlink_change
- problem_link_evidence
- problem_unlink_evidence
- change_search
- change_get
- competitor_search
- competitor_get
- competitor_mutate
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.