Connecting AI Tools

Choose your AI tool, connect your Crunchbase account, then run a quick test.

Choose your AI tool

Choose an AI tool to jump to its setup instructions.

Other MCP clients · Create OAuth credentials · MCP and OAuth endpoints · Test your connection

Before you connect

Use these details when your AI tool asks for an MCP server:

Directory connections

Add the Crunchbase plugin or connector, then sign in with your Crunchbase account.

Crunchbase is available in ChatGPT's plugin directory.

1. Open the Crunchbase listing. View Crunchbase in the ChatGPT plugin directory. You can also open the Plugins tab and search for Crunchbase.
2. Install the plugin. Select Crunchbase, then use the + button to install it.
3. Connect your account. When prompted, sign in with your Crunchbase account and choose Allow to approve access.
4. Test your connection. Start a new chat in Chat or Work, make sure the Crunchbase plugin is available, and run the test prompt below.

ChatGPT Business, Enterprise, and Edu: your workspace admin controls which plugins are available to your role. If Crunchbase does not appear in search or cannot be installed, contact your workspace admin.

See OpenAI's plugin instructions.

Crunchbase is available in Claude's connector directory, including on the free Claude plan.

1. Open the Crunchbase listing. View Crunchbase in the Claude connector directory. You can also open Claude's connector directory and search for Crunchbase.
2. Add the connector. Select Crunchbase and follow the prompt to add or connect it.
3. Connect your account. Sign in with your Crunchbase account and choose Allow to approve access.
4. Test your connection. Start a new chat and run the test prompt below.

The connector is tied to your Claude account. After you add it, it is available in Claude on the web, desktop, and mobile apps.

Claude Team and Enterprise: workspace admins may need to enable connectors before members can add them. If Crunchbase does not appear in search or cannot be connected, contact your Claude workspace admin.

See Claude's connector instructions.

Crunchbase is available in Perplexity's Connectors directory.

1. Open the Crunchbase listing. View Crunchbase in the Perplexity Connectors directory. You can also open the Connectors settings page and search for Crunchbase.
2. Add the connector. Select the Crunchbase connector tile, then choose Connect (or Add/Enable, depending on the view).
3. Connect your account. Sign in with your Crunchbase account and choose Allow to approve access. When you return to Perplexity, confirm that Crunchbase shows as connected.
4. Test your connection. Start a new thread and either type @Crunchbase in your query or click the + icon, open Connectors and sources, and select Crunchbase. Then run the test prompt below.

Perplexity Enterprise: your organization admin may need to enable the Crunchbase connector before members can connect it. If Crunchbase does not appear in search, contact your Perplexity organization admin.

See Crunchbase's Perplexity setup guide for additional setup guidance.

Back to AI tools ↑

Coding tools and agents

Use Crunchbase from your editor, terminal, or coding agent. Choose the instructions for your AI tool.

If you sign in to Claude Code with your Claude.ai subscription, the Crunchbase connector you added in Claude.ai is automatically available in Claude Code. You do not need to add the MCP server again.

1. Connect Crunchbase in Claude.ai. Open the Crunchbase listing in the Claude connector directory, add the connector, and complete the Crunchbase sign-in flow.

2. Use the same Claude.ai account in Claude Code. Start Claude Code while signed in with the Claude.ai subscription where you connected Crunchbase.

3. Check the connection. In Claude Code, run:

   Text

   /mcp

   Crunchbase appears in the list with an indicator showing that it comes from Claude.ai.

4. Test your connection. Run the test prompt below.

claude mcp add --transport http --scope user crunchbase https://mcp.crunchbase.com

See Claude Code's MCP instructions.

Enable AI features, open a local project folder, and sign in to your chosen agent before setup.

1. Add the server. Open the Command Palette (Cmd+Shift+P on Mac, Ctrl+Shift+P on Windows/Linux) and run MCP: Add Server. Choose HTTP, enter https://mcp.crunchbase.com, and use crunchbase as the server ID.

2. Choose where to save it. For a personal Copilot configuration, select Global → Copilot Global when available. For other session types or shared project configurations, follow VS Code's configuration destination guidance.

3. Connect your account. Review the server trust prompt and complete the browser sign-in with your Crunchbase account. Choose Allow to approve access.

4. Test your connection. In an agent session, run the test prompt below.

   Review any tool approval prompt, then expand the tool call to confirm that Crunchbase returned the data.

{
  "servers": {
    "crunchbase": {
      "type": "http",
      "url": "https://mcp.crunchbase.com"
    }
  }
}

Connect Cursor directly to https://mcp.crunchbase.com and sign in with your Crunchbase account. You do not need to create a custom OAuth client or enter a client ID or client secret.

1. Add the server. Add the following to ~/.cursor/mcp.json to make Crunchbase available across your projects, or .cursor/mcp.json in your project for project-specific access. If the file already contains servers, add the crunchbase entry to the existing mcpServers object.

   JSON

   {
     "mcpServers": {
       "crunchbase": {
         "url": "https://mcp.crunchbase.com"
       }
     }
   }

2. Connect your account. Save the file and restart Cursor. Open Customize → MCPs, find crunchbase, and follow the authentication prompt. Sign in with your Crunchbase account and choose Allow to approve access.

3. Test your connection. Open an Agent chat and run the test prompt below.

   Approve the Crunchbase tool call when prompted.

See Cursor's MCP setup instructions.

Connect through the Crunchbase plugin, or configure the MCP server directly. Use one method to avoid duplicate tools.

Desktop plugin

1. Install the plugin. Open Plugins, search for Crunchbase, and install the Crunchbase plugin.
2. Connect your account. Connect the plugin, sign in with your Crunchbase account, and approve the connection.
3. Test your connection. Start a new Codex chat and run the test prompt below.

Direct MCP setup for CLI and local Codex clients

1. Add the server. Add this entry to ~/.codex/config.toml. If it already exists, update the existing entry:

   TOML

   [mcp_servers.crunchbase]
   url = "https://mcp.crunchbase.com"

2. Connect your account. In your terminal, run:

   Bash

   codex mcp login crunchbase

   Complete the browser sign-in with your Crunchbase account.

3. Check the connection. Start a new Codex session and run /mcp.

4. Test your connection. Run the test prompt below.

Local Codex clients on the same host share this configuration. You do not need to create a custom OAuth client for the default browser sign-in flow.

See OpenAI's MCP setup instructions and plugin instructions.

Use a current Hermes Agent release and start the browser sign-in from your terminal.

1. Add the server. Run:

   Bash

   hermes mcp add crunchbase --url https://mcp.crunchbase.com --auth oauth

2. Connect your account. Complete the browser authorization when prompted. To start or repeat sign-in explicitly, run:

   Bash

   hermes mcp login crunchbase --flow browser

3. Check the connection. Run hermes mcp test crunchbase.

4. Test your connection. Start a Hermes chat and run the test prompt below.

You do not need to create a custom OAuth client for this terminal-initiated browser flow.

See Hermes' MCP configuration reference and CLI commands.

Back to AI tools ↑

Custom connectors with OAuth credentials

Google Gemini, Mistral Vibe, and Devin use Crunchbase's custom OAuth client setup. The same steps apply to other compatible clients that require a client ID and client secret. Crunchbase supports OAuth 2.1 with PKCE and does not support Dynamic Client Registration (DCR).

Create OAuth credentials

Create a separate OAuth client in Crunchbase for each custom integration, such as Gemini, Mistral, or Devin. Open the AI tool's custom connector setup first so you can obtain its exact OAuth callback (redirect) URL. If the tool does not show it, obtain it from the provider before registering; do not use the MCP server URL as the callback URL. You can create multiple clients.

1. Open the MCP integration settings. In Crunchbase, go to Account Settings → Integrations → MCP.
2. Start a client registration. Under Custom OAuth Client, click Create OAuth Client.
3. Name the client. Enter a descriptive client name so your workspace can identify the integration later.
4. Add the callback URL. Enter at least one callback URL from your client's MCP or connection settings, then click Add Callback URL. You can register up to 10 callback URLs per client. Callback URLs must use HTTPS, except for localhost or 127.0.0.1. Wildcards are not supported, and URLs must match exactly. You can add, remove, or update callback URLs later, up to the 10-URL limit.
5. Create the client. Click Create Custom OAuth Client.
6. Copy your credentials. Copy the client_id and client_secret from the client details and enter them in your client's connection settings with the MCP server URL.

Treat the client_secret like a password: don't share it or commit it to source control. If a secret is compromised, rotate it from the client's settings in Crunchbase.

If your client connects but tool calls fail with an authorization error, complete the OAuth flow in a browser when prompted; the server does not accept unauthenticated requests.

Connect Crunchbase as a custom app using pre-registered OAuth credentials.

1. Open the connection settings. At gemini.google.com, open Settings → Connected Apps. If needed, go through Personal Intelligence → Connected Apps.
2. Add the server. Under Custom apps, use the add-app field or Add a custom app and enter https://mcp.crunchbase.com.
3. Create OAuth credentials. Expand Advanced features → Show more. Obtain Gemini's exact OAuth callback URL from its setup or provider, then follow Create OAuth credentials in Crunchbase. Google's help article does not publish a callback URL.
4. Connect your account. Enter your Crunchbase client_id and client_secret in Gemini's credential fields, click Next, and complete the Crunchbase sign-in and authorization prompts.
5. Test your connection. Type @, select the connected Crunchbase app, and run the test prompt below.

See Google's custom app instructions for current availability and setup.

Connect Mistral Vibe Work using a custom connector and pre-registered OAuth credentials.

Before you start: custom connectors require administrator privileges in Vibe. On Free, Pro, and Student plans, the account owner is the administrator by default.

1. Open the connection settings. In Vibe Work, open Connectors, select + Add Connector, and switch to the Custom MCP Connector tab.
2. Add the server. Enter Crunchbase as the connector name and https://mcp.crunchbase.com as the server URL.
3. Create OAuth credentials. Obtain the callback URL from Vibe's connector setup, then follow Create OAuth credentials in Crunchbase.
4. Connect your account. Select Connect to detect authentication. Enter your Crunchbase client ID and client secret in the Client ID and Client Secret fields when prompted. Complete the Crunchbase sign-in and choose Allow. Each user signs in with their own Crunchbase account on first use.
5. Test your connection. Start a new chat, open Connectors, confirm Crunchbase is enabled, and run the test prompt below.

See Mistral's custom connector instructions. These steps describe Vibe Work's connector interface.

Connect Devin using a custom HTTP MCP server and pre-registered OAuth credentials.

1. Open the connection settings. In Devin, go to Customize → MCPs and add a custom MCP server.
2. Add the server. Name it Crunchbase, choose HTTP (Streamable HTTP), enter https://mcp.crunchbase.com, and select OAuth authentication.
3. Create OAuth credentials. Copy the OAuth callback URL shown under OAuth credentials. Devin documents https://api.devin.ai/mcp/oauth/callback for all deployments. Follow Create OAuth credentials in Crunchbase and register that callback URL.
4. Connect your account. Enter the Crunchbase client ID and secret in Devin's OAuth credentials fields. Choose Personal access so each person connects their own Crunchbase account. Save, then select Connect and complete the Crunchbase sign-in.
5. Test your connection. Use Test tools, then start a Devin session and run the test prompt below.

If you cannot add a server at your selected organization or enterprise scope, ask your Devin administrator for the appropriate permissions.

See Devin's custom MCP instructions.

Other MCP clients

Use a client that supports the server’s Streamable HTTP transport and compatible OAuth flow. Implementing MCP alone does not establish compatibility:

• Endpoint: https://mcp.crunchbase.com
• Transport: Streamable HTTP
• Authentication: OAuth 2.1 with PKCE. Sign-in uses your Crunchbase account.

Clients that support Client ID Metadata Documents (CIMD) connect directly, with no registration required. Dynamic Client Registration (DCR) is not supported.

If a client requires its own client ID and secret, follow Create OAuth credentials and enter those credentials in its custom connector settings. A client that only supports DCR, with neither CIMD nor manually supplied credentials, cannot use this setup.

Back to AI tools ↑

Test your connection

Start a new chat with Crunchbase enabled. In Gemini, type @ and select the custom app. In Perplexity, select Crunchbase from the connector menu or use @Crunchbase.

Use Crunchbase to find Anthropic's total funding to date and who led their most recent round.

Success looks like: the client calls a Crunchbase tool, returns data without an authentication error, and bases its answer on that result. A plausible answer alone does not verify the connection.

If authorization fails, reconnect Crunchbase and complete the browser sign-in flow.

Back to AI tools ↑

Next steps

• Getting Started with MCP: authentication and effective prompts
• Developer Reference: every tool the server exposes, with parameters and examples

Building an integration

For application developers, see Building a Crunchbase MCP Integration, Reliability, Errors, and Pagination, and Known MCP Limitations.