MCP Fetch
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetchB | Perform HTTP requests with full control over method, headers, body, and other fetch options |
| get-rulesA | Get use cases and best practices for using the tools in this MCP server |
| graphqlB | Execute GraphQL queries and mutations with support for variables and custom headers |
| puppeteerB | Control browsers and pages with Puppeteer - launch/close browsers, open/close pages, execute JavaScript, take screenshots, and more |
| socketB | Manage WebSocket connections - connect, send, receive messages, list connections, and close |
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 5 tools
Each tool has a clearly distinct purpose: fetch for HTTP requests, get-rules for documentation, graphql for GraphQL operations, puppeteer for browser automation, and socket for WebSocket management. There is no overlap in functionality, making tool selection straightforward for an agent.
The naming conventions are mixed: fetch, graphql, and socket use lowercase single words, while get-rules uses kebab-case and puppeteer is a proper noun. This inconsistency reduces predictability, though the names remain readable and descriptive of their functions.
With 5 tools, the server is well-scoped for a utility-focused domain like web and browser operations. Each tool serves a distinct and essential purpose, such as HTTP requests, GraphQL, browser control, WebSocket management, and documentation, making the count appropriate and efficient.
The tool set covers key areas for web and browser automation, including HTTP, GraphQL, WebSockets, and Puppeteer, with a documentation tool for guidance. Minor gaps might exist, such as advanced caching or proxy handling, but core workflows are well-supported without dead ends.