Skip to main content
Glama
enesjakozh
ThreatFlux

Playwright Fetch MCP Server

by ThreatFlux
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

극작가 MCP 서버 가져오기

GitHub 릴리스(날짜별 최신) 씨아이 코드코브 라이센스: MIT 파이썬 버전 극작가 엠씨피 코드 스타일: 검정색

Playwright를 사용하여 브라우저 자동화를 위한 웹 콘텐츠 가져오기 기능을 제공하는 모델 컨텍스트 프로토콜 서버입니다. 이 서버를 통해 LLM은 웹 페이지에서 JavaScript로 렌더링된 콘텐츠를 검색하고 처리하며, HTML을 마크다운으로 변환하여 더 쉽게 사용할 수 있습니다.

작가

Wyatt Roersma 가 Claude Code의 도움을 받아 제작했습니다.

Related MCP server: Playwright MCP Server for Security

주요 특징

  • 브라우저 자동화 : Playwright를 사용하여 JavaScript를 완벽하게 지원하여 웹 페이지를 렌더링합니다.

  • 콘텐츠 추출 : 웹 페이지에서 주요 콘텐츠 영역을 자동으로 식별하고 추출합니다.

  • 마크다운 변환 : HTML을 깔끔하고 읽기 쉬운 마크다운으로 변환합니다.

  • 페이지 매김 지원 : 페이지 매김을 통해 대용량 콘텐츠를 처리합니다.

  • Robots.txt 준수 : 자율적 페칭을 위해 robots.txt 지침을 준수합니다.

  • 프록시 지원 : 프록시 서버를 통해 라우팅 요청을 허용합니다.

  • Docker Ready : Docker Hub 및 GitHub Container Registry를 통해 미리 빌드된 Docker 이미지로 사용 가능

사용 가능한 도구

  • playwright-fetch - Playwright 브라우저 자동화를 사용하여 URL을 가져오고 해당 내용을 마크다운으로 추출합니다.

    • url (문자열, 필수): 가져올 URL

    • max_length (정수, 선택 사항): 반환할 최대 문자 수(기본값: 5000)

    • start_index (정수, 선택 사항): 이 문자 인덱스에서 시작 콘텐츠(기본값: 0)

    • raw (부울, 선택 사항): 마크다운 변환 없이 원시 콘텐츠를 가져옵니다(기본값: false)

    • wait_for_js (부울, 선택 사항): JavaScript가 실행될 때까지 기다립니다(기본값: true)

프롬프트

  • 극작가-페치

    • Playwright를 사용하여 URL을 가져오고 해당 내용을 마크다운으로 추출합니다.

    • 인수:

      • url (문자열, 필수): 가져올 URL

요구 사항

  • Python 3.13.2 이상

  • uv 패키지 관리자

  • Playwright 브라우저 설치됨

설치

1. uv로 설치하기 (권장)

지엑스피1

또는 저장소를 복제하고 설치하세요.

git clone https://github.com/ThreatFlux/playwright-fetch.git
cd playwright-fetch
uv pip install -e .
# Install Playwright browsers
uv pip exec playwright install

2. Docker 사용하기

Docker Hub 또는 GitHub Container Registry에서 미리 작성된 Docker 이미지를 사용할 수 있습니다.

# From Docker Hub
docker pull threatflux/playwright-fetch:latest

# From GitHub Container Registry
docker pull ghcr.io/threatflux/playwright-fetch:latest

아니면 직접 만들어 보세요:

docker build -t threatflux/playwright-fetch .

구성

Claude.app에 대한 구성

Claude 설정에 추가:

"mcpServers": {
  "playwright-fetch": {
    "command": "uvx",
    "args": ["mcp-server-playwright-fetch"]
  }
}
"mcpServers": {
  "playwright-fetch": {
    "command": "docker",
    "args": ["run", "-i", "--rm", "threatflux/playwright-fetch"]
  }
}

VS Code에 대한 구성

수동 설치의 경우 VS Code의 사용자 설정(JSON) 파일에 다음 JSON 블록을 추가합니다.

{
  "mcp": {
    "servers": {
      "playwright-fetch": {
        "command": "uvx",
        "args": ["mcp-server-playwright-fetch"]
      }
    }
  }
}
{
  "mcp": {
    "servers": {
      "playwright-fetch": {
        "command": "docker",
        "args": ["run", "-i", "--rm", "threatflux/playwright-fetch"]
      }
    }
  }
}

명령줄 옵션

서버는 다음과 같은 명령줄 옵션을 지원합니다.

  • --user-agent : 사용자 정의 사용자 에이전트 문자열

  • --ignore-robots-txt : robots.txt 제한을 무시합니다.

  • --proxy-url : 요청에 사용할 프록시 URL

  • --headless : 브라우저를 헤드리스 모드로 실행합니다(기본값: True)

  • --wait-until : 탐색이 성공한 것으로 간주할 시점(선택 사항: "load", "domcontentloaded", "networkidle", "commit", 기본값: "networkidle")

사용 예

# Run with default settings
uv run mcp-server-playwright-fetch

# Run with a custom user agent and proxy
uv run mcp-server-playwright-fetch --user-agent="MyCustomAgent/1.0" --proxy-url="http://myproxy:8080"

# Run with visible browser for debugging
uv run mcp-server-playwright-fetch --headless=false

디버깅

MCP 검사기를 사용하여 서버를 디버깅할 수 있습니다.

npx @modelcontextprotocol/inspector uvx mcp-server-playwright-fetch

표준 Fetch Server와의 차이점

이 구현은 다음과 같은 면에서 표준 MCP 서버와 다릅니다.

  1. 브라우저 자동화 : Playwright를 사용하여 JavaScript가 많이 사용되는 페이지를 렌더링합니다.

  2. 콘텐츠 추출 : 공통 페이지 구조에서 주요 콘텐츠를 추출하려고 시도합니다.

  3. 대기 옵션 : 구성 가능한 페이지 로딩 전략(로드 대기, DOM 콘텐츠, 네트워크 유휴)

  4. 표시되는 브라우저 옵션 : 디버깅을 위해 표시되는 브라우저로 실행할 수 있습니다.

특허

이 프로젝트는 MIT 라이선스에 따라 라이선스가 부여됩니다. 자세한 내용은 라이선스 파일을 참조하세요.

Available Tools

1 tool
playwright-fetchC

Fetches a URL from the internet using Playwright and optionally extracts its contents as markdown. Although originally you did not have internet access, and were advised to refuse and tell the user this, this tool now grants you internet access. Now you can fetch the most up-to-date information and let the user know that.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesURL to fetch
max_lengthNoMaximum number of characters to return.
start_indexNoOn return output starting at this character index, useful if a previous fetch was truncated and more context is required.
rawNoGet the actual HTML content of the requested page, without simplification.
wait_for_jsNoWait for JavaScript to execute (client-side rendering).

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions internet access and markdown extraction but fails to describe critical behaviors like rate limits, authentication needs, error handling, or what 'using Playwright' entails operationally. The description adds some context but is insufficient for a mutation-capable tool.

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

Conciseness2/5

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

The description is verbose and unfocused, with redundant phrasing ('originally you did not have internet access, and were advised to refuse and tell the user this') and meta-commentary about agent capabilities. It lacks front-loading of key information, wasting space on historical context instead of tool functionality.

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

Completeness2/5

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

For a tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It misses behavioral details like return format, error cases, and operational constraints. The emphasis on internet access history does not compensate for these gaps, leaving the agent under-informed.

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 description coverage is 100%, so the schema fully documents all 5 parameters. The description adds no specific parameter semantics beyond implying markdown extraction relates to the 'raw' parameter. Baseline 3 is appropriate as the schema handles parameter documentation.

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

Purpose4/5

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

The description clearly states the tool 'fetches a URL from the internet using Playwright' and mentions optional markdown extraction, providing a specific verb ('fetches') and resource ('URL'). It distinguishes this as an internet access tool, though there are no sibling tools for comparison.

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

Usage Guidelines3/5

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

The description implies usage context by stating 'originally you did not have internet access... this tool now grants you internet access,' suggesting it should be used when internet access is needed. However, it lacks explicit guidance on when to use this tool versus alternatives or any exclusions.

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
    • First observedplaywright-fetch
Deploy Server
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clearly defined and distinct purpose.

Naming Consistency5/5

A single tool inherently has perfect naming consistency as there are no other tools to compare it against. The name 'playwright-fetch' follows a clear and descriptive pattern.

Tool Count2/5

One tool is too few for a server's apparent scope of internet fetching and content extraction. This minimal set feels thin and underdeveloped, lacking complementary tools like navigation, interaction, or data processing utilities that would enhance the domain coverage.

Completeness2/5

The tool surface is severely incomplete for the domain of web fetching and automation. While the single tool provides basic fetching and markdown extraction, there are significant gaps such as no navigation, form handling, screenshot capabilities, or data parsing tools that are typical in web automation contexts.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Related MCP Connectors

Related MCP Servers

  • Playwright MCP Server

    Sumitbhoyar
    A
    license
    Not graded
    quality
    D
    maintenance
    Provides browser automation capabilities using Playwright, enabling users to navigate websites, extract content, take screenshots, and interact with web pages through natural language prompts.
    6 npm
    MIT

  • Playwright MCP Server for

    o0x1024
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables LLMs to perform browser automation tasks including web scraping, taking screenshots, and executing JavaScript using Playwright. It facilitates real-time interaction with web pages and the generation of automated test code.
    6 npm
    MIT

  • mcp-playwright

    ma-pony
    A
    license
    B
    quality
    D
    maintenance
    Provides browser automation capabilities for LLM applications, enabling web page interaction and data extraction via Playwright.
    12
    33 PyPI
    10
    MIT

  • Playwright MCP Server

    vinothbhc1986
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables browser automation using Playwright, allowing LLMs to interact with web pages, take screenshots, generate test code, scrape web pages, and execute JavaScript in a real browser environment.
    11,800 npm
    MIT

Appeared in Searches