Connect the data to your own LLM
Generate a personal API key and plug the entire crowdfunding dataset into your own model—Claude, Cursor, ChatGPT, or any MCP-capable client. Then just ask, in plain language, and your model pulls and analyzes the data for you.
What is this?
Traditional web pages are centralized: you see what the page shows you. This gives you the raw data instead, under your account, so your own model can do flexible, personalized analysis. Three pieces work together:
Your credential. A browser logs in with a cookie; a program proves it is you with an "ks_…" key. Both MCP and CLI sit on top of it.
A "data socket" for AI clients (Cursor / Claude). Paste one config and your own model can call our data as tools—this is the part you actually want.
A terminal command a human types to query or export data. Same API underneath; handy for scripts. (Not shipped yet.)
How to use it (3 steps)
- 1Generate a key
Open Settings → API / MCP Access and click Generate. Copy the "ks_…" key—it is shown only once.
- 2Add the MCP config
Paste the snippet below into your Cursor / Claude MCP settings and replace KS_API_KEY with your key.
- 3Ask your model
In natural language, e.g. "Analyze the success rate of tech campaigns over the last 30 days." Your model calls the tools and reasons over the results.
{
"mcpServers": {
"kicksonar": {
"command": "npx",
"args": [
"-y",
"ks-mcp"
],
"env": {
"KS_API_KEY": "ks_your_key_here",
"KS_BASE_URL": "https://your-domain"
}
}
}
}Replace KS_API_KEY with the key from your Settings page.
Cursor: Settings → MCP (or edit ~/.cursor/mcp.json). Claude Desktop: edit claude_desktop_config.json and restart.
Available tools (read-only)
search_projectsSearch / filter campaigns by platform, category, country, state, text, sort, pagination (≤100 rows/call).get_projectFull detail for one project id, plus similar projects.get_trendsMonthly trend series: launches, success rate, pledged.get_leaderboardTop projects / creators / agencies with summary totals.get_statsAggregate totals, success rate, state distribution, live summary.Quotas & security
Per-user rate limits identical to the website, plus a per-key daily request cap (resets 00:00 UTC) so no single key can bulk-export the dataset.
Only the hash of a key is stored; plaintext is shown once. Revoke any key anytime. Read-only data endpoints only—no sync/admin/write access.
Sign in to get started
Keys are managed on the Settings page.