Crunchbase MCP Server

A Model Context Protocol (MCP) server that provides access to Crunchbase data for AI assistants. This server allows AI assistants to search for companies, get company details, funding information, acquisitions, and people data from Crunchbase.

Features

• Search for companies based on various criteria
• Get detailed information about specific companies
• Retrieve funding rounds for companies
• Get acquisition data
• Search for people associated with companies

Prerequisites

• Node.js (v16 or higher)
• A Crunchbase API key

Installation

1. Clone the repository:

bash git clone https://github.com/Cyreslab-AI/crunchbase-mcp-server.git cd crunchbase-mcp-server

1. Install dependencies:

bash npm install

1. Build the project:

bash npm run build

Configuration

The server requires a Crunchbase API key to function. You can obtain an API key by signing up for the Crunchbase API.

Setting up the API Key

Set the API key as an environment variable:

bash export CRUNCHBASE_API_KEY=your_api_key_here

MCP Configuration

You can use the included setup script to automatically configure the MCP server:

bash

Build the project first

npm run build

Run the setup script

npm run setup

The setup script will:

1. Ask for your Crunchbase API key
2. Find your MCP settings file (or create a new one)
3. Add the Crunchbase MCP server to your settings

Alternatively, you can manually add it to your MCP configuration file:

{ "mcpServers": { "crunchbase": { "command": "node", "args": ["/path/to/crunchbase-mcp-server/build/index.js"], "env": { "CRUNCHBASE_API_KEY": "your_api_key_here" }, "disabled": false, "autoApprove": [] } } }

Usage

Running the Server

Start the server:

bash npm start

For development with automatic reloading:

bash npm run dev

Available Tools

The server exposes the following tools:

1. search_companies - Search for companies based on various criteria

2. Parameters:

   • query (optional): Search query (e.g., company name, description)
   • location (optional): Filter by location (e.g., "San Francisco", "New York")
   • category (optional): Filter by category (e.g., "Artificial Intelligence", "Fintech")
   • founded_after (optional): Filter by founding date (YYYY-MM-DD)
   • founded_before (optional): Filter by founding date (YYYY-MM-DD)
   • status (optional): Filter by company status (e.g., "active", "closed")
   • limit (optional): Maximum number of results to return (default: 10)

3. get_company_details - Get detailed information about a specific company

4. Parameters:

   • name_or_id (required): Company name or UUID

5. get_funding_rounds - Get funding rounds for a specific company

6. Parameters:

   • company_name_or_id (required): Company name or UUID
   • limit (optional): Maximum number of results to return (default: 10)

7. get_acquisitions - Get acquisitions made by or of a specific company

8. Parameters:

   • company_name_or_id (optional): Company name or UUID
   • limit (optional): Maximum number of results to return (default: 10)

9. search_people - Search for people based on various criteria

10. Parameters:
    • query (optional): Search query (e.g., person name)
    • company (optional): Filter by company name
    • title (optional): Filter by job title
    • limit (optional): Maximum number of results to return (default: 10)

Available Resources

The server also exposes the following resources:

1. Trending Companies - List of trending companies on Crunchbase

2. URI: crunchbase://trending/companies

3. Company Details - Detailed information about a specific company

4. URI Template: crunchbase://companies/{name}

5. Company Funding Rounds - Funding rounds for a specific company

6. URI Template: crunchbase://companies/{name}/funding

7. Company Acquisitions - Acquisitions made by or of a specific company

8. URI Template: crunchbase://companies/{name}/acquisitions

Example Queries

Here are some examples of how an AI assistant might use this MCP server:

1. Search for AI companies in San Francisco:

{ "query": "AI", "location": "San Francisco", "limit": 5 }

1. Get details for a specific company:

{ "name_or_id": "OpenAI" }

1. Get funding rounds for a company:

{ "company_name_or_id": "Anthropic" }

1. Search for CEOs at tech companies:

{ "title": "CEO", "limit": 10 }

License

MIT

Contact

For questions or support, please contact: contact@cyreslab.ai

WIKIPEDIA: XMLHttpRequest (XHR) is an API in the form of a JavaScript object whose methods transmit HTTP requests from a web browser to a web server. The methods allow a browser-based application to send requests to the server after page loading is complete, and receive information back. XMLHttpRequest is a component of Ajax programming. Prior to Ajax, hyperlinks and form submissions were the primary mechanisms for interacting with the server, often replacing the current page with another one.

== History == The concept behind XMLHttpRequest was conceived in 2000 by the developers of Microsoft Outlook. The concept was then implemented within the Internet Explorer 5 browser (1999). However, the original syntax did not use the XMLHttpRequest identifier. Instead, the developers used the identifiers ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"). As of Internet Explorer 7 (2006), all browsers support the XMLHttpRequest identifier. The XMLHttpRequest identifier is now the de facto standard in all the major browsers, including Mozilla's Gecko layout engine (2002), Safari 1.2 (2004) and Opera 8.0 (2005).

=== Standards === The World Wide Web Consortium (W3C) published a Working Draft specification for the XMLHttpRequest object on April 5, 2006. On February 25, 2008, the W3C published the Working Draft Level 2 specification. Level 2 added methods to monitor event progress, allow cross-site requests, and handle byte streams. At the end of 2011, the Level 2 specification was absorbed into the original specification. At the end of 2012, the WHATWG took over development and maintains a living document using Web IDL.

== Usage == Generally, sending a request with XMLHttpRequest has several programming steps.

Create an XMLHttpRequest object by calling a constructor: Call the "open" method to specify the request type, identify the relevant resource, and select synchronous or asynchronous operation: For an asynchronous request, set a listener that will be notified when the request's state changes: Initiate the request by calling the "send" method: Respond to state changes in the event listener. If the server sends response data, by default it is captured in the "responseText" property. When the object stops processing the response, it changes to state 4, the "done" state. Aside from these general steps, XMLHttpRequest has many options to control how the request is sent and how the response is processed. Custom header fields can be added to the request to indicate how the server should fulfill it, and data can be uploaded to the server by providing it in the "send" call. The response can be parsed from the JSON format into a readily usable JavaScript object, or processed gradually as it arrives rather than waiting for the entire text. The request can be aborted prematurely or set to fail if not completed in a specified amount of time.

== Cross-domain requests ==

In the early development of the World Wide Web, it was found possible to brea