mcp-server-requests

Created By
coucyaa year ago
Web Content Retrieval (full webpage, filtered content, or Markdown-converted), Custom User-Agent, Multi-HTTP Method Support (GET/POST/PUT/DELETE/PATCH), LLM-Controlled Request Headers, LLM-Accessible Response Headers, and more.
Overview

What is mcp-server-requests?

The mcp-server-requests project is a service designed for HTTP requests that enables LLMs (Large Language Models) to read web pages. It supports various features such as converting web pages to Markdown, customizing User-Agent strings, and multiple HTTP methods.

How to use mcp-server-requests?

To use mcp-server-requests, clone the repository from GitHub, install the package, and run the server with the provided command. You can then use various subcommands to fetch web content or perform HTTP requests.

Key features of mcp-server-requests?

  • Converts web pages to Markdown format.
  • Allows customization of User-Agent strings.
  • Supports multiple HTTP methods: GET, POST, PUT, DELETE, PATCH.
  • Provides options for controlling request and response headers.

Use cases of mcp-server-requests?

  1. Fetching and processing web content for data analysis.
  2. Automating web scraping tasks with customizable headers.
  3. Integrating web content retrieval into LLM applications.

FAQ from mcp-server-requests?

  • Can I customize the User-Agent?

Yes! You can specify a custom User-Agent or use a randomly generated one.

  • What HTTP methods are supported?

The service supports GET, POST, PUT, DELETE, and PATCH methods.

  • How do I install mcp-server-requests?

You can install it by cloning the repository and running pip install . in the project directory.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
coucya
Star
1
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago