Skip to main content
Glama
enesjakozh
enemyrr

MCP Server Pagespeed

by enemyrr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

@enemyrr/mcp-서버-페이지 속도

Google PageSpeed Insights 분석을 제공하는 모델 컨텍스트 프로토콜 서버입니다. 이 서버를 통해 AI 모델은 표준화된 인터페이스를 통해 웹페이지 성능을 분석할 수 있습니다.

커서 IDE 설치 및 설정

  1. 프로젝트를 복제하고 빌드합니다.

지엑스피1

  1. 커서 IDE 설정에 서버를 추가합니다.

    • 명령 팔레트 열기(Cmd/Ctrl + Shift + P)

    • "MCP: 서버 추가"를 검색하세요

    • 다음 필드를 채워주세요:

      • 이름: pagespeed

      • 유형: command

      • 명령어: node /absolute/path/to/mcp-server-pagespeed/build/index.js

참고 : /absolute/path/to/ 프로젝트를 복제하고 빌드한 실제 경로로 바꾸세요.

Related MCP server: Lighthouse MCP

명령줄 사용법

그냥 실행하세요:

npx mcp-server-pagespeed

사용 가능한 도구

분석_페이지 속도

Google PageSpeed Insights API를 사용하여 웹페이지를 분석합니다.

use_mcp_tool({
  server_name: "pagespeed",
  tool_name: "analyze_pagespeed",
  arguments: {
    url: "https://example.com"
  }
});

도구는 다음을 반환합니다.

  • 전체 성과 점수(0~100점)

  • 로딩 경험 지표

    • 첫 번째 콘텐츠 페인트

    • 첫 번째 입력 지연

  • 상위 5가지 개선 제안:

    • 제목

    • 설명

    • 잠재적 영향

    • 현재 가치

특징

  • 실시간 웹페이지 성능 분석

  • 자세한 로딩 경험 측정 항목

  • 우선순위가 지정된 개선 제안

  • 포괄적인 오류 처리

  • TypeScript 지원

오류 처리

서버는 다음에 대한 자세한 오류 메시지를 제공합니다.

  • 잘못된 URL

  • API 요청 실패

  • 연결 문제

  • 잘못된 도구 호출

기여하다

기여를 환영합니다! https://github.com/enemyrr/mcp-server-pagespeed 에 풀 리퀘스트를 제출해 주세요.

특허

MIT

Available Tools

1 tool
analyze_pagespeedC

Analyzes a webpage using Google PageSpeed Insights API

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to analyze

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the API but fails to describe key traits like rate limits, authentication needs, error handling, or what the analysis entails (e.g., performance metrics, recommendations). This leaves the agent with insufficient information about how the tool behaves.

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?

The description is a single, efficient sentence that directly states the tool's function without unnecessary words. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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?

Given the lack of annotations and output schema, the description is incomplete. It does not explain what the analysis returns (e.g., scores, suggestions) or behavioral aspects like API constraints. For a tool that likely provides detailed performance data, this omission is significant, leaving the agent without enough context to understand the tool's full scope.

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?

The input schema has 100% description coverage, with the 'url' parameter documented as 'The URL to analyze.' The description does not add any meaning beyond this, such as URL format requirements or examples. With high schema coverage, the baseline score of 3 is appropriate, as the schema handles the parameter documentation adequately.

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's purpose: 'Analyzes a webpage using Google PageSpeed Insights API.' It specifies the verb ('analyzes') and resource ('a webpage'), and mentions the underlying API. However, with no sibling tools, it cannot demonstrate differentiation from alternatives, preventing a perfect score of 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or exclusions. It simply states what the tool does without context for its application, which is a significant gap in usage instructions.

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 observedanalyze_pagespeed
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

The single tool name follows a clear verb_noun pattern (analyze_pagespeed). Since there is only one tool, consistency is inherently perfect with no deviations to assess.

Tool Count2/5

A single tool is too few for a server named 'MCP Server Pagespeed', which suggests a broader scope for page speed analysis. This minimal set feels thin and limits functionality, as it only covers analysis without supporting operations like history tracking or batch processing.

Completeness2/5

The tool surface is severely incomplete for a page speed analysis domain. It only provides analysis but lacks essential operations such as retrieving historical results, comparing analyses, or managing configurations, leaving significant gaps for agent workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Lighthouse MCP

    mizchi
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI models to perform Google Lighthouse website performance analysis, including Core Web Vitals, accessibility, SEO audits, and actionable optimization recommendations. Provides comprehensive web performance insights through natural language interactions.
    1,529 npm
    4
    MIT

  • PageSpeed MCP Server

    mcpflow
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI assistants to perform comprehensive web performance analysis using Google's PageSpeed Insights API, including metrics, best practices, SEO, and accessibility audits.
    26 npm
    MIT

Appeared in Searches