MCP server for LeadDelta — manage LinkedIn connections and CRM data via AI assistants.
Connect your AI assistant to LeadDelta — the LinkedIn CRM — and manage your network directly from Cursor, Claude, or any MCP-compatible client. ------|-------------| | Search and filter your LinkedIn connections by name, company, job title, location, or headline | | Retrieve your full list of LeadDelta connections | Open Cursor Settings → MCP and add a new server, or edit directly: Where to find…
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Connect your AI assistant to LeadDelta — the LinkedIn CRM — and manage your network directly from Cursor, Claude, or any MCP-compatible client. ------|-------------| | Search and filter your LinkedIn connections by name, company, job title, location, or headline | | Retrieve your full list of LeadDelta connections | Open Cursor Settings → MCP and add a new server, or edit directly: Where to find your API key: Log in to app.leaddelta.com → Integrations → API Key. Once connected, you can ask your…
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.