Skip to main content
Glama
enesjakozh
tinyfish-io

AgentQL MCP Server

by tinyfish-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

AgentQL MCP 서버

이는 AgentQL 의 데이터 추출 기능을 통합한 MCP(Model Context Protocol) 서버입니다.

특징

도구

  • extract-web-data - 'prompt'를 실제 데이터와 추출할 필드에 대한 설명으로 사용하여 주어진 'url'에서 구조화된 데이터를 추출합니다.

Related MCP server: Fetcher MCP

설치

AgentQL MCP Server를 사용하여 웹 페이지에서 데이터를 추출하려면 npm을 통해 설치하고, Dev Portal 에서 API 키를 받은 다음, MCP를 지원하는 원하는 앱에서 구성해야 합니다.

패키지를 설치하세요

지엑스피1

Claude 구성

  • ⌘ + , 를 눌러 Claude 데스크톱 설정을 엽니다(Claude 계정 설정과 혼동하지 마세요).

  • 개발자 사이드바 섹션으로 이동

  • 구성 편집을 클릭하고 claude_desktop_config.json 파일을 엽니다.

  • 구성 파일의 mcpServers 사전 내에 agentql 서버를 추가합니다.

  • 앱을 다시 시작하세요

{
  "mcpServers": {
    "agentql": {
      "command": "npx",
      "args": ["-y", "agentql-mcp"],
      "env": {
        "AGENTQL_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

여기에서 Claude의 MCP 구성에 대해 자세히 알아보세요.

커서 구성

  • 커서 설정 열기

  • MCP > MCP 서버 로 이동

  • + 새 MCP 서버 추가를 클릭하세요

  • 다음을 입력하세요.

    • 이름: "agentql"(또는 원하는 이름)

    • 유형: "명령"

    • 명령어: env AGENTQL_API_KEY=YOUR_API_KEY npx -y agentql-mcp

여기에서 Cursor의 MCP 구성에 대해 자세히 알아보세요.

Windsurf 구성

  • Windsurf 열기: MCP 구성 패널

  • 사용자 정의 서버 추가를 클릭하세요+

  • 또는 ~/.codeium/windsurf/mcp_config.json 직접 열 수 있습니다.

  • 구성 파일의 mcpServers 사전 내에 agentql 서버를 추가합니다.

{
  "mcpServers": {
    "agentql": {
      "command": "npx",
      "args": ["-y", "agentql-mcp"],
      "env": {
        "AGENTQL_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Windsurf의 MCP 구성에 대한 자세한 내용은 여기에서 확인하세요.

MCP 통합 검증

에이전트에게 웹에서 데이터를 추출하는 작업을 맡겨 보세요. 예:

Extract the list of videos from the page https://www.youtube.com/results?search_query=agentql, every video should have a title, an author name, a number of views and a url to the video. Make sure to exclude ads items. Format this as a markdown table.

[!TIP] 에이전트가 AgentQL을 사용하지 않고는 URL을 열거나 웹에서 콘텐츠를 로드할 수 없다고 불평하는 경우 "도구 사용" 또는 "agentql 도구 사용" 힌트를 추가해 보세요.

개발

종속성 설치:

npm install

서버를 빌드하세요:

npm run build

자동 재빌드를 사용한 개발의 경우:

npm run watch

개발 버전을 사용해보고 싶다면 기본 구성 대신 다음 구성을 사용할 수 있습니다.

{
  "mcpServers": {
    "agentql": {
      "command": "/path/to/agentql-mcp/dist/index.js",
      "env": {
        "AGENTQL_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

[!NOTE] Claude를 두 개의 유사한 서버와 혼동하지 않으려면 기본 AgentQL MCP 서버 구성을 제거하는 것을 잊지 마세요.

디버깅

MCP 서버는 stdio를 통해 통신하므로 디버깅이 어려울 수 있습니다. 패키지 스크립트로 제공되는 MCP Inspector를 사용하는 것이 좋습니다.

npm run inspector

검사기는 브라우저에서 디버깅 도구에 액세스할 수 있는 URL을 제공합니다.

Available Tools

1 tool
extract-web-dataA

Extracts structured data as JSON from a web page given a URL using a Natural Language description of the data.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL of the public webpage to extract data from
promptYesNatural Language description of the data to extract from the page

TDQS

A3.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. Describes core function but omits important behavioral traits like rate limits, authentication requirements, handling of dynamic content, or error scenarios.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single concise sentence that is front-loaded and contains only essential information. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Mentions output format (JSON) but lacks details on return structure, error handling, or limitations like URL restrictions or page complexity. Adequate for a simple tool but incomplete for production use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear parameter descriptions. The description reinforces the 'prompt' parameter's nature but adds no new meaning beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states verb (Extracts), resource (structured data as JSON from web page), and method (Natural Language description). Specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implicitly indicates use when needing structured data from a URL via NL description. No siblings to differentiate, but lacks explicit when-not-to-use or alternative methods.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Addedextract-web-data
  2. 1 tool updatev1.0.0
    • Removedextract-web-data
  3. 1 tool update
    • First observedextract-web-data
Deploy Server
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

TDQS

A3.6/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no risk of confusion between tools, so disambiguation is perfect.

Naming Consistency5/5

The single tool name 'extract-web-data' follows a clear verb_noun pattern, and consistency is trivially maintained.

Tool Count2/5

A single tool is too few for a web scraping server, which typically requires tools for different actions (e.g., listing, configuring) or handling multiple extraction strategies.

Completeness2/5

The server only provides extraction via natural language, missing common features like pagination, multiple output formats, or error handling, leaving significant gaps for agents.

Maintenance

ActivityActive
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers

  • MCP Server Firecrawl

    Msparihar
    A
    license
    C
    quality
    D
    maintenance
    A server that provides web scraping and intelligent content searching capabilities using the Firecrawl API, enabling AI agents to extract structured data from websites and perform content searches.
    5
    3
    MIT

  • Fetcher MCP

    everford
    -
    license
    C
    quality
    Not graded
    maintenance
    A server that allows fetching web page content using Playwright headless browser with AI-powered capabilities for efficient information extraction.
    2
    4,375 npm
    7
    -

Appeared in Searches