MCP Server Boilerplate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start-chrome-debugA | Start Chrome browser with remote debugging enabled. Use this tool to view network traffic and request details. |
| query-network-trafficB | Query network requests by URL pattern or time range from the active Chrome debugging session. Pages take a few seconds to load, so wait a few seconds before querying. |
| get-network-detailsA | Get detailed information about a specific network request including headers, payload, and response body |
| open-urlA | Open a specific URL in the Chrome debug browser window and wait for network traffic to settle |
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 4 tools
Each tool serves a distinct step in the debugging workflow: starting the browser, opening a URL, querying traffic, and inspecting details. Their purposes are clearly different and the descriptions reinforce the separation.
All tool names follow a consistent hyphen-separated, verb-first pattern (start-, open-, query-, get-), making the naming predictable and uniform.
Four tools is well-scoped for a Chrome network debugging server; each tool covers a fundamental operation without unnecessary bloat.
The core workflow is covered, but there is no explicit stop or teardown tool for the debugging session, leaving a minor gap in lifecycle management.