If you want Harmonic feeding deal signals into Claude, use Harmonic's own hosted MCP server. It is the right default for day-to-day enrichment, search, and saved-search monitoring — you sign in with OAuth, there is nothing to install, and it lives in Claude's Connectors menu. The community-built server still wins in two narrow cases: when you want raw, scriptable access to specific API endpoints, and when deal data isn't on your plan anyway and you'd rather have control over everything else. That's the whole piece in three sentences. The rest is the why, the gotchas, and the one setup detail that silently breaks the whole thing.
IThe Honest Verdict Up Front
Here's the call, stated plainly before any of the setup detail.
For most funds wiring Harmonic into Claude, the official hosted server is the answer. It covers the three jobs you actually do all day — enrich a company or a person, run a search, and watch a saved search for net-new results — and it does them through a login flow that takes about a minute. No local files, no key juggling, no version drift.
The actively-maintained community server is the better pick when you are an engineer who wants each Harmonic API endpoint exposed as its own tool, scriptable and predictable, and you don't need the deal-data tools that sit behind a paid gate regardless of which server you choose. The older community server is a skip — I'll explain why below.
One thing up front, because I build these integrations for funds for a living: this is a documentation-grounded map, not a benchmark. Everything here is read straight from Harmonic's own support docs, its marketing comparisons, and the READMEs and code of the two open-source servers — so when I tell you a tool is read-only or a call is gated, I'm telling you what the sources say, and I point at which source each time. The value here isn't a stopwatch. It's that the public record on Harmonic's MCP support is a mess of contradictions, and someone needs to sort it out before you wire anything into Claude.
IIYes, Harmonic Has an Official MCP Server (Despite What Google Tells You)
Search "harmonic api" or "harmonic mcp" right now and you'll hit a confident vendor blog post telling you Harmonic does not publish an official MCP server. It's wrong. Harmonic's own MCP Server getting-started guide — last updated October 2026, version 1.2.0 — documents a first-party, hosted, OAuth-based server at mcp.api.harmonic.ai, with a native listing in Claude's Connectors directory. That lets Claude, ChatGPT, or any MCP-compatible client pull live Harmonic company, people, and investor data directly, not through a third party.
Harmonic's marketing says the same thing in plainer words. In its comparison with SourceScrub, Harmonic notes that it "is compatible with all CRMs via Polytomic and has a native Affinity integration," and that "the API supports custom workflows, and Harmonic recently launched an MCP for connecting to any LLM." Its VC-focused post frames MCP as plumbing, not a science project: "Harmonic integrates natively with Affinity and provides API and MCP access for firms that want Harmonic's data to flow into their existing infrastructure."
So where does the "no official server" claim come from? A widely-indexed vendor post from October 2026 states it flatly while selling a proxy gateway built on top of the Harmonic API. The first-party docs and the Connectors listing contradict it directly. Worth knowing before you pay for a middleman you don't need.
There's a second trap in the search results. A separate company called Harmonic Security — no relation to the deal-sourcing platform — launched its own "MCP Gateway" in October 2025, a governance product for monitoring agent traffic org-wide. Different company, different problem. If a writeup blurs the two, close the tab.
IIITwo Ways to Connect: Claude Connectors vs. a Direct Config
There are two routes in, and they suit two different kinds of user.
The click-through route is the one I'd point most fund teams to. In Claude Web or Desktop, open your profile icon, go to Settings, then Connectors, then the Web tab. Find Harmonic in the list, add it, and complete the OAuth login to your Harmonic account. That's it — Claude now has the Harmonic tools, and the sign-in handles auth for you.
The developer route is for anyone living in Claude Code. You add Harmonic from the command line as an HTTP transport pointed at the server address, then run the MCP command to kick off the same OAuth login. Slightly more hands-on, same destination.
The one detail that silently breaks setups is the authentication header. If you're using API-key authentication instead of OAuth — the right choice for server-to-server and programmatic use — the header in your config has to be named exactly apikey, all one word, lowercase. Not "Authorization," not "api_key." Most MCP configs expect one of those two, so people copy a template, paste their key, and get silent failures with no obvious cause. Name the header apikey and it works. This is the kind of trap I also wrote about in Affinity MCP Setup: Claude, Cursor, and What Breaks — the pattern repeats across every MCP integration.
IVWhat You Actually Get: Quotas, Plans, and the Deal-Data Gate
What the server will actually let you do depends entirely on how you authenticate and what plan your team is on. Here's the shape of it:
A team admin flips the "use API credits for MCP requests" switch in the MCP integration settings to remove the daily cap; after that, MCP usage is billed against the same credits your direct API calls draw from.
The single biggest catch for anyone trying to wire "deal sourcing" end to end: deal data specifically is gated behind a separate add-on, even when enrichment and search tools are already available to you. You request it from your Harmonic account team. No MCP server — official or community — gets around that gate, because the gate lives on the account, not on the connector. If deal-flow tooling is the whole reason you're doing this, confirm the add-on is live before you build anything on top of it. For how those plan tiers price out by fund size, I broke down the real numbers in Harmonic.ai Pricing: The Real Cost by Fund Size.
VThe Official Tool Set: Built for Monitoring, Not One-Off Lookups
The hosted server organizes its tools into seven categories: enrichment, search, lookup, saved search, network mapping, list management, and custom data. Look at the real tool names surfaced in a third-party MCP directory listing and the center of gravity is obvious — this toolset is built to watch deal flow over time, not to run ad hoc company lookups.
The net-new tools are the point. You build a saved search once in Harmonic, then ask Claude what's new since last time — the companies or people that just crossed your criteria. That's a monitoring loop, and it's the thing the official server does best. One-off "tell me about this one company" lookups work too, but the tool surface clearly favors the standing-watch pattern.
Most of these tools are read-only. Write tools exist — creating or updating a list, for instance — but Harmonic does not currently support destructive operations, and Claude natively prompts you to confirm before any write runs. So an agent can add a company to a list, but it won't quietly delete your data, and nothing writes without a human tap.
VIThe Community Alternative: A 13-Tool Server You Install Yourself
The actively-maintained open-source option is alludium/harmonic-mcp-server, MIT-licensed, and it takes a different philosophy: one tool per API endpoint, mapped 1:1. It exposes 13 distinct tools, each wired to a specific Harmonic call — searching companies hits the search endpoint, looking up a company hits the companies endpoint, pulling net-new results from a saved search hits the saved-search net-new endpoint, and so on. If you think in endpoints and want predictable, scriptable behavior, this is the cleaner mental model.
Setup is a single npx command, and it authenticates with your Harmonic API key set as an environment variable rather than an OAuth flow. That's a plus for server-to-server automation and a minus for a non-technical teammate who'd rather click a button in Claude's settings.
The detail I like most is that it respects Harmonic's underlying rate limit for you. The Harmonic API allows 10 requests per second, and the server builds in automatic throttling and retry logic for rate-limited requests, with clear error messages for the usual failure codes — bad request, unauthorized, not found, too many requests, and server errors. That's the kind of unglamorous reliability work that decides whether an integration survives a busy sourcing week, the same theme I dug into in MCP Server Security: What My Own Audit Found.
aThe Older Community Server: Why to Skip It
There's a third option, blue-yard/harmonic-mcp-server, and I'd pass on it. It carries a smaller, rawer tool set — search a company by domain, search companies, search people, pull saved-search results, list a company's employees — and it sits at two GitHub stars. Setup is the clunky part: you point Claude Desktop at an absolute local file path, then manually run a set-api-key tool call inside the chat before anything works. Compared to the official server's OAuth login or the alludium one-liner, it's the most friction for the least surface. Interesting as a reference; not what I'd run today.
VIIOfficial vs. Community: Which One Wins for Deal Sourcing
Here's the side-by-side I'd actually hand a fund deciding between them.
Map it to the actual deal-sourcing jobs and, on paper, the split is clean. Enriching a company or a person, running a search, and pulling net-new results off a saved search all come through the official hosted hooks directly — those are first-class tools in Claude's tool list, documented by name. Anything that leans on a Harmonic endpoint that hasn't been wrapped as an official MCP tool, or on a bulk, scripted pattern you want to control yourself, still wants the raw API — which is exactly where the community server's one-tool-per-endpoint design earns its place. And deal data sits outside both: no server surfaces it until the add-on is live on your account, so a true "find me new deals" call fails the same way on every path until that gate is open. That's the honest version of which calls come through cleanly and which still need the raw API — read off the documented tool surfaces, not a leaderboard.
The verdict holds from the top. If you want the data flowing into Claude with the least fuss and your main job is watching saved searches for net-new deals, take the official hosted server. If you're an engineer who wants each endpoint as its own predictable tool — and you're not relying on the gated deal-data tools anyway — the alludium server gives you more control for the same underlying data. Either way, the deal-data add-on is the thing to sort out first.
VIIIWhat This Looks Like Wired Into a Fund's Actual Stack
The mistake I see funds make is treating a new connector as a new destination. It isn't. The point of wiring Harmonic into Claude is to move signal into the places your team already works — not to open yet another tab nobody checks.
For one multi-stage European fund, the useful pattern wasn't "log into Claude to ask about companies." It was routing the net-new results from a few carefully-built saved searches into the fund's existing CRM and a Slack channel the partners already read every morning. Harmonic's MCP tools surface what's new; a thin automation layer decides what's worth a human glance and drops it where the team lives. The connector is a pipe, not a product. I wrote up that whole philosophy in How I Automate AI Deal Sourcing Without a New CRM, and it's the same reason Harmonic's native Affinity integration and Polytomic CRM compatibility matter more than any single tool call — continuity beats novelty.
That's the lens I bring to this as an AI studio that helps funds integrate these tools without hiring an engineering team: pick the server that matches who's maintaining it, get the deal-data gate sorted, and spend your real effort on where the signal lands, not on the connector itself.
IXFAQ
Does Harmonic have an official MCP server?
Yes. Harmonic runs a first-party, hosted, OAuth-based MCP server at mcp.api.harmonic.ai with a native Claude Connectors listing, documented in its getting-started guide. Any vendor post claiming otherwise is out of date or selling you a middleman.
Is Harmonic's MCP server free to use?
Partly. Signing in with OAuth on a limited-API plan gives you 100 free MCP requests per day, resetting at midnight UTC, with deal data excluded. Beyond that, usage draws from your team's API credit pool, and teams on an Unlimited API access plan get unlimited MCP usage by default.
What's the difference between Harmonic's MCP server and the community one?
The official server is hosted, uses OAuth, and organizes tools into seven categories that lean toward saved-search monitoring. The actively-maintained community server, alludium/harmonic-mcp-server, is self-installed, authenticates with an API key, exposes 13 tools mapped 1:1 to API endpoints, and adds its own throttling and retry logic for Harmonic's 10-requests-per-second limit.
Can Claude create or edit records through Harmonic's MCP server?
Yes, within limits. Write tools exist — creating or updating a list, for example — but Harmonic does not support destructive operations, and Claude prompts you to confirm before any write action runs.
Is "Harmonic Security" the same company as Harmonic.ai?
No. Harmonic Security is an unrelated AI-governance vendor that launched its own "MCP Gateway" product in October 2025. It's easy to confuse with Harmonic.ai's MCP server in search results, but they're different companies solving different problems.
— Michael Rouveure
