HeyReach MCP Server

Use your HeyReach API key (Settings → API Keys). The hosted MCP endpoint expects it as Bearer credentials on each HTTP request; other header styles are rejected with 401.

This integration is dynamic: the live tool list comes from the server at connection time. Orient using concepts below, then match capabilities to the tools and descriptions your client shows.

Core domains

LinkedIn sender accounts: List and inspect the LinkedIn identities that send on your behalf. Many workflows need a sender or account scope before you change routing or interpret activity.

Campaigns: List, inspect, pause, resume, and manage leads inside sequences. Only add leads to campaigns that are actually ready to send (not draft or misconfigured states).

Lead lists: Create lists, page through them, add or remove rows by profile identity, and move leads between lists or campaigns when the product allows it.

Conversations: Pull thread-style activity with filters (sender, campaign, lead identifiers, free-text search) when you need reply context or inbox triage.

Tags and lead context: Attach or read tags on a lead when you need segmentation or follow-up logic driven by labels.

Webhooks: Register and inspect outbound HTTP hooks for product events when you are integrating external systems.

Messaging: Send outbound messages where the product permits; respect sequence state and compliance (do not blast cold contacts outside campaign rules).

Workflow patterns

Start from read operations to collect stable IDs (senders, campaigns, lists, leads) before write steps. Pagination parameters are first-class—default page sizes are not always implied, so pass explicit limits when the schema allows.

Aggregate analytics and rollups often require account and campaign scope in the payload; if the API responds with a validation error about missing scope, gather those IDs from listing endpoints first.

Batch lead imports and status toggles can hit rate limits—space writes and surface HTTP errors to the user in full.

Entity model (conceptual)

A campaign ties together LinkedIn senders, lead sources, and sequence steps. Leads are usually addressed by profile URL, email, or internal identifiers depending on the operation. Lists hold leads for bulk operations. Conversations link leads, senders, and campaigns for reply tracking.