Guide
Use clearpull tools from Claude or Cursor
Claude, Cursor and other AI assistants can run our data tools for you through Apify’s MCP server. You ask in plain words, for example “Which of these 20 keywords are rising in the UK?”, and the assistant runs the tool on Apify, reads the results and answers. Setup takes about five minutes, and you don’t write any code.
This guide uses our data tools on the Apify Store. Every step works with a free Apify account.
What you need
- An Apify account. The free plan includes monthly credit, which is enough to try every tool below.
- An AI assistant that supports MCP: Claude on the web, the Claude desktop app, Claude Code, Cursor, or another MCP client such as VS Code.
MCP (Model Context Protocol) is the standard way for AI assistants to use outside tools. Apify runs a hosted MCP server, so there’s nothing to install.
The tools you can use
| Tool | Ask it things like |
|---|---|
| Google Trends Scraper | “Which of these keywords are rising in the US this year?” |
| Google Autocomplete | “What questions do people in the UK type about heat pumps?” |
| Google Play Scraper | “Compare the ratings and installs of these five apps.” |
| Yahoo Finance | “Show the quote and key statistics for AAPL, MSFT and NVDA.” |
| AI Image Upscaler | “Upscale these three product photos 4x.” |
1. Choose the server address
Apify’s MCP server lives at https://mcp.apify.com. On its own, that address gives the assistant general tools for searching the whole Apify Store and running any Actor. To give it exactly our five live tools, list them after ?tools=:
https://mcp.apify.com?tools=clearpull/google-trends-scraper,clearpull/google-autocomplete-scraper,clearpull/google-play-scraper,clearpull/yahoo-finance,clearpull/image-upscaler
- Each tool appears on its own in the assistant, named like
clearpull--google-trends-scraper. The server also adds the small helper tools the assistant needs to read the results, such asget-dataset-items. - The list replaces the default set. To keep Store search as well, start the list with
actors,docs,. - Only need one tool? Use just its name, for example
https://mcp.apify.com?tools=clearpull/google-trends-scraper. Fewer tools keep the assistant’s choices clear.
2. Connect your assistant
Claude on the web or in the desktop app
- Open Customize, then Connectors (in some versions it’s Settings → Connectors). Choose Add, then Add custom connector.
- Name it
clearpull toolsand paste the address from step 1 as the MCP server URL. - Choose Continue, keep the settings Claude detects, and choose Add.
- Sign in to Apify, pick your account and choose Allow access. Apify’s docs say to expect a warning that the app was registered automatically. That’s normal for Claude.
A custom connector can’t be edited. To change its tools, remove it and add it again with a new address. On Team and Enterprise plans, only an owner can add one, and it’s added for the whole organization.
Claude Code
Run this in a terminal, with the whole address in quotes:
claude mcp add --transport http clearpull "https://mcp.apify.com?tools=clearpull/google-trends-scraper,clearpull/google-autocomplete-scraper,clearpull/google-play-scraper,clearpull/yahoo-finance,clearpull/image-upscaler"
Then type /mcp in Claude Code, choose clearpull and sign in to Apify in the browser window that opens.
Cursor
Add the server to ~/.cursor/mcp.json for every project, or to .cursor/mcp.json in one project:
{
"mcpServers": {
"clearpull": {
"url": "https://mcp.apify.com?tools=clearpull/google-trends-scraper,clearpull/google-autocomplete-scraper,clearpull/google-play-scraper,clearpull/yahoo-finance,clearpull/image-upscaler"
}
}
}
Open Cursor’s settings, find clearpull in the MCP section and connect it. Sign in to Apify when the browser opens.
Other assistants
VS Code and most other MCP clients take the same address. If yours can’t sign in through a browser, send your Apify API token in a header instead: Authorization: Bearer <your token>. You’ll find the token in Apify Console under Settings → API & Integrations. Keep it in the client’s settings only, never in a shared file, a repository or a chat.
3. Ask for what you need
Start a new chat, so the assistant sees the new tools, and ask in plain words. Prompts that work well:
- “Use the Google Trends tool with the summary output format. Which of these 20 keywords are rising in the US over the past 12 months? Sort them by change.” The summary format (
outputFormat: "summary") returns each keyword’s trend direction, change, peak and top regions instead of hundreds of data points. - “Get Google autocomplete questions for heat pumps in the UK, then group them by topic.”
- “Compare the ratings, star histograms and install counts of these five apps on Google Play in Germany.”
- “Get quotes and key statistics for AAPL, MSFT and NVDA and put them in a table.” Prices are at least 15 minutes old.
- “Upscale these product photos 4x and give me the download links.”
Each request starts a run on Apify. Most finish in seconds to a couple of minutes, then the assistant reads the results. If it only reports a run ID, ask it to “get the dataset items for that run”.
What it costs
- You pay per result, not per month. Each tool charges per keyword, suggestion, app, quote or image. The price is on each tool’s Store page, under Pricing.
- Runs come out of your Apify account, including the free plan’s monthly credit. Every run, with its cost, is listed in Apify Console under Runs.
- Start small. Try a handful of keywords or apps first, then scale up once the answer looks right.
If something goes wrong
- The tools don’t show up: start a new chat, and check that the connector is switched on for it.
- Sign-in fails or keeps repeating: remove the connector and add it again. That starts a fresh sign-in.
- The assistant uses a different tool: name the tool in your request, for example “use the clearpull Google Play tool”.
- The answer is cut short: ask for fewer items per run, or for the summary format where the tool has one.
Disclosure: we (clearpull) built these tools. Apify runs them and bills each run to your Apify account.
Need data from another public source, or a different setup? Get in touch.