create_custom_signal — linkedin buying signals MCP Tool Mutating
create_custom_signal
(create custom signal) is one of 15 tools on the
linkedin buying signals
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call create_custom_signal from your client
- Claude Code linkedin buying signals create_custom_signal run in your project directory
- Claude Desktop linkedin buying signals create_custom_signal ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor linkedin buying signals create_custom_signal ~/.cursor/mcp.json
- VS Code linkedin buying signals create_custom_signal .vscode/mcp.json
- Zed linkedin buying signals create_custom_signal ~/.config/zed/settings.json
- Windsurf linkedin buying signals create_custom_signal ~/.codeium/windsurf/mcp_config.json
- Cline linkedin buying signals create_custom_signal ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI linkedin buying signals create_custom_signal ~/.gemini/settings.json
- Grok linkedin buying signals create_custom_signal .mcp.json (in your project root)
- ChatGPT linkedin buying signals create_custom_signal Settings → Connectors → Advanced → Developer mode
- Claude.ai linkedin buying signals create_custom_signal Settings → Connectors → Add custom connector
- LangChain linkedin buying signals create_custom_signal pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http linkedin-buying-signals https://www.getcleed.com/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 25 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.