URL Text Fetcher MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRAVE_API_KEY | Yes | Brave Search API key | |
| REQUEST_TIMEOUT | No | Request timeout in seconds (default: 10) | 10 |
| MAX_RESPONSE_SIZE | No | Maximum response size in bytes (default: 10485760) | 10485760 |
| BRAVE_RATE_LIMIT_RPS | No | Rate limit for Brave Search API in requests per second (default: 1) | 1 |
| CONTENT_LENGTH_LIMIT | No | Content length limit in characters (default: 5000) | 5000 |
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 |
|---|---|
| get_server_infoA | Get information about this MCP server including version, implementation, and capabilities. Returns: Server information including version, implementation type, and available features |
| test_brave_searchC | Test the Brave Search API connection and configuration. Args: query: Test query to search for (default: "test") |
| fetch_url_textA | Download all visible text from a URL. Args: url: The URL to fetch text from |
| fetch_page_linksB | Return a list of all links on the page. Args: url: The URL to fetch links from |
| brave_search_and_fetchA | Search the web using Brave Search and automatically fetch content from the top results. Args: query: The search query max_results: Maximum number of results to fetch content for (default: 3, max: 10) |
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
Most tools have distinct purposes: search-and-fetch, fetch links, fetch text, get server info, and test search. However, 'brave_search_and_fetch' and 'test_brave_search' could cause some confusion as both involve Brave Search queries, though their primary functions differ (content fetching vs. API testing).
The naming is mixed with no clear pattern: 'brave_search_and_fetch' uses underscores and compound verbs, 'fetch_page_links' and 'fetch_url_text' follow a verb_noun style, while 'get_server_info' and 'test_brave_search' use different verb styles. This inconsistency makes the set less predictable but still readable.
With 5 tools, this server is well-scoped for its URL text fetching purpose. Each tool earns its place by covering core functionalities like searching, fetching text/links, server info, and API testing, without being overly sparse or bloated.
The toolset covers the main workflows for a URL text fetcher: searching, fetching text and links, and server management. A minor gap is the lack of tools for advanced text processing or filtering, but agents can work around this with the provided fetch operations.