Context MCP Server
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 |
|---|---|
| fetchA | Fetches a URL from the internet 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. |
| fetch_and_saveA | Fetches a URL from the internet using Jina Reader API (with fallback to standard fetch) and saves the content to a file. This tool first tries to fetch content using Jina Reader API for better markdown conversion, and falls back to the standard fetch method if Jina fails. Files are saved in the configured working directory. If no file path is specified, an automatic filename will be generated based on the URL. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| fetch | Fetch a URL and extract its contents as markdown |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have significant functional overlap. Both fetch URLs from the internet and handle content extraction, with fetch_and_save essentially being an enhanced version of fetch that adds file saving functionality. An agent would struggle to determine when to use fetch versus fetch_and_save since the core fetching behavior is duplicated.
The naming follows a consistent snake_case pattern with clear verb-action structure. Both tools start with 'fetch' as the primary action, and fetch_and_save accurately describes the additional functionality. The minor deviation is that fetch doesn't specify its optional markdown extraction in the name, but this is reasonable.
With only 2 tools, the server feels thin for a 'Context MCP Server' which suggests broader contextual capabilities. While internet fetching is a valuable function, a server with this name might be expected to offer additional context-related operations beyond just URL fetching and saving.
For a server named 'Context MCP Server', the toolset is severely incomplete. There are no tools for managing, searching, or analyzing fetched content, no context storage or retrieval mechanisms, and no integration with other context sources. The server essentially provides only basic URL fetching with file saving as an afterthought.