For GTM engineers
The Harp team ·
If you build outbound systems with Claude Code, you already have the agent, the data tools and the prompts. What you keep rebuilding is the rest: somewhere to store research with provenance, a sequencer that respects mailbox limits, something that notices replies, and a LinkedIn runner you trust with a real account. Harp is that layer.
What you get
- An MCP server shaped for agents: a short daily tool list, folders for the rest, compact JSON results.
- Qualification questions with answers, evidence, source, history and age, plus research gaps.
- Playbooks and campaigns, with drafts held until variables resolve and optional copy review.
- Sending with warm-up, spacing, recipient-local timing, plain text and one-click unsubscribe.
- A reply loop that stops sequences and wakes your agent.
- LinkedIn steps from a real Chrome on a Mac, with a right-person check.
Plays well with your stack
Your agent can connect other MCP servers next to Harp, such as Apollo or Clay for data. Harp holds the outbound loop; you keep choosing the rest.
Questions
What is a GTM engineer?
Someone who builds the systems behind go-to-market: data, enrichment, routing, sequencing and now agents. See What is a GTM engineer?.