1. Home
  2. AgentQL MCP Server
  3. AgentQL MCP Server for Cursor: Setup & Config

Data as of

AgentQL MCP Server for Cursor: Setup & Config

Cursor: AgentQL MCP Server extracts structured JSON from a web page using a natural-language description of the desired fields.

What you can do with AgentQL in Cursor

A compact URL-and-prompt interface for turning web pages into structured JSON inside MCP workflows.

  • Bring structured page data into an assistant report.
  • Use the same extraction tool across supported MCP hosts.

Before you start: AgentQL in Cursor

  • Node.js with npm / npx
  • AgentQL API key
  • An MCP-compatible host

The 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.

AgentQL Cursor configuration

  1. Choose Cursor configuration scope

    For AgentQL MCP Server, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

  2. Add AgentQL MCP Server to Cursor

    Use the agentql-mcp entry below in mcpServers. Keep AgentQL MCP Server's documented stdio connection fields and your other Cursor entries.

  3. Check AgentQL MCP Server in Cursor

    AgentQL MCP Server: Enable in Cursor’s MCP settings; inspect tools.

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

JSON
{
  "mcpServers": {
    "agentql-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "agentql-mcp"
      ],
      "env": {
        "AGENTQL_API_KEY": "<API key from the AgentQL developer portal>"
      }
    }
  }
}

AgentQL tools available to Cursor

AgentQL's stored tool list documents 1 tool; compare it with Cursor's connected tool list, because the stored list is not a live check.

extract-web-data

Find extract-web-data under AgentQL in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Extract JSON fields from a page URL using a natural-language description.

AgentQL: full stored tool descriptions

Troubleshooting AgentQL in Cursor

  • Cursor must find npx agentql-mcp (Node.js/npm) for AgentQL MCP Server. Enable the project/user entry in MCP settings and inspect its tools.
  • Review AGENTQL_API_KEY for AgentQL MCP Server before sharing project .cursor/mcp.json; project scope travels with the repository.
  • AgentQL MCP Server uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Requires an AgentQL API key.
  • Known limitation: Only one extraction tool is documented.
  • Known limitation: Pricing and usage limits are not stated in the README.
  • General Cursor troubleshooting lives in the /clients/cursor guide.

AgentQL MCP Server — details. Cursor guide

Frequently asked questions

Cursor's AgentQL MCP Server entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.

Cursor's agentql-mcp example uses stdio.

AgentQL MCP Server's Cursor configuration invokes npx agentql-mcp (Node.js/npm).

Cursor's AgentQL MCP Server example references AGENTQL_API_KEY. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

AgentQL MCP Server's stored list contains 1 tool, including extract-web-data. Compare those names with Cursor's connected tool list; the stored list is not a live check.

The tool accepts a page URL and a prompt describing the desired data and fields.

No. The supplied README and tool list describe only extract-web-data.

The README suggests explicitly asking the assistant to use tools or the AgentQL tool.