← All integrations

Needle MCP server

23 operations0 webhooks

Manage Needle leads and their LinkedIn and Instagram identities, run campaigns and enroll or stop leads, maintain suppression lists, search places and preview AI-composed messages.

Try Needle with your agent

Connect Needle, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Needle on my account, then run one read-only example and show me the result.

Runs once, when you ask

Needle tools and triggers

Tools are what your agent can do in Needle through Corsair's MCP server. Triggers are the Needle events a routine can start from.

Campaigns

  • CreateWrite

    Create a campaign in draft from a sequence graph; it contacts nobody until campaigns.update sets it active

    campaigns.create

  • DeleteDestructive

    Archive a campaign: it stops sending and leaves the active list, and the record is kept

    campaigns.delete

  • EnrollDestructive

    Enroll up to 500 leads at once, with one result per lead so a batch can partly succeed; an enrolled lead can be contacted

    campaigns.enroll

  • GetRead-only

    Read one campaign, including its sequence graph and status

    campaigns.get

  • LeadsRead-only

    Page through the leads enrolled in a campaign with their status

    campaigns.leads

  • ListRead-only

    Page through campaigns, optionally filtered by status

    campaigns.list

  • StatsRead-only

    Read a campaign’s progress and funnel: invites, messages, replies, and why leads were skipped

    campaigns.stats

  • Stop LeadsWrite

    Stop leads in a campaign so no further step reaches them, keeping them in the list

    campaigns.stopLeads

  • UpdateDestructive

    Rename a campaign, replace its graph, or set active to start sending and paused to halt it; going active begins contact and cannot be undone

    campaigns.update

Leads

  • CreateWrite

    Create a lead with a LinkedIn or Instagram identity; a duplicate identity is refused with 409, so use leads.upsert to merge instead

    leads.create

  • DeleteDestructive

    Delete a lead and its identities permanently; there is no restore call

    leads.delete

  • GetRead-only

    Read one lead by id, with its identities and live enrollment

    leads.get

Connect Needle to Claude, ChatGPT or Cursor

  1. 1

    Connect Needle in Corsair

    Add your Needle API key once in Corsair. Corsair stores the credential encrypted and makes the Needle API calls for your agent, so it never goes into a prompt or a config file. Connect Needle

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Needle. On a ChatGPT personal plan, connect Needle here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Needle's read and write operations run right away and its 5 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/needle, add the Needle plugin, and connect with an API key. Then call methods like corsair.needle.api.account.me() from your app. Corsair keeps each tenant isolated.

Yes. Needle requires an API key from your Needle account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Needle, GitHub, Notion, Stripe, and the rest. Trigger Needle from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for manage Needle leads and their LinkedIn and Instagram identities, run campaigns and enroll or stop leads, maintain suppression lists, search places and preview AI-composed messages. Common builds include sync jobs, admin tooling, and agents that call Needle APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Needle API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/needle in the open repo. When Needle ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Needle data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Needle data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Needle on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 5 destructive Needle operations. You can change a link's mode at hub.corsair.dev/me.