start_campaign — Nose for Leads MCP Tool Mutating
start_campaign
(start campaign) is one of 11 tools on the
Nose for Leads
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call start_campaign from your client
- Claude Code Nose for Leads start_campaign run in your project directory
- Claude Desktop Nose for Leads start_campaign ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Nose for Leads start_campaign ~/.cursor/mcp.json
- VS Code Nose for Leads start_campaign .vscode/mcp.json
- Zed Nose for Leads start_campaign ~/.config/zed/settings.json
- Windsurf Nose for Leads start_campaign ~/.codeium/windsurf/mcp_config.json
- Cline Nose for Leads start_campaign ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Nose for Leads start_campaign ~/.gemini/settings.json
- Grok Nose for Leads start_campaign .mcp.json (in your project root)
- ChatGPT Nose for Leads start_campaign Settings → Connectors → Advanced → Developer mode
- Claude.ai Nose for Leads start_campaign Settings → Connectors → Add custom connector
- LangChain Nose for Leads start_campaign pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http leads-mcp https://api.noseforleads.com/mcpOther tools on this server
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.