Use Wingmen from Claude

What Claude can do

Nine things. Seven of them read, and every key gets those.

• Pipeline status

  Where the workspace stands right now: leads by status, how many came in today, whether discovery and outreach are running, and which list approved leads are saved to.

• Leads waiting on you

  The queue in Lead Radar, highest score first, with enough on each person to make the call.

• Contact search

  Find a saved contact or lead by name, company or email. Filter by signal type or by status.

• Campaign performance

  How the agents are doing: leads enrolled, invites sent, acceptances, replies, send failures, and the all-time funnel.

• Conversations

  Your Wingmen inbox. Filter by sentiment or search by lead name.

• Usage against your plan

  Contacts generated, messages sent, AI credits, connected accounts, and how much of each is left.

• Your ICP

  The ideal customer profile exactly as scoring and targeting read it, not a summary of it.

Two more, only if you allow them

When you create a key you choose between read only and read plus approving leads. Read only is the default, and a read-only key cannot see or call either of these.

• Approve a lead

  Saves a lead from the queue to your target list. Nothing goes out at that moment. The campaign engine drains that list on its own schedule, under the same pacing, billing and safety limits as an approval you click yourself.

• Dismiss a lead

  Takes a lead out of the queue so it stops coming back. Nothing is deleted, the lead stays on record as removed.

What it cannot do

Claude cannot send a message or an email, send a connection request, view anyone's profile, post, comment, enrich a lead, spend your credits, or change your targeting. Those are not exposed to it at all, on either scope, so there is no prompt that reaches them.

Setting it up

1. Create a key

In Wingmen, open Settings and pick the Claude / MCP access tab. Give the key a name so you can tell your keys apart later, choose what Claude may do, then press Create key. The key is shown once, so copy it before you close that panel. The same panel hands you both snippets below with your key already filled in.

2a. Claude Code

Run this in your terminal, with your own key in place of the placeholder.

claude mcp add --transport http wingmen https://app.flywingmen.com/api/mcp \
  --header "Authorization: Bearer wgm_live_your_key_here"

2b. Claude Desktop

Add this to your Claude Desktop config file (Settings, Developer, Edit Config), then restart Claude Desktop. The mcp-remote command it runs is the bridge a desktop client uses to reach a server that lives on the web.

{
  "mcpServers": {
    "wingmen": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://app.flywingmen.com/api/mcp",
        "--header",
        "Authorization: Bearer wgm_live_your_key_here"
      ]
    }
  }
}

3. Ask it something

• “What is in my pipeline right now?”
• “Who is waiting on a decision, best first?”
• “How did my agents do this week, and where am I losing people?”
• “Anything hot sitting in my inbox?”
• “Am I close to any of my plan limits?”

Keys and safety

• The key is shown once

  Wingmen keeps only a fingerprint of it, so no screen can show it to you again, and no one at Wingmen can read it back. If you lose it, create a new one and revoke the old.

• Revoke anytime

  Settings, Claude / MCP access, the revoke button next to the key. It stops working immediately and anything connected with it loses access on the next call.

• Read only unless you say otherwise

  Approving leads is a separate choice at the moment you create the key, not a setting Claude can change later.

• A key sees one workspace

  The workspace is fixed to the key when you create it. Nothing in a request can point it at anyone else's data.

• Every call is recorded

  Calls land in the audit trail marked as coming from Claude, so an approval made this way never reads as you clicking it in the app.

• There is a daily ceiling

  500 calls per workspace per day. A normal conversation is nowhere near that. It is there so a client stuck in a loop stops instead of running all night.

Treat the key like a password. Anyone holding it has the access above until you revoke it.