draft_linkedin_message — linkedin buying signals MCP Tool
draft_linkedin_message
(draft linkedin message) 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 draft_linkedin_message from your client
- Claude Code linkedin buying signals draft_linkedin_message run in your project directory
- Claude Desktop linkedin buying signals draft_linkedin_message ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor linkedin buying signals draft_linkedin_message ~/.cursor/mcp.json
- VS Code linkedin buying signals draft_linkedin_message .vscode/mcp.json
- Zed linkedin buying signals draft_linkedin_message ~/.config/zed/settings.json
- Windsurf linkedin buying signals draft_linkedin_message ~/.codeium/windsurf/mcp_config.json
- Cline linkedin buying signals draft_linkedin_message ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI linkedin buying signals draft_linkedin_message ~/.gemini/settings.json
- Grok linkedin buying signals draft_linkedin_message .mcp.json (in your project root)
- ChatGPT linkedin buying signals draft_linkedin_message Settings → Connectors → Advanced → Developer mode
- Claude.ai linkedin buying signals draft_linkedin_message Settings → Connectors → Add custom connector
- LangChain linkedin buying signals draft_linkedin_message 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.