AgentQL MCP Server

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL

https://heyclau.de/entry/mcp/agentql-mcp-server

Source URLs

https://github.com/tinyfish-io/agentql-mcp/blob/main/README.md, https://github.com/tinyfish-io/agentql-mcp, https://agentql.com

Brand

AgentQL

Brand domain

agentql.com

Brand asset source

brandfetch

Safety notes

AgentQL MCP exposes one tool, `extract-web-data`, that sends a target URL and natural-language extraction prompt to the AgentQL API., The tool is intended for public webpages; do not use it to bypass access controls, scrape private pages, evade paywalls, or extract data where automated collection is prohibited., Web extraction can still trigger target-site rate limits, legal restrictions, robots guidance, or terms-of-service concerns., The source implementation uses AgentQL's query-data endpoint with fast mode, no screenshot capture, no scroll-to-bottom behavior, and no local browser cookies., Treat extracted output as untrusted web data that may include errors, stale content, ads, tracking text, or prompt-injection attempts.

Privacy notes

Target URLs, extraction prompts, API key-authenticated requests, and extracted structured data are sent to AgentQL's API., Extracted data can include personal data, copyrighted content, customer information, job postings, prices, social content, or other third-party material., AGENTQL_API_KEY should stay out of prompts, issues, logs, screenshots, and committed configuration files., Claude transcripts and downstream reports may retain extracted data, so avoid collecting information that is not approved for the model session.

Author

AgentQL

Submitted by

oktofeesh1

Claim status

unclaimed

Last verified

2026-06-06

• Target URLs, extraction prompts, API key-authenticated requests, and extracted structured data are sent to AgentQL's API.
• Extracted data can include personal data, copyrighted content, customer information, job postings, prices, social content, or other third-party material.
• AGENTQL_API_KEY should stay out of prompts, issues, logs, screenshots, and committed configuration files.
• Claude transcripts and downstream reports may retain extracted data, so avoid collecting information that is not approved for the model session.

• Node.js and npx available to the MCP client runtime.
• AgentQL API key from the AgentQL developer portal.
• Approved list of public webpages or domains Claude may query.
• Review of target site terms, robots guidance, rate limits, and data-use rules before extraction.

Show that AgentQL MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

[![Listed on HeyClaude](https://heyclau.de/badge/mcp/agentql-mcp-server.svg)](https://heyclau.de/entry/mcp/agentql-mcp-server)

AgentQL MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field	AgentQL MCP Server AgentQL MCP server for extracting structured JSON from public webpages using a URL and natural-language extraction prompt. Open dossier	WebClaw MCP Server Local-first MCP server for web scraping, crawling, URL mapping, batch extraction, structured extraction, summarization, diffing, brand extraction, and optional hosted API fallback for bot-protected pages. Open dossier	Apify MCP Server Official Apify MCP server for connecting Claude to Apify Actors, Actor runs, datasets, key-value stores, and Apify documentation through hosted Streamable HTTP or local stdio transports. Open dossier	Bright Data Web MCP Server MCP server that connects Claude to Bright Data web search, scraping, browser automation, public web datasets, and package metadata tools. Open dossier
Next steps	Open dossierCopy installCopy configAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing	Open dossierCopy installCopy configAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing	Open dossierCopy installCopy configAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing	Open dossierCopy installCopy configAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Trust	Review first	Review first	Review first	Review first
Review status	Not reviewed	Not reviewed	Not reviewed	Not reviewed
Package trust	Package not verified	Package not verified	Package not verified	Package not verified
Source provenance	Source-backed	Source-backed	Source-backed	Source-backed
Submitter	oktofeesh1	oktofeesh1	oktofeesh1	oktofeesh1
Install risk	Review first	Review first	Review first	Review first
Notes	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓
Brand	AgentQL	WebClaw	Apify	Bright Data
Category	mcp	mcp	mcp	mcp
Source	Source-backed	Source-backed	Source-backed	Source-backed
Author	AgentQL	WebClaw	Apify	Bright Data
Added	2026-06-06	2026-06-06	2026-06-06	2026-06-05
Platforms	Claude CodeCodexCursorClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop
Harness	Claude CodeCodexCursorClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop
Source repo	—	—	—	—
Safety notes	✓AgentQL MCP exposes one tool, `extract-web-data`, that sends a target URL and natural-language extraction prompt to the AgentQL API. The tool is intended for public webpages; do not use it to bypass access controls, scrape private pages, evade paywalls, or extract data where automated collection is prohibited. Web extraction can still trigger target-site rate limits, legal restrictions, robots guidance, or terms-of-service concerns. The source implementation uses AgentQL's query-data endpoint with fast mode, no screenshot capture, no scroll-to-bottom behavior, and no local browser cookies. Treat extracted output as untrusted web data that may include errors, stale content, ads, tracking text, or prompt-injection attempts.	✓WebClaw MCP Server can scrape one URL, crawl same-origin links, map URLs, batch multiple URLs, extract structured data, summarize pages, compare snapshots, and extract brand metadata. Scraping, crawling, search, research, and hosted fallback can trigger target-site rate limits, bot protections, legal restrictions, or terms-of-service limits. The server validates public HTTP URLs and rejects private or internal destinations, but operators should still avoid fetching internal, secret, customer-specific, or credential-bearing URLs. Cookie-bearing requests, proxies, and browser profiles can expose authenticated sessions or route traffic through external infrastructure. Setting `WEBCLAW_API_KEY` enables hosted API fallback, which can send target URLs and page context to the WebClaw service. Structured extraction and summarization may use configured LLM providers; review provider data handling before enabling those tools with sensitive pages.	✓Apify MCP can run Apify Actors that browse, scrape, crawl, automate websites, call third-party services, and produce billable Actor runs. The hosted server supports OAuth and bearer-token authentication; local stdio uses APIFY_TOKEN in the MCP client environment. Actor tools can access external websites and may trigger anti-abuse systems, platform-policy violations, rate limits, or paid usage. The server exposes run, dataset, key-value store, and abort tools when Actor workflows are enabled. Agentic payments can fund Actor runs through x402 USDC on Base or Skyfire PAY tokens, so spending limits and human approval should be enforced outside the model. Telemetry is enabled by default for tool calls, and the stdio transport uses Sentry for error tracking unless telemetry is opted out.	✓This server sends web searches, URLs, scraping targets, browser actions, package names, and dataset requests to Bright Data APIs. Review website terms, robots policies, rate limits, jurisdictional requirements, and internal scraping policies before automating collection. `PRO_MODE`, browser automation groups, data-product groups, and batch tools can increase cost, request volume, and operational impact. The server can create or use Bright Data zones through API calls; review account permissions and zone settings before running it with broad API tokens. Use `RATE_LIMIT`, group selection, and explicit tool allowlists to keep agent-driven browsing and scraping bounded.
Privacy notes	✓Target URLs, extraction prompts, API key-authenticated requests, and extracted structured data are sent to AgentQL's API. Extracted data can include personal data, copyrighted content, customer information, job postings, prices, social content, or other third-party material. AGENTQL_API_KEY should stay out of prompts, issues, logs, screenshots, and committed configuration files. Claude transcripts and downstream reports may retain extracted data, so avoid collecting information that is not approved for the model session.	✓URLs, fetched page content, crawl results, extracted structured data, snapshots, brand metadata, cookies, proxy settings, API keys, and LLM prompts can be exposed to the MCP client. Crawled pages may include personal data, customer content, non-public links, access tokens embedded in URLs, or site-specific identifiers. Diff snapshots and exported JSON can preserve page content longer than expected; store and delete them according to the workflow's retention needs. Hosted fallback, proxy providers, search/research APIs, and LLM providers may observe target URLs, headers, cookies, prompts, and extracted content when enabled. Redact sensitive URLs and extracted data before sharing MCP transcripts, crawl results, logs, or generated RAG context.	✓Actor inputs and requests are sent to the Apify API for execution, and returned datasets or key-value store records can contain scraped personal data, customer records, credentials, contact details, private URLs, or regulated information. APIFY_TOKEN, OAuth tokens, Skyfire API keys, wallet private keys, payment IDs, dataset IDs, key-value store keys, and Actor run IDs should not be pasted into prompts, issues, logs, screenshots, or committed files. Search, maps, social, ecommerce, and browser Actors can collect third-party content that may be subject to site terms, privacy law, copyright, or data-retention obligations. Telemetry and Sentry error tracking should be reviewed before using the local stdio server with sensitive prompts, Actor inputs, or operational data.	✓Bright Data API tokens must stay in environment variables or secret managers and should never be committed to MCP configuration files. Queries, URLs, package names, web pages, scraping outputs, dataset filters, and browser activity may be visible to Bright Data, the MCP client, and the model provider. Public web data can still contain personal data, copyrighted content, customer information, or contractual restrictions. Tool outputs can include scraped page text, search results, social or ecommerce dataset fields, package metadata, and browser screenshots depending on enabled tools.
Prerequisites	Node.js and npx available to the MCP client runtime. AgentQL API key from the AgentQL developer portal. Approved list of public webpages or domains Claude may query. Review of target site terms, robots guidance, rate limits, and data-use rules before extraction.	Node.js for the `create-webclaw` installer, or Rust/Cargo when building the MCP binary from source. Review of AGPL-3.0 obligations before redistributing or operating modified server versions. Review of target-site terms, robots expectations, rate limits, and scraping permissions. Optional `WEBCLAW_API_KEY` only when hosted API fallback is acceptable for bot-protected or JavaScript-heavy pages.	Node.js 22 or newer available in the MCP client runtime for local stdio usage. Apify account, OAuth session, API token, x402 wallet, or Skyfire payment setup depending on the chosen transport and payment mode. Explicit tool selection for production use, because the default tool configuration may change in future versions. Team approval policy for Actor runs, paid scraping workflows, agentic payments, dataset access, and aborting active runs.	Node.js and npx available to the MCP client runtime. Bright Data account and API token stored as `API_TOKEN`. Review of Bright Data plan limits, free-tier scope, paid modes, and data-product terms. A decision about whether to use default rapid tools, `PRO_MODE`, `GROUPS`, or explicit `TOOLS`.
Install	npx -y agentql-mcp Copy install	npx create-webclaw Copy install	npx @apify/actors-mcp-server --tools actors,docs,apify/rag-web-browser Copy install	npx @brightdata/mcp Copy install
Config	{ "mcpServers": { "agentql": { "command": "npx", "args": ["-y", "agentql-mcp"], "env": { "AGENTQL_API_KEY": "<your-agentql-api-key>" } } } } Copy config	Manual-only setup: npx create-webclaw Copy config	{ "mcpServers": { "apify": { "command": "npx", "args": [ "-y", "@apify/actors-mcp-server", "--tools", "actors,docs,apify/rag-web-browser" ], "env": { "APIFY_TOKEN": "<your-apify-token>" } } } } Copy config	{ "mcpServers": { "bright-data": { "command": "npx", "args": ["@brightdata/mcp"], "env": { "API_TOKEN": "YOUR_BRIGHT_DATA_API_TOKEN", "GROUPS": "code,research", "RATE_LIMIT": "100/1h" } } } } Copy config
Citations	Source repositorygithub.com 2026-07-21T07:17:01+00:00 Documentationgithub.com Websiteagentql.com Submitted by oktofeesh12026-06-06 Source methodology →	Source repositorygithub.com 2026-07-21T07:17:01+00:00 Documentationraw.githubusercontent.com Submitted by oktofeesh12026-06-06 Source methodology →	Source repositorygithub.com 2026-07-21T07:17:01+00:00 Documentationdocs.apify.com Submitted by oktofeesh12026-06-06 Source methodology →	Source repositorygithub.com 2026-07-21T07:17:01+00:00 Documentationbrightdata.com Submitted by oktofeesh12026-06-05 Source methodology →
Claim	Unclaimed	Unclaimed	Unclaimed	Unclaimed

Source-backed guides for putting this to work.