Demandbase MCP and Linkeddit in Claude: know which accounts to work and what to say

The Demandbase connector is the account side. Its Agent Index listing shows 7 tools: 3 reads, 1 write and 3 the listing does not classify. Among them are account_brief, company_global_directory and contact_global_directory for its third-party data, plus search_internal_account_database and search_internal_person_database for your own accounts and contacts. Demandbase's own MCP page says its intelligence covers 150M+ contacts, buying groups and intent signals.

Linkeddit is the competitor and AI visibility side. Compete tracks a competitor's blog, changelog and monitored pages with a priority on each move, and stores its public reviews from G2, Capterra, TrustRadius and Trustpilot. Answer Radar records which brands the five answer engines name when they answer your buying questions. All of it comes with one plan at $60 a month. Linkeddit holds no company or contact list, and it writes no messages.

That split matters because the two halves answer different questions. Demandbase answers "who" and "how warm". Linkeddit answers "why now" and "what to say". Claude reads both and drafts the account plan, and you decide what goes to the account team.

It adds the competitive context an account brief cannot hold. Demandbase's connector description says an account brief combines engagement state, opportunities, buying-group coverage, intent signals, company profile and news in one call. None of that is what a rival shipped last week or what its reviewers say.

On Linkeddit's test project, plausible.io, a read-only run returned two high priority competitor signals for the week of 2026-10-26: Matomo published critical PHP security guidance, and Fathom Analytics launched an AI assistant called Luna. Each came with a source link and a line on why it matters. Claude can set one beside an account that uses that competitor and open the conversation with a real event instead of a generic pitch.

A B2B SaaS founder described the cold version of the problem: "vague “we do it differently” claims kill cold outreach." A dated competitor move, a review quote or an answer gap is the opposite of vague, and each carries a link the account owner can open.

Not an alert feed. Claude works when you start it, so a competitor move reaches your account list when you run the prompt. Linkeddit's side runs on its own clock: on the test project all five competitor monitors are set to weekly, each with a next run of 2026-11-04, so the data is ready when you ask.

A workable weekly routine is to have Claude read the high priority competitor signals with Linkeddit, then ask Demandbase for target accounts that match the competitor's customer profile or show intent on its topics. On the test project the week produced two high priority signals, so a short list is a normal result. Say so in the output instead of padding it. If you need a real-time alert, use a tool built to push one.

Start with who actually competes with you in search, then take that list to Demandbase. Linkeddit's competitor footprint on the test project covers 59 checked keywords and 358 competing domains. Matomo ranked in the Google top 10 on 11 of those keywords, and its domain was cited 21 times by ChatGPT in the latest finished answer run, so it is a company worth studying.

Claude can take the competitor names that come out of that data and ask Demandbase for companies by name with company_global_directory, then read an account_brief for any it finds. Be strict about one point: a competitor domain is a vendor, not a customer. The step that finds customers of a competitor needs a technology filter that the connector listing does not confirm, so the prompt should tell Claude to stop and say so rather than guess.

Sometimes. Answer Radar records which domains the engines cite when they answer your buying questions, and answer_gaps_get lists the questions where an engine recommended somebody else. On the test project the top open gap was "Umami vs Matomo for self-hosted analytics", with an intent score of 0.6 and an evidence score of 22.

Demandbase is a company and contact database, so it helps when a cited source is a company with a team you can reach, such as a vendor or a publisher with a business entity. It is not a directory of every editor or blogger. Ask Claude to read the cited domains with Linkeddit, look each company up, and say plainly which it could not find. Outreach is for a real conversation about a useful page, never a way to buy a citation.

Check access, data and claims. The connector is available only with the right Demandbase licenses, and its listing counts one write tool, so tell Claude to change nothing in Demandbase unless you ask. Contact data is personal data, so follow your own policy and the rules of the countries you contact.

Then verify each competitor claim against its source link, because Claude can misread a changelog. A review is one customer's opinion at one time, so quote it with its date and site and never present a single review as a trend. Check the top few accounts by hand before anyone writes to them.