# Amplemarket

> Canonical: https://www.yalc.ai/mcps/amplemarket/

Run outbound (search, enrich, sequences) inside Claude Code via Amplemarket's official remote MCP.

## Categories

- prospecting
- content

**Website:** https://amplemarket.com/

## Glance

- Maintainer: Amplemarket (official)
- Transport: Remote HTTP (hosted)
- Auth: OAuth 2.0 (no API key)

**Install Command:** claude mcp add amplemarket --transport http https://mcp.amplemarket.com/mcp

**Install Notes:** Amplemarket ships an official hosted MCP server at `https://mcp.amplemarket.com/mcp`. It is a remote HTTP server, so there is nothing to run locally and no token to paste. Run the command above, restart Claude Code, and the first call opens a browser window where you sign in to your Amplemarket account and approve access over OAuth 2.0. You need a paid Amplemarket seat for the underlying data and sending to work.

**Yalc Fit Score:** 6

**Yalc Verdict:** The right bridge when Amplemarket is already your data and sending layer. Yalc keeps the orchestration, signal reasoning, and cross tool logic while driving Amplemarket search, enrichment, and sequences through the MCP.

## Plain Description

Amplemarket maintains an official remote MCP server that exposes its outbound platform as native Claude tool calls. As of 2026 it covers people and company search, contact and company enrichment, lead list creation and management, sequence creation and enrollment, Duo AI messaging, Unibox inbox and outbox access, and natural language analytics queries. Connection is a single remote URL with OAuth, so there is no local process and no API key to manage.

For Yalc operators the honest framing matters. Amplemarket is an all in one outbound platform, and Yalc positions as the operating system that sits above your stack rather than a replacement for a sending tool you already pay for. If you run Amplemarket, this MCP lets Yalc use it as the execution layer: Yalc gathers signals, decides who to touch and why, then calls Amplemarket to enrich the contact, add them to the right list, and enroll them in a sequence. The reasoning stays in Claude Code, the sending stays in Amplemarket, and the handoff is one prompt instead of a tab switch.

If you do not already run Amplemarket, this is not the page that sends you to buy it. Yalc composes a stack from a CRM, a sequencer, and a data provider of your choice, and Amplemarket is simply one sequencer plus data option that happens to expose a clean MCP.

## Yalc Framework

**Workflow Step:** send

### Workflow Narrative

The Amplemarket MCP sits at the **send** node, with a reach back into intake. Yalc runs the top of the workflow (signal capture, account selection, message reasoning), then calls Amplemarket to enrich the chosen contacts and push them into a sequence.

Most useful patterns: enrich a list Yalc assembled from a signal run, create a lead list with custom columns for a new segment, enroll validated contacts into an existing sequence, and query campaign analytics in plain language for a weekly readout.

**Workflow Position:** The outbound execution node for teams already on Amplemarket. Yalc decides and personalizes; Amplemarket enriches and sends. Less about replacing your sequencer, more about letting Yalc drive it.

### Prompt Patterns

- Yalc, take these 40 accounts from the hiring signal run, enrich the head of sales at each through Amplemarket, and build a lead list called "Q3 hiring signal".
→ Yalc calls Amplemarket search and enrichment via the MCP, then creates the list.

- Yalc, enroll the 12 contacts that replied positively last week into the Amplemarket sequence "Warm reply follow up", and skip anyone already in an active sequence.
→ Yalc reads sequence membership, filters, and enrolls through the MCP.

- Yalc, ask Amplemarket for reply and meeting rates on my three active sequences and post a plain language summary to Slack.
→ Yalc runs the analytics query via the MCP and posts through the Slack MCP.


### Chaining

**Upstream:** Yalc signal run → Amplemarket MCP (enrich, list, enroll)

**Downstream:** Amplemarket reply event → Yalc workflow (via webhook handler)


### Anti Patterns

- Don't use the MCP to replace Yalc's reasoning. Amplemarket sends; Yalc decides who and why. Let each do its job.
- Don't enroll unvalidated contacts. Run Yalc's qualification first, then enroll only survivors.
- Don't treat analytics answers as source of truth for reporting. Spot check against the Amplemarket dashboard before you quote a number to a client.


**Compatibility:** The server is remote and hosted, so it works in any client that supports remote MCP servers over HTTP, including Claude Code, Claude Desktop, and Cursor. Auth is OAuth 2.0 with a browser sign in on first connect. Access and rate limits follow your Amplemarket plan.

## Pros

- Official Amplemarket server. Hosted and remote, nothing to run locally.
- OAuth sign in, no API key to store or rotate.
- Broad Coverage: search, enrich, lists, sequences, messaging, analytics.
- Works across Claude Code, Claude Desktop, and Cursor.

## Cons

- Requires a paid Amplemarket seat. The MCP is a front door, not free data.
- Overlaps heavily with Yalc's own outbound logic, so value is highest only if you already run Amplemarket.
- Hosted only. No self host option if your security posture forbids remote MCP servers.
- Sending actions are real. A loose prompt can enroll the wrong people, so gate with qualification.

## Who For

- Teams already paying for Amplemarket who want Yalc to orchestrate it
- Operators who want signal reasoning in Claude Code and sending in an established platform
- RevOps leads consolidating outbound execution behind one MCP call

## Alternatives

- **Lemlist MCP**
  - Rule: Switch when Lemlist is your sequencer and you want the same drive it from Yalc pattern.
  - Url: #
- **Smartlead or Instantly MCP**
  - Rule: Switch when high volume cold email deliverability is the priority over an all in one suite.
  - Url: #
- **Native Yalc outbound**
  - Rule: Skip a third party sequencer entirely when you want Yalc to own the full send path.
  - Url: #

## Faq

- Q: Is there an official Amplemarket MCP server?
  - A: Yes. Amplemarket hosts an official remote MCP server at https://mcp.amplemarket.com/mcp. Connect it to Claude Code with `claude mcp add amplemarket --transport http https://mcp.amplemarket.com/mcp`, then sign in through the browser window on first use.
- Q: Do I need an API key?
  - A: No. The server uses OAuth 2.0. The first call opens a browser where you sign in to Amplemarket and approve access. There is no key to paste or rotate.
- Q: What can the Amplemarket MCP actually do?
  - A: It exposes people and company search, contact and company enrichment, lead list management, sequence creation and enrollment, Duo AI messaging, Unibox inbox and outbox access, and natural language analytics.
- Q: Does it work with Claude Code, not just Claude Desktop?
  - A: Yes. It is a remote HTTP server, so any client that supports remote MCP servers connects, including Claude Code, Claude Desktop, and Cursor.
- Q: How does this fit with Yalc if Yalc already does outbound?
  - A: Yalc stays the operating system that reasons over signals and decides the play. The Amplemarket MCP is the execution layer for teams already on Amplemarket, so Yalc enriches, lists, and enrolls through it rather than replacing a sender you already pay for.
- Q: Do I need a paid Amplemarket account?
  - A: Yes. The MCP is the access door to your Amplemarket workspace. The underlying data, sequences, and sending require an active Amplemarket seat.

**Reviewer:** Othmane Khadri