Performance Analysis MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEFAULT_URL | No | Optional default URL to analyze |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_pageA | Collect page performance metrics for a public http(s) URL using Playwright and CDP. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools; the purpose is singular and clear.
The single tool follows a consistent verb_noun pattern (analyze_page), which is clear and predictable.
The server claims to be a Performance Analysis MCP Server but provides only one tool, which is too few for the implied broader scope. A single tool feels thin and under-scoped.
The server covers only basic page performance metrics. Missing tools for audits, comparisons, history, or reporting create significant gaps for a performance analysis server.