Two MCP servers, no integration build, and a researched brief on the record before the call.
Every other workflow on this site is a pipeline: a trigger, a set of steps, a schedule and something to maintain. This one is not, and that is the point of including it. An AI client connected to two MCP servers, one for data and one for the CRM, can do the research-and-write-a-brief job without anybody building the integration between them first.
That is a genuinely new capability rather than a faster version of an old one. The job it replaces is not a pipeline, it is the twenty minutes a rep spends before a call assembling context from four tabs, or the half-built automation somebody wrote to do it badly. It does not replace a scheduled sync, and this page is careful about that line.
This is on-demand research with a write-back, driven by a person or a task rather than by a record event. It is not a substitute for the CRM data layer, which is a scheduled loop over thousands of records and should stay one. An agent is the right tool for one account at a time and the wrong tool for ten thousand.
4 steps. The ones in blue are the data layer; everything else is plumbing you already own or can stand up in an afternoon.
Point the client at the MCP endpoint. OAuth 2.1 where the client supports it, otherwise an Authorization header with your API key. Thirty-seven tools arrive by their own count, 36 of them in its tables: enrich and search for people and companies, the live variants, the search filter catalogues, asynchronous email and phone lookups that return a task id to poll, Lists, Bulk, tasks and goals, and free checks on a profile, your usage and a running task. A company domain now goes straight in through enrich_company, which it did not before November 2026.
HubSpot publishes a connector for Claude that sits at 184,000 installs on its marketplace, which makes it one of the most-installed apps HubSpot lists. It reads and writes CRM records under your own permissions.
Name the account, say which fields to pull, say what the brief should contain, and say explicitly what to do when the data is missing. The last instruction is the one that decides whether this is useful or dangerous.
A note on the company record, so it is where the rep already looks rather than in a chat log. Optionally a Slack message to the owner, which is the same restraint rule as everywhere else: one channel, one trigger, one owner.
This workflow ships as a skill file: the API surface of every tool in the chain, the build order, the limits that break it, and how to check it worked. Point an agent at it and it has what it needs without reading 3 sets of vendor docs first.
--- name: mcp-account-brief description: Connect the Reverse Contact and CRM MCP servers to an AI client and have i t research an account and write a pre-call brief onto the CRM record. Use wh... --- # Agent-written account briefs ## What you are building ## Prerequisites ## The tools, and how to call them → Reverse Contact, HubSpot ## Build it → 4 steps ## Gotchas ## What breaks, from the vendors' own docs ## How to verify it works → 5 checks
mkdir -p .claude/skills/mcp-account-brief curl -o .claude/skills/mcp-account-brief/SKILL.md https://www.reversecontact.com/integrations-hub/skills/agent-account-briefs.md
For Codex, Cursor, or anything else that reads a file or fetches a URL, hand it https://www.reversecontact.com/integrations-hub/skills/agent-account-briefs.md directly. It is plain markdown with YAML frontmatter and no tool-specific syntax, so nothing in it depends on which agent is reading it.
3 of the joins in this chain have a full guide behind them, HubSpot and Reverse Contact and Slack and Reverse Contact among them. The chain crosses 3 of the seven layers a stack splits into, from the data layer outward, which is why no single vendor owns it.
Documented by one of the vendors in the chain, and easier to design around than to discover.
All five are documented by a vendor rather than observed by us, which is the useful part: a limit you can read is a limit you can design around before it costs you a week.
What each component bills on, and which line actually scales with your volume.
| Component | Billing | What drives it |
|---|---|---|
| Reverse Contact | Per credit | Every call the agent makes. Usually more per account than a pipeline would make, because an agent explores. |
| HubSpot connector | Free | Published by HubSpot. It runs under your own CRM permissions. |
| AI client | Whatever yours costs | Unchanged by this workflow. No hosting, no scheduler, no instance. |
| Build | Zero | Two connections and a prompt. There is nothing to maintain when an API version moves. |
The variable nobody expects is how many enrichment calls an agent makes while exploring one account. Check your usage after a week rather than guessing, and put a ceiling on it if the answer surprises you.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, with a confidence score your logic can branch on. The free trial takes no card and runs until the 500 credits a new account starts with are spent, which is enough to run this end to end before anyone signs anything.
Free trial, no card required, and 500 credits to start.
Reverse Contact lists Claude.ai, Claude Desktop, Cowork, Claude Code, ChatGPT, Codex, Cursor and Gemini CLI, plus any stdio-based MCP client through mcp-remote. The server speaks streamable HTTP with JSON-RPC 2.0. In practice, if your client supports remote MCP servers, it works.
No, and treating it as one is the main way to be disappointed by it. Enrichment in the CRM is a scheduled loop over every record that needs a field. This is on-demand research over one account, producing prose rather than properties. Teams that need both run both, and the two barely interact.
Two controls. In the prompt, tell it to preserve nulls and attribute each fact to its source. In the setup, start it on notes rather than properties, so everything it produces is additive and reviewable rather than a change to a field your routing depends on. Move to property writes only once you have read a month of notes and trust them.
For this class of job, yes, and that is the interesting part. If an agent can call both APIs under your own credentials, the integration between them does not need to exist and nobody maintains it. What it does not replace is the scheduled, high-volume, two-way sync, which is still a pipeline and should stay one.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.