MCP Web URL Reader

Provides a web URL reading service via an MCP endpoint that fetches pages through a configurable prefix.

javascript

0

GitHub Stars

javascript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

You run an MCP server that exposes a single tool named read_web_url. It fetches absolute URLs by routing requests through a configurable prefix, enabling you to proxy, cache, or gate web requests for AI applications. Its Streamable HTTP endpoint is compatible with many MCP-enabled clients, making it easy to integrate into your workflows.

How to use

You initialize a session with an MCP client and then invoke the read_web_url tool to fetch web content. The server executes the request by prepending a CUSTOM_PREFIX to the target URL and performing the fetch, returning the page content you requested. Use this to route AI web traffic through your own proxy, authentication gateway, cache, or monitoring layer.

How to install

Prerequisites: install Docker and Docker Compose on your host machine.

Create and run the MCP server using Docker Compose. Ensure port 8080 is available on your host.

Run these commands to start the service:

docker-compose up -d

Configuration and usage notes

The MCP server exposes an HTTP endpoint at http://localhost:8080/mcp for integration with AI clients. You can customize how URLs are fetched by setting a CUSTOM_PREFIX, which is prepended to every requested URL before the fetch.

Environment variables shown in examples include CUSTOM_PREFIX and INTERNAL_PORT. CUSTOM_PREFIX defines the URL prefix to prepend to all requests. INTERNAL_PORT defines the port that the server listens on inside the container.

Examples

Example: route requests through a caching proxy

CUSTOM_PREFIX=http://cache-server/proxy
INTERNAL_PORT=8080

Troubleshooting

If the server won’t start, ensure port 8080 is free and environment variables are set. Check container logs for errors and verify that the CUSTOM_PREFIX URL is reachable from within the container.

API and tool usage

The server provides one MCP tool: read_web_url. It accepts a single parameter url (string, required) and returns the text content of the fetched web page.

Example tool call from an MCP client: use the mcp endpoint and request the tool with the URL you want to fetch.

Available tools

read_web_url

Read and return the contents of a web page by fetching the provided URL through the configured CUSTOM_PREFIX