Data as of

AgentQL MCP Server for VS Code: Setup & Config

VS Code: 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 VS Code

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

  • Extract named fields from a page into JSON.
  • Bring structured page data into an assistant report.

Before you start: AgentQL in VS Code

  • 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 VS Code configuration

  1. Choose VS Code configuration scope

    For AgentQL MCP Server, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

  2. Add AgentQL MCP Server to VS Code

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

  3. Check AgentQL MCP Server in VS Code

    AgentQL MCP Server: Start in VS Code’s MCP controls; inspect output and trust prompts.

Config file · Workspace: .vscode/mcp.json

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

AgentQL tools available to VS Code

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

extract-web-data

Look for extract-web-data among VS Code's agent-mode tools after starting AgentQL through the MCP controls.

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

AgentQL: full stored tool descriptions

Troubleshooting AgentQL in VS Code

  • Make npx agentql-mcp (Node.js/npm) available in the workspace, container, or remote environment hosting AgentQL MCP Server. Start through VS Code's MCP controls; inspect output and trust prompts.
  • For AgentQL MCP Server, keep AGENTQL_API_KEY out of version control; VS Code documents input variables and secret handling.
  • AgentQL MCP Server uses stdio here: VS Code 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 VS Code troubleshooting lives in the /clients/vscode guide.

AgentQL MCP Server — details. VS Code guide

Frequently asked questions

For AgentQL MCP Server, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.

VS Code's agentql-mcp example uses stdio.

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

VS Code'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 VS Code's connected tool list; the stored list is not a live check.

The supplied tool facts identify structured JSON output.

The README directs users to the AgentQL developer portal at https://dev.agentql.com.

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