Wrenfield AI Search Visibility

Wrenfield Data MCP

SEO and AI-search data, priced per result.

Keyword, domain, AI-visibility and lead data for AI agents, as remote MCP servers. Nothing to install or host.

What this is

Wrenfield Data publishes data tools as Apify Actors. This repo bundles them into three ready-made MCP servers (one per suite), served by the Apify MCP server at mcp.apify.com. Point your MCP client at a suite URL, sign in to Apify (OAuth) or pass an Apify API token, and each Actor appears as a tool with typed input and output schemas.

• No server to run. Apify hosts the MCP endpoint and runs the tools.
• Pay per result. Each tool charges for the results it returns, billed to your Apify account. Some tools add a small per-run or per-request fee, listed in the tables below. There's no subscription, and you don't need third-party API keys. The Apify Free plan includes a monthly usage credit.
• Capped spend. The per-Actor tools in these suites take only the Actor's input, so they have no spend-cap argument. To cap a single run from an agent, add Apify's generic call-actor tool to the suite URL and pass callOptions.maxTotalChargeUsd (details). REST callers can use the maxTotalChargeUsd query parameter.
• Also a plain API. Every tool is a normal Apify Actor you can call over REST, from Python or Node, or from n8n/Make/Zapier (examples).

Quick start

1. Get an Apify account (free) at console.apify.com/sign-up. This step is optional if your client supports OAuth, because you sign in when you connect.
2. Pick a suite URL below. All three can run side by side.
3. Add it to your client (Claude, Cursor, VS Code, ChatGPT, others).

Example prompts once connected:

"Get US search volume and CPC for 'crm software', 'best crm for small business' and 'free crm', and tell me which has the best volume-to-CPC ratio."

"Compare domain authority and organic traffic for hubspot.com, pipedrive.com and zoho.com."

"Ask ChatGPT and Perplexity 'What is the best CRM for a small business?' and tell me whether HubSpot is mentioned and which URLs are cited."

"Find the official domains for these 20 company names, then pull their contact emails and CMS."

1. SEO Data

Keyword research, domain-level SEO data, search trends and competitor ads. Keyword and domain metrics come from licensed sources (Google Ads Keyword Planner data and DataForSEO), not from scraping Ahrefs or Semrush.

https://mcp.apify.com?tools=wrenfield-data/keyword-search-volume,wrenfield-data/ai-search-volume-checker,wrenfield-data/domain-authority-traffic-checker,wrenfield-data/google-trends-scraper,wrenfield-data/google-ads-transparency-scraper,wrenfield-data/competitor-keywords,wrenfield-data/keyword-difficulty-checker,wrenfield-data/keyword-research-tool,wrenfield-data/seo-toolkit,wrenfield-data/google-autocomplete-keyword-expander,wrenfield-data/people-also-ask-scraper,wrenfield-data/keyword-gap-report,wrenfield-data/bulk-pagespeed-checker,wrenfield-data/amazon-keyword-research

Coming soon (being published on Apify Store this week; not callable yet):

• wrenfield-data--google-rank-tracker: Google positions per keyword with change since last run and AI Overview citation check

2. AI Search Visibility

Generative-engine optimization (GEO/AEO) data: run your prompts across AI assistants and see whether your brand is mentioned, how it's ranked and which URLs are cited, compared with your competitors.

https://mcp.apify.com?tools=wrenfield-data/ai-search-visibility-tracker,wrenfield-data/keyword-search-volume,wrenfield-data/ai-search-volume-checker,wrenfield-data/people-also-ask-scraper,wrenfield-data/ai-answer-scraper,wrenfield-data/agency-ai-visibility-reports

Coming soon (being published on Apify Store this week; not callable yet):

• wrenfield-data--google-rank-tracker: Google positions per keyword with change since last run and AI Overview citation check

3. Local Leads

Turn a list of businesses into a usable lead list: official domains, public contact details and the technology each site runs on.

https://mcp.apify.com?tools=wrenfield-data/website-contact-scraper,wrenfield-data/website-tech-stack-detector,wrenfield-data/domain-to-company,wrenfield-data/company-enrichment,wrenfield-data/company-name-to-domain,wrenfield-data/businesses-without-websites,wrenfield-data/google-maps-grid-rank-tracker,wrenfield-data/bulk-pagespeed-checker

4. Company Data

Company resolution for agents and data pipelines. Turn a company name into its official domain, checked against the live homepage and given a confidence score. Turn a domain or work email into the company behind it, then enrich it with firmographics, public contacts and tech stack. Free-mail domains and rows that don't resolve are not charged.

https://mcp.apify.com?tools=wrenfield-data/company-name-to-domain,wrenfield-data/domain-to-company,wrenfield-data/company-enrichment,wrenfield-data/website-tech-stack-detector,wrenfield-data/website-contact-scraper

More Wrenfield Data Actors

These Actors aren't in a suite, but you can add any of them to a suite URL (...,wrenfield-data/<name>) or call them over REST.

Prices pulled from Apify Store on 2026-11-03. They are Apify Free-plan rates; paid Apify plans get lower tiered rates. Each Actor's Store page is the authoritative price list. A "run start" fee is charged once per call.

Connect your client

Each suite URL is a standard Streamable HTTP MCP endpoint. You can authenticate in either of two ways:

• OAuth (recommended): add just the URL. On first connect your browser opens so you can sign in to Apify and approve access.
• Bearer token: send Authorization: Bearer <YOUR_APIFY_TOKEN>. Get the token from Apify Console → Settings → API & Integrations. Keep it out of git.

Ready-made files for every client below are in configs/.

Claude Desktop and Claude Code

Claude Desktop (remote connector): go to Settings → Connectors → Add custom connector, paste a suite URL and sign in to Apify. Availability depends on your Claude plan.

Claude Desktop (local, any plan): merge configs/claude-desktop.json into claude_desktop_config.json and restart Claude. This runs Apify's open-source stdio server (@apify/actors-mcp-server, Node 18+) with the same tools:

{
  "mcpServers": {
    "wrenfield-seo": {
      "command": "npx",
      "args": ["-y", "@apify/actors-mcp-server@latest", "--tools",
               "wrenfield-data/keyword-search-volume,wrenfield-data/domain-authority-traffic-checker,wrenfield-data/google-trends-scraper,wrenfield-data/google-ads-transparency-scraper"],
      "env": { "APIFY_TOKEN": "<YOUR_APIFY_TOKEN>" }
    }
  }
}

Claude Code: see configs/claude-code.sh. For example:

claude mcp add --transport http wrenfield-seo \
  "https://mcp.apify.com?tools=wrenfield-data/keyword-search-volume,wrenfield-data/domain-authority-traffic-checker,wrenfield-data/google-trends-scraper,wrenfield-data/google-ads-transparency-scraper" \
  --header "Authorization: Bearer $APIFY_TOKEN"

Cursor

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project). See configs/cursor.json. Cursor opens the Apify sign-in on first use.

{
  "mcpServers": {
    "wrenfield-seo": {
      "url": "https://mcp.apify.com?tools=wrenfield-data/keyword-search-volume,wrenfield-data/domain-authority-traffic-checker,wrenfield-data/google-trends-scraper,wrenfield-data/google-ads-transparency-scraper"
    }
  }
}

To use a token instead, add "headers": { "Authorization": "Bearer <YOUR_APIFY_TOKEN>" }.

VS Code (GitHub Copilot)

Save configs/vscode.json as .vscode/mcp.json. VS Code prompts once for the token and stores it securely:

{
  "inputs": [{ "type": "promptString", "id": "apify-token", "description": "Apify API token", "password": true }],
  "servers": {
    "wrenfield-seo": {
      "type": "http",
      "url": "https://mcp.apify.com?tools=wrenfield-data/keyword-search-volume,wrenfield-data/domain-authority-traffic-checker,wrenfield-data/google-trends-scraper,wrenfield-data/google-ads-transparency-scraper",
      "headers": { "Authorization": "Bearer ${input:apify-token}" }
    }
  }
}

To use OAuth instead, remove headers (and inputs).

ChatGPT

On plans and workspaces where custom MCP connectors (developer mode) are enabled, go to Settings → Apps (or Plugins) → Create / Add custom MCP server. Paste a suite URL, choose OAuth, then sign in to Apify. Availability and menu names depend on your ChatGPT plan; see OpenAI's guide.

Other clients

• Any client that supports remote MCP: use configs/generic-oauth.json or configs/generic-bearer.json.
• Windsurf: use configs/windsurf.json (serverUrl).
• Cline: use configs/cline.json ("type": "streamableHttp").
• Clients that only support stdio: run npx -y @apify/actors-mcp-server --tools wrenfield-data/<actor>,... with APIFY_TOKEN set.
• AI coding agents that install servers for you can follow llms-install.md.

Using the tools from an agent

• Each suite also loads Apify's helper tools get-actor-run, get-dataset-items, get-key-value-store-record and abort-actor-run. If a long run doesn't finish within the call, fetch its results with get-dataset-items.
• Spend caps: the per-Actor tools (for example wrenfield-data--keyword-search-volume) accept only the Actor's input and don't expose callOptions, so they can't cap spend per call. To cap a run, add call-actor to the URL's tools= list (for example ?tools=call-actor,wrenfield-data/keyword-search-volume) and call it with actor: "wrenfield-data/keyword-search-volume", the Actor input in input, and callOptions: { "maxTotalChargeUsd": 1 }. call-actor returns the run status and storage IDs, not the rows; read them with get-dataset-items.
• Results are JSON rows with stable field names. Each Actor's Store page documents its input and output schema.
• Optional: add &telemetry-enabled=false to a URL to opt out of Apify MCP telemetry.

REST, Python and Node

Every tool is a regular Apify Actor (wrenfield-data~<actor-name> in the API). The simplest call is run-sync-get-dataset-items, which runs the Actor and returns its results in one request (runs must finish within 300 s).

curl -s -X POST \
  "https://api.apify.com/v2/acts/wrenfield-data~keyword-search-volume/run-sync-get-dataset-items?maxTotalChargeUsd=1" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"keywords": ["crm software", "free crm"], "location": "United States", "language": "English"}'

Instant keyword volume (no run to start). Keyword Search Volume also runs as a warm HTTP API (Apify Standby). Agents and n8n/Make/Zapier HTTP nodes can call it directly and get rows back in under a second when warm (0.5–0.8 s measured Nov 3, 2026). Prices are the same as a normal run:

curl -s "https://wrenfield-data--keyword-search-volume.apify.actor/volume?keywords=crm%20software,free%20crm&location=United%20States" \
  -H "Authorization: Bearer $APIFY_TOKEN"
# also: GET /ideas?keywords=seed&maxIdeas=50 · POST / with the normal input JSON · GET / for usage

The response is {"items": [...], "summary": {...}, "elapsedMs": ...}. 400, 429 and 503 responses are never charged. The OpenAPI spec is in the Actor's Server tab on Apify.

Instant company domain lookup. Company Name to Domain has the same kind of warm endpoint: GET https://wrenfield-data--company-name-to-domain.apify.actor/domain?name=Stripe (or ?companies=a,b&country=DE, up to 50) returns the verified official domain, confidence, LinkedIn and logo. A fresh lookup takes about 1–10 s (the homepage is checked live), and a repeat takes about 0.5 s. It is charged per resolved company, like a normal run.

import os, requests

r = requests.post(
    "https://api.apify.com/v2/acts/wrenfield-data~domain-authority-traffic-checker/run-sync-get-dataset-items",
    params={"maxTotalChargeUsd": 1},
    headers={"Authorization": f"Bearer {os.environ['APIFY_TOKEN']}"},
    json={"domains": ["hubspot.com", "pipedrive.com"]},
    timeout=320,
)
r.raise_for_status()
for row in r.json():
    print(row["domain"], row.get("organic_traffic"), row.get("domain_rank"))

const res = await fetch(
  "https://api.apify.com/v2/acts/wrenfield-data~website-tech-stack-detector/run-sync-get-dataset-items?maxTotalChargeUsd=1",
  {
    method: "POST",
    headers: { Authorization: `Bearer ${process.env.APIFY_TOKEN}`, "Content-Type": "application/json" },
    body: JSON.stringify({ urls: ["wordpress.org", "allbirds.com"] }),
  },
);
for (const row of await res.json()) console.log(row.domain, row.technologies);

More in examples/: curl scripts, Python (requests and apify-client) and Node (fetch and apify-client).

Repository layout

README.md            this file
suites.json          source of truth: which Actors are in each suite
configs/             copy-paste MCP configs per client
registry/<suite>/    server.json for the official MCP Registry
examples/            curl, Python and Node examples
assets/              logo, suite icons, tool icons
scripts/generate.py  regenerates configs, registry files and README tables from suites.json
llms-install.md      setup notes for AI coding agents

To change a suite, edit suites.json and run python3 scripts/generate.py. The script reads only public Apify Store data and refuses to list any Actor that isn't public.

Acceptable use

The tools use public web pages and licensed data sources only, and none of them log in to websites. Lead tools return business contact details that are publicly listed. You are responsible for following GDPR, CAN-SPAM, TCPA and similar rules when you contact anyone.

About

Wrenfield Data builds SEO, AI-search and lead data tools, priced per result.

• Website: wrenfielddata.com
• Apify Store: apify.com/wrenfield-data
• YouTube: @wrenfielddata
• Contact: hello@wrenfielddata.com
• Bugs and requests: GitHub issues, or the Issues tab on each Actor's Store page

The MCP endpoint is operated by Apify (apify/apify-mcp-server). Wrenfield Data is an independent Apify Store publisher and isn't affiliated with Apify, Anthropic, OpenAI or Google. Product names are trademarks of their owners.

License

MIT. This covers the configs, examples and docs in this repo. Use of the tools is billed through Apify under Apify's terms.

Links to apify.com in this README carry the Wrenfield Data Apify affiliate ref (fpr). It does not change your price.