crunchbase

This Crunchbase MCP Server exposes a set of tools that let an AI assistant query Crunchbase data through a consistent MCP interface. The primary tools include searching for companies, retrieving detailed company profiles, obtaining funding rounds, listing acquisitions, and searching for people associated with companies. The server also exposes convenient URI resources for trending companies and specific entity details, enabling quick lookups within your agent workflows. To use the server, start it with your chosen MCP runner configuration (for example via node pointing to the built index.js) and supply your Crunchbase API key when prompted or via environment variables. The available tools are designed as structured actions: search_companies, get_company_details, get_funding_rounds, get_acquisitions, and search_people, each accepting parameters described in the documentation. You can combine these tools to build strategies for finding potential companies, following funding histories, or identifying key personnel connected to a company.

Prerequisites:

• Node.js (v16 or higher) and npm installed on your machine
• A Crunchbase API key

Installation steps:

1. Clone the repository: git clone https://github.com/Cyreslab-AI/crunchbase-mcp-server.git cd crunchbase-mcp-server

2. Install dependencies: npm install

3. Build the project (if a build step is defined): npm run build

4. Obtain a Crunchbase API key from the Crunchbase API documentation and prepare to supply it via environment variable CRUNCHBASE_API_KEY.

5. Start the server (example): npm start

If you prefer to use the MCP setup script mentioned in the README, follow: npm run setup

Note: If you deploy in a container or different environment, ensure the environment variable CRUNCHBASE_API_KEY is set in your runtime environment.

Tips and considerations:

• Ensure your Crunchbase API key has the necessary permissions for the endpoints used by the MCP server.
• The example MCP configuration includes an explicit CRUNCHBASE_API_KEY environment variable. When deploying, avoid hardcoding keys in code; use a secure secret manager or runtime environment configuration.
• If you modify the server configuration or add new MCP services, run npm run build (if applicable) before starting the server in production.
• Check the server logs if an endpoint returns errors to confirm that the API key is valid and that you have network access to Crunchbase APIs.
• The available tools are designed to be invoked with JSON-like parameter objects; ensure your agent passes the correct keys (e.g., query, location, limit) as described in the tool documentation.
• If you need to expose additional endpoints (like more granular filters), consider updating the MCP server code and rebuilding the project, then updating the MCP config accordingly.