DEV Community

appierun
appierun

Posted on

Track LinkedIn Profiles and Pull Leads Into Claude or Cursor

#mcp #linkedin #claude #sales

You can keep a LinkedIn watch list and work its leads from your AI client with three MCP tool calls: set_linkedin_profile to add a profile, get_linkedin_profiles to check the list, and list_linkedin_leads to see the people who engaged, with email and phone when a lookup has found them.

Disclosure: Appie.run publishes this post, and the MCP server below is ours. Other LinkedIn MCP servers exist, and our LinkedIn MCP servers explainer compares the kinds you'll find. This walkthrough covers Appie's only.

Who this is for

  • GTM engineers and RevOps people who already live in Claude Code, Cursor or Codex.
  • Outbound agencies watching customers, partners, competitors' founders or industry voices.
  • Teams moving off Trigify, whose access ended on 22 October 2026 for most customers. We have a separate Trigify alternatives piece.

Step 1: Key and server

In Appie, open your project and choose API in the sidebar. A project admin generates the esk_ key. Set it once in your shell:

export APPIE_API_KEY=esk_your_key_here
Enter fullscreen mode Exit fullscreen mode

The server is https://appie.run/mcp, and it accepts Authorization: Bearer esk_… or X-Api-Key: esk_….

Claude Code:

claude mcp add --transport http appie https://appie.run/mcp \
  --header "Authorization: Bearer $APPIE_API_KEY"
Enter fullscreen mode Exit fullscreen mode

Codex CLI:

codex mcp add appie --url https://appie.run/mcp --bearer-token-env-var APPIE_API_KEY
Enter fullscreen mode Exit fullscreen mode

Cursor and other clients (config from the Appie docs):

{
  "mcpServers": {
    "appie": {
      "url": "https://appie.run/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

With a valid key, claude mcp list should show the server as connected. A 401 means the key is wrong or revoked. The Reddit MCP walkthrough covers scopes, .mcp.json and troubleshooting in more detail.

Step 2: Add the profiles you want to watch

set_linkedin_profile adds or updates one profile. profile_url is required, and tracking_enabled defaults to true.

{
  "profile_url": "https://www.linkedin.com/in/example"
}
Enter fullscreen mode Exit fullscreen mode

To pause a profile without removing it:

{
  "profile_url": "https://www.linkedin.com/in/example",
  "tracking_enabled": false
}
Enter fullscreen mode Exit fullscreen mode

Saving a profile doesn't spend credits. In the docs' words, "the existing schedule runs the scan, which costs 30 credits." The docs don't say how often that schedule runs, so check the project settings in the app before you add a long list.

Step 3: Check your watch list

get_linkedin_profiles lists the profiles the project tracks. It takes no required arguments and doesn't spend credits. Ask your agent to show it as a table with tracking status, so you can spot anything you paused by mistake.

Step 4: List leads by profile

Leads are the people who engage with the profiles you track. list_linkedin_leads takes an optional limit (default 20, maximum 50) and an optional tracked_profile_id, which you get from Step 3.

{
  "tracked_profile_id": "PROFILE_ID_FROM_STEP_3",
  "limit": 50
}
Enter fullscreen mode Exit fullscreen mode

Each lead includes email and phone when a lookup has found them. Listing is free. The lookup that fills email and phone costs 5 credits per lead.

Illustrative shape of one lead (not real output; only email and phone are field names the docs confirm):

lead: Example Person, engaged with https://www.linkedin.com/in/example
email: person@example.com
phone: (empty, no lookup result)
Enter fullscreen mode Exit fullscreen mode

What the docs don't cover: whether the email lookup runs automatically or has to be triggered (no lookup tool is listed in the MCP), whether ICP scores come back over MCP, and which other fields are returned. Run the tool once and read the response before you build on it.

Step 5: Do something useful with them

Two common routes:

  1. Keep it in your own stack. Ask your agent to turn the leads with an email into a CSV or rows for your sheet or CRM.
  2. Stay inside Appie. The app groups leads by source profile with new, emailed and contacted counts, scores them against project-level ICP weights, shows posts from tracked profiles next to the people, and can hand a lead into a Journeys sequence once an email is found. Appie's page puts it as "no surprise sends from a profile sync": you choose who gets contacted.

The MCP has no messaging, connection-request or posting tools. Your agent can read and list; a person decides who to contact and what to say. For the outreach side, see From Likes to Replies: How to Turn LinkedIn Engagement Into Leads With Warm Outreach.

If you're writing first emails by hand, two free Appie tools help:

  • AI Email Response Generator: paste an email, choose a language and tone, and get a draft with subject, greeting, body and sign-off. Review it before you send.
  • Email Signature Generator: builds an HTML signature in your browser for Gmail, Outlook or Apple Mail.

Prompts to paste

  • "Add these five LinkedIn profile URLs to Appie and confirm tracking is on for each: …"
  • "List my tracked LinkedIn profiles as a table with their IDs and tracking status."
  • "Show leads from tracked profile PROFILE_ID that have an email, as a table. Leave out anyone without one."
  • "Turn those leads into CSV rows with name, email and source profile so I can import them."

What it costs

  • Save or update a profile (set_linkedin_profile): Credits: 0
  • List profiles (get_linkedin_profiles): Credits: 0
  • List leads (list_linkedin_leads): Credits: 0
  • Scheduled profile scan: Credits: 30 per profile
  • Lead email lookup: Credits: 5 per lead

Illustrative example: 5 tracked profiles cost 150 credits per scheduled scan, and 40 email lookups cost 200 credits. That's 350 credits, inside the Free plan's 500 for a single run. How many scans happen in a month depends on the schedule, so work out your monthly number from that.

Plans (appie.run/pricing, as of 20 Oct 2026): Free is $0 with 500 credits and no credit card needed. Starter is $19/month for 2,000 credits. Standard is $49/month for 5,000 credits.

Appie gets LinkedIn data through third-party vendor APIs.

Responsible use

You're collecting data about real people. Read LinkedIn's terms yourself. For leads in the EU or UK, GDPR applies: have a lawful basis, keep only the data you need, and honour opt-outs. Check with your own advisers. Appie doesn't make that decision for you, and this post isn't legal advice.

FAQ

How do I track LinkedIn profile engagers from Claude?
Connect the Appie MCP server, add profiles with set_linkedin_profile, then call list_linkedin_leads to see the people who engaged with them.

Can an MCP server find emails for LinkedIn leads?
Appie's list_linkedin_leads returns email and phone when a lookup has found them. Each lookup costs 5 credits per lead. The MCP doesn't list a separate lookup tool, so check the docs for how lookups run.

How much does a LinkedIn profile scan cost in Appie?
30 credits per profile scan. Saving and listing profiles is free.

Can Claude send LinkedIn messages through Appie?
No. The MCP has no messaging, connection or posting tools.

Add your watch list with set_linkedin_profile and list your first leads from Cursor or Claude: appie.run/docs/mcp

Top comments (0)