Skip to main content
Harp is built to be driven by Claude. Claude does the research, writing and decisions; Harp’s MCP server gives it the tools to read and write your outbound records, and Harp does the sending. You use your own Claude plan, so there are no AI credits.

​
Connect the MCP server

The Harp team installs the server with you during onboarding. You need two values from the app:
  • API key: Settings > Integrations > Developer > generate a key
  • Workspace ID: the ID in your workspace URL
The server runs locally over stdio and talks to Harp over HTTPS. It reads three environment variables: It works in any MCP client: Claude Code (.mcp.json), Claude Desktop (claude_desktop_config.json) and Cowork.

​
A small tool list on purpose

Harp shows Claude a short list of daily workflow tools, plus three folder tools (browse_tools, describe_tool, run_tool) that reach everything else. Results come back as compact JSON. This keeps tool definitions and read results small, so Claude can work through a full account list without filling its context window.

​
The daily tools

​
What a session looks like

1

Briefing

Claude calls briefing and sees what is due today.
2

Research

research_gaps lists the questions each account still needs answered. Claude researches them and saves each answer with save_answers, including the evidence and where it came from.
3

Enroll

Qualified contacts go into a campaign with enroll. If a campaign requires copy review, Claude reviews the rendered drafts with copy_review_queue before they send.
4

Manual steps

work_queue lists LinkedIn and manual steps that are due. Claude completes them and records each with step_done.

​
Example prompts

  • “Start with a briefing, then fill the research gaps for my top 20 accounts.”
  • “Find accounts we haven’t touched in 60 days that passed qualification, and enroll their VPs of Sales in the re-engagement playbook.”
  • “Review the drafts going out tomorrow and tighten the first lines.”

​
How sending works

Each mailbox waits a random 2 to 6 minutes between sends, so a large campaign spreads out over time. Emails land in the recipient’s local working hours when their timezone is known. A campaign with copy review holds each email until Claude approves the draft.