Claude Crunchbase connectorWhat Claude can do in your Crunchbase account.
The Claude Crunchbase connector exposes 16 tools: 11 read, 3 write, and 2 have no description anywhere. Here: which company, funding and investor data Claude can pull, which lists it can create or fill, the seat your admin must assign, and who can switch it off.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for sales, investors and analysts
Researching a company on Crunchbase usually means a search, a profile, three tabs of funding rounds and a spreadsheet. With the connector on, you describe what you want in a sentence and Claude picks the right Crunchbase tools itself, then answers in the conversation with data drawn from the same profiles your team already uses.
A briefing before the meeting. A founder meets an investor on Thursday. cb_expert_resolve_entity pins down the right firm even if the name is ambiguous, then cb_entity_get returns its profile with funding rounds, leadership and investments.
A sourcing list from a thesis. A VC associate describes the kind of startups they fund. cb_expert_build_search turns that description into a precise Crunchbase search, and cb_search_query can rerun it identically next month.
Research that survives the chat. cb_list_create opens a list in your workspace and cb_list_add_entities fills it, so the team keeps what Claude found.
What the sheet will not tell you: no documented tool edits a company profile or your CRM. Documented writing covers lists and feedback only. Two tools on the sheet have no description at all. Your workspace needs an MCP seat assigned by its admin. And nothing runs by itself: no tool fires when a company raises a round. To run something on a schedule, look at automation tools, a different job; the Integrations hub gathers them.
The vocabulary in one minute
Five words you will meet while connecting Crunchbase.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work on it while it answers you.
- Tool
- One named thing a connector lets Claude do. Claude chooses the ones it needs by itself; the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, where you give Claude the access it will use later. Granted once per person, revocable the same way.
- Approval
- The confirmation Claude waits for before going through with something that changes an account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service.
Connect Crunchbase to Claude in three steps
- 01
Find Crunchbase in Claude
In Claude's settings, open Customize, then Connectors, and look for Crunchbase in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector before members can connect individually.
- 02
Start the connection
Click Connect on its row and sign in with your own Crunchbase account in the window Crunchbase opens. If the link breaks later, choose Disconnect and connect again.
- 03
Read the authorization screen
Read the authorization screen before accepting. It is Crunchbase's screen, not Claude's, and it sets what the access covers. You can also take the access back from your Crunchbase account afterwards.
The 16 tools of the Claude Crunchbase connector
Crunchbase MCP gives Claude 16 tools: 11 that read your account, 3 that change something in it, and 2 no official source describes.
Three groups: what Claude reads, what it changes in your workspace, and what no official source describes. Names stay as Claude shows them, in English.
- 11 read
- 3 write
- 2 not documented
What Claude reads (11)
11 toolsEleven tools that search, resolve and fetch Crunchbase data without changing anything.
cb_entity_autocomplete
Searches Crunchbase by name and returns matching identifiers with a short description. It is how Claude gets a valid ID before calling anything else.
cb_entity_get
Retrieves everything on one identified entity: financials, leadership, locations and categories, plus linked cards such as rounds raised, investments made and employees.
cb_expert_build_search
Turns a plain description of the companies you want into a structured Crunchbase search, handling fields, operators and value formats so you never write query syntax.
cb_expert_query_answer
Answers a question in natural language with live Crunchbase data: it works out the queries, runs them and gives an answer with supporting results rather than a raw table.
cb_expert_query_domain
Explains the shape of the Crunchbase data itself: which entities, fields and links exist, and whether a draft question can be answered. It never touches actual records.
cb_expert_resolve_entity
Takes an ambiguous name and resolves it to one canonical Crunchbase entity, or returns a ranked list of candidates when it is not confident.
cb_list_get
Returns the entity identifiers stored in one of your saved lists, page by page, so Claude can then work on exactly those companies.
cb_list_query
Lists every saved list you own, with names, how many entities each holds and timestamps. Claude uses it to find the right list ID first.
cb_metering_get_state
Shows the meter states that apply to you: which limits are active and how they affect each tool.
cb_reference
Serves Crunchbase's own reference on its data model as readable documentation, with an index and paths to drill into. Called with an empty path, it returns the full navigable index.
cb_search_query
Runs a structured search with explicit criteria and returns matching entities with the fields you asked for. Crunchbase presents it as deterministic and repeatable.
What Claude changes (3)
3 toolsThree tools that write to your workspace: lists and feedback only. No source describes a confirmation specific to them; the general rule below applies.
cb_expert_submit_feedback
Approval: see the ruleSends your feedback on an earlier direct answer back to Crunchbase. A negative rating may lead the service to rewrite the query and return corrected results.
cb_list_add_entities
Approval: see the ruleAppends companies or other entities to one of your existing lists. The list then lives in your workspace for the whole team.
cb_list_create
Approval: see the ruleCreates a new, empty list in your Crunchbase workspace. Filling it is a separate step.
Undocumented (2)
2 toolsThe directory publishes these two names and nothing more. No official text says what they do, and we will not guess from a name.
cb_expert_submit_search_feedback
This name appears in the directory's tool list, and nothing more is published about it. Crunchbase's tool reference does not mention it and no Claude page does either.
cb_knowledge_center
Same situation: a listed name that no official source documents. Better to show the gap than to fill it with a guess based on how the name sounds.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before any action it takes on an account on your behalf. The request shows up in the conversation right when it matters.
That covers the three writing tools here. On Team or Enterprise, owners decide whether members may let certain actions through without being asked every time, and they can cap what a connector may do for the whole organization, for example keeping reading open and closing writing. Nobody overrides that from their own account. Claude works with your rights and nothing more: every call runs as the signed-in Crunchbase user.
Which Claude plans it runs on
Of the 819 sheets in the official directory, none shows plan availability. The connector-by-connector answer is published nowhere.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before each member can connect. For the current state, the connector's sheet in the official directory is the place to look. Also note this connector is documented by Crunchbase only, with no Claude help article of its own.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you; nothing starts when a company raises money or changes leadership.
The tool list is an observed floor, not a promise: an admin can open actions no public sheet lists. The directory's partner badge is not a security audit either, and Anthropic writes it on every sheet: it does not pick the tools a publisher exposes and does not guarantee they behave as described. Connect only what comes from a publisher you trust. For a connector that writes to a work tool, compare with the Claude asana connector.
Need help connecting Crunchbase MCP to Claude?
A person reads every message.
