Server facts
AgentQL MCP Server
Project
- Author
- tinyfish-io
- Repository
- github.com/tinyfish-io/agentql-mcp
- License
- MIT
- Category
- Search & Web Data
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 181
- Last commit
- Data as of
Tags
- Agentql
- Natural Language
- Nodejs
- Structured Data
- Web Extraction
Overview
AgentQL MCP Server exposes AgentQL web-data extraction through a single MCP tool. The caller supplies a page URL and a natural-language prompt describing the information and fields to collect. The result is structured JSON rather than an unprocessed page dump. This focus makes the server a small integration for assistants that need data from a page in a defined shape. The README demonstrates a video-results extraction task asking for titles, creators, view counts, and video links while excluding advertising entries; that is an example request, not a separate video-specific tool.
Installation uses the agentql-mcp npm package, and the client configuration starts it through npx. An AgentQL API key from the developer portal is required and passed as AGENTQL_API_KEY. The README provides configurations for Claude Desktop, VS Code, Cursor, and Windsurf, including an input prompt for the key in VS Code. It also documents a built local version for development and recommends removing duplicate server configurations when testing that version. MCP Inspector is available through a package script for debugging stdio communication. The supplied material does not specify pricing, service quotas, authentication flows for target websites, or additional browsing actions. Selection should therefore rest on the documented URL-plus-description extraction interface, not assumptions about a general-purpose browser automation suite.
Install & configure
Requirements
- Node.js with npm / npx
- AgentQL API key
- An MCP-compatible host
npx -y agentql-mcpThe README also documents npm install -g agentql-mcp. Restart the host after adding its configuration. Development builds should replace, rather than duplicate, the default server entry.
Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"agentql-mcp": {
"command": "npx",
"args": [
"-y",
"agentql-mcp"
],
"env": {
"AGENTQL_API_KEY": "<API key from the AgentQL developer portal>"
}
}
}
}Config file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"agentql-mcp": {
"command": "npx",
"args": [
"-y",
"agentql-mcp"
],
"env": {
"AGENTQL_API_KEY": "<API key from the AgentQL developer portal>"
}
}
}
}Config file · Workspace: .vscode/mcp.json
For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.
{
"servers": {
"agentql-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"agentql-mcp"
],
"env": {
"AGENTQL_API_KEY": "<API key from the AgentQL developer portal>"
}
}
}
}Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json
Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"agentql-mcp": {
"command": "npx",
"args": [
"-y",
"agentql-mcp"
],
"env": {
"AGENTQL_API_KEY": "<API key from the AgentQL developer portal>"
}
}
}
}Config file · Project scope: .mcp.json at the repository root
The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"agentql-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"agentql-mcp"
],
"env": {
"AGENTQL_API_KEY": "<API key from the AgentQL developer portal>"
}
}
}
}Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Tools
Source: repository tool metadata. Tool descriptions are a documented snapshot, not a live capability check.
| Tool | What it does |
|---|---|
| extract-web-data | Extract JSON fields from a page URL using a natural-language description. |
Names, permissions, and defaults can change. Check the current upstream documentation before granting access.
Use cases
- Extract named fields from a page into JSON.
- Collect video-result metadata as illustrated in the README.
- Bring structured page data into an assistant report.
- Use the same extraction tool across supported MCP hosts.
Strengths
- One focused tool with URL and natural-language inputs.
- Returns structured JSON instead of requiring raw-page interpretation.
- Documents setup for several common MCP clients.
Limitations
- Requires an AgentQL API key.
- Only one extraction tool is documented.
- Pricing and usage limits are not stated in the README.
Frequently asked questions
Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.
