CRM · The Companies API + Claude
Companies API MCP with Claude: Find, Enrich and Analyse Target Accounts
The short answer
Claude works with the Companies API through the Model Context Protocol, an open standard that lets Claude securely use other software. Once connected with an API key, Claude can search company profiles, enrich records with technology and location data, build target-account lists and analyse company similarity, all from natural-language requests, with permissions the organisation controls.
What is The Companies API?
The Companies API is a business intelligence service for searching, enriching and analysing company data. It helps teams discover company profiles, the technologies companies use, where they operate and how they relate to one another. Sales, marketing, business development and revenue operations teams typically use it to find prospects, keep CRM records accurate and plan outreach. It sits within the CRM category, so the data often feeds directly into the systems where customer relationships are managed.
How Claude connects to The Companies API through MCP
The Model Context Protocol, or MCP, is an open standard that lets Claude use other software securely. Think of it as a universal adapter between Claude and a tool. Through MCP, Claude can ask the tool for information and, where you allow it, take actions, without your team copying data by hand between screens.
Once the Companies API is connected, Claude can typically search for companies by criteria such as industry or location, look up a profile, add technology and location details to existing records, assemble a list of accounts that match your ideal customer profile and compare companies for similarity. Requests can be made in ordinary language, such as asking for mid-sized logistics firms in the Gulf that use a particular platform.
Access is controlled by the API key your organisation issues. We set up least-privilege access so Claude only reaches the data it needs, and consequential actions such as bulk updates to your CRM can be routed to a person for approval first. Audit logs record what was requested and returned, so your team stays in charge of what changes.
What you can automate
Building target-account lists
A business development manager describes the ideal customer in plain English, for example software firms with a set headcount range in the UK. Claude searches the Companies API, shortlists matching companies and presents them in a clean list ready for review. The team spends time deciding who to contact rather than building spreadsheets by hand.
Enriching CRM records
Sales operations teams often hold company records with missing details. Claude can pull technology and location data for accounts already in the CRM, flag gaps and propose updates. A person reviews the changes before they are written back, which keeps records accurate and segmentation reliable.
Finding lookalike customers
When a company wins a strong customer, the marketing lead wants more like it. Claude uses the similarity analysis in the Companies API to identify firms with comparable profiles, technologies and locations, and summarises why each one fits the pattern.
Preparing account plans
Account managers preparing a quarterly review can ask Claude for a current profile of a client or prospect, including its technology footprint and locations. Claude pulls the relevant details into a short briefing, saving research time before a meeting.
Territory and market mapping
A regional head planning expansion can ask Claude to map companies by location and sector within a chosen market. The output helps leaders decide where to add sales capacity and which segments deserve focus in the next planning cycle.
An end-to-end workflow: Qualified prospect list to CRM
TriggerEvery Monday morning, or when a regional sales lead requests a new list
Claude reads the agreed ideal customer profile, such as industry, size and region, from the sales brief.
Claude searches the Companies API and returns matching company profiles with technology and location data.
Claude removes companies already present in the CRM, checking existing records to avoid duplicates.
Claude drafts the new records and a short reason for each match, and posts them for review in the team's channel.
After a sales manager approves the list, Claude creates the accounts and contacts in the CRM and logs the source.
OutcomeSales teams receive a fresh, de-duplicated list of qualified prospects each week, with reasons attached, and reps spend their time on conversations rather than research. Results vary by market and data coverage.
How we set it up
Free automation audit
We review how your team currently finds and maintains company data, and identify the workflows worth automating with the Companies API. There is no charge for this session.
Secure connection with an API key
Your organisation issues an API key for the Companies API. We store it securely and connect Claude through an MCP server or a managed connector, with least-privilege access limited to what the workflow needs.
Workflow design
We design the end-to-end flow across the Companies API and your other systems, such as your CRM, Microsoft 365 or ticketing tool, and agree which actions need human approval.
Testing against real cases
We test the workflow using past prospecting and enrichment cases from your team, compare outputs with what your people would have produced, and tune prompts and rules before anything goes live.
Launch, monitoring and training
We launch with monitoring and audit logs, then train your sales, marketing and operations staff on making requests, reviewing results and approving changes.
Who benefits
- Sales leaders
- Get consistent, well-matched prospect lists without waiting on manual research.
- Revenue operations managers
- Keep CRM company records complete and de-duplicated with reviewed updates.
- Marketing managers
- Identify lookalike accounts for campaigns and measure segment fit more easily.
- Account managers
- Arrive at client meetings with current company profiles and technology context.
Security and control
- Least-privilege API key access, limited to the data each workflow needs.
- Human approval before any bulk change is written to the CRM.
- Audit logs recording what was requested, returned and changed.
- Regular reviews of match quality, so outputs stay aligned with your ideal customer profile.
- Clear rules on how company data is stored, retained and deleted in line with your policies.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the Claude workflow in their chosen region to meet their data requirements. Indian organisations must consider the Digital Personal Data Protection Act, 2023, and we can host in India for that purpose. In the Middle East, including the UAE and Saudi Arabia, we design around local data protection laws and select a hosting region that meets those requirements. The right hosting location is chosen during the audit, not assumed.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Companies API MCP server do?
The MCP server gives Claude a secure way to use the Companies API. Claude can search company profiles, enrich records with technology and location data, build target-account lists and analyse company similarity, using natural-language requests. The server only exposes the actions you approve during setup.
Is connecting the Companies API to Claude secure?
Security depends on how it is set up. We use an API key stored securely, least-privilege access and audit logs. Consequential actions can require human approval. We also agree on data retention and hosting region with your team before launch.
What can Claude do with the Companies API?
Typically, Claude can search for companies by criteria, retrieve profiles, add technology and location details, compile prospect lists and compare companies for similarity. Exactly what is possible depends on the access your API key provides and the rules you set.
How long does setup take?
Simple connections can be completed in a few days once the workflow is agreed. Workflows that touch several systems, such as the CRM and internal approvals, usually take longer. The free automation audit gives a realistic timeline for your case.
Which plan or permissions do I need?
You need an API key issued by your organisation for the Companies API, with access appropriate to the data you want Claude to use. The exact plan and permission level depend on your existing agreement with the tool's provider, so check that with your account contact before we begin.