Crunchbase Search Results avatar
Crunchbase Search Results

Pricing

$29.00/month + usage

Go to Store
Crunchbase Search Results

Crunchbase Search Results

Developed by

SASWAVE

SASWAVE

Maintained by Community

Scrape crunchbase and Download ANY Crunchbase search results in a json file (companies, funding, acquisition, peoples ...). Only PRO plan needed

0.0 (0)

Pricing

$29.00/month + usage

6

Total users

333

Monthly users

39

Runs succeeded

>99%

Issues response

8.3 hours

Last modified

18 days ago

You can access the Crunchbase Search Results programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.

{
"mcpServers": {
"apify": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.apify.com/sse?actors=saswave/crunchbase-search-results",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with Crunchbase Search Results

You have a few options for interacting with the MCP server:

  • Use mcp.apify.com via mcp-remote from your local machine to connect and authenticate using OAuth or an API token (as shown in the JSON configuration above).

  • Set up the connection directly in your MCP client UI by providing the URL https://mcp.apify.com/sse?actors=saswave/crunchbase-search-results along with an API token (or use OAuth).

  • Connect to mcp.apify.com via Server-Sent Events (SSE), as shown below:

{
"mcpServers": {
"apify": {
"type": "sse",
"url": "https://mcp.apify.com/sse?actors=saswave/crunchbase-search-results",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}

You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.

If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.