No Infrastructure Needed
No proxy setup, rendering stack, or scaling layer to maintain in your MCP client.
Connect via Streamable HTTP and run scrape, extract, search, social, and app-store workflows from a single MCP endpoint.
No proxy setup, rendering stack, or scaling layer to maintain in your MCP client.
Use the same endpoint for crawling, extraction, social APIs, and app store intelligence.
MCP calls consume credits exactly like standard API calls. No hidden MCP surcharge.
Switch between categories and plug MCP tools directly into your agent workflows.
Use CrawlKit MCP tools for core scraping, extraction, and search pipelines.
Usage-based credits with clear volume tiers and no hidden infrastructure fees.
Transparent rates by monthly volume. Your per-credit cost drops as usage increases.
| Usage (credits / month) | Price / 1K credits |
|---|---|
| 0 - 25K | $0.96 |
| 25K - 100K | $0.77 |
| 100K - 250K | $0.67 |
| 250K+ | From $0.58 |
Example: 184,320 credits costs about $132.71/month.
Switch services and preview the payloads your application will actually consume.
1{2 "success": true,3 "data": {4 "id": "kat***hig***s-a******",5 "name": "Katie H*****s",6 "first_name": "Katie",7 "last_name": "H*****s",8 "city": "Braintree, England, UK",9 "location": "Braintree",10 "country_code": "GB",11 "followers": 548,12 "connections": 500,13 "avatar": "https://static.licdn.com/...",14 "banner_image": "https://static.licdn.com/...",15 "linkedin_num_id": "2099250",16 "influencer": false,17 "default_avatar": true,18 "volunteer_experience": [{ ... }],19 "people_also_viewed": [{ ... }],20 "activity": [{ ... }],21 "creditsUsed": 2,22 "creditsRemaining": 984623 }24}
Everything you need before using CrawlKit MCP in production.
Use https://api.crawlkit.sh/mcp with Streamable HTTP transport in your MCP client configuration.
Set Authorization header as Bearer ck_xxx inside your mcpServers.crawlkit.headers object.
MCP calls consume credits using the same endpoint pricing as direct REST API requests.
Scrape, extract, search, LinkedIn, Instagram, TikTok, Play Store, App Store, plus credit and API key validation flows.
No. Credits never expire and remain available across all supported CrawlKit endpoints.
Keep the key only in your MCP client config, never commit it to public repos, and rotate it if exposure is suspected.