Mcp Http

Created By
one-matrixa year ago
MCP Http Server is a Model Context Protocol (MCP) server implemented based on the Python httpx library. It supports HTTP request operations via a REST API, including various methods like GET, POST, PUT, and DELETE, aiming to simplify integration with various Web APIs.
Overview

What is MCP Http?

MCP Http Server is a Model Context Protocol (MCP) server implemented using the Python httpx library. It facilitates HTTP request operations via a REST API, supporting methods like GET, POST, PUT, and DELETE, aimed at simplifying integration with various Web APIs.

How to use MCP Http?

To use MCP Http, clone the project from GitHub, install the necessary dependencies, and start the server using the provided commands. You can then make HTTP requests to interact with the server.

Key features of MCP Http?

  • Supports multiple HTTP methods (GET, POST, PUT, DELETE).
  • Easy integration with Web APIs.
  • Built on the reliable Python httpx library.

Use cases of MCP Http?

  1. Integrating with third-party APIs for data retrieval.
  2. Building RESTful services for web applications.
  3. Simplifying backend communication in microservices architecture.

FAQ from MCP Http?

  • What programming language is MCP Http written in?

MCP Http is implemented in Python using the httpx library.

  • Is MCP Http free to use?

Yes! MCP Http is open-sourced under the MIT License.

  • How can I contribute to the project?

You can contribute by submitting issues or pull requests on the GitHub repository.

Server Config

{
  "mcpServers": {
    "mcp-httpx": {
      "command": "uv",
      "args": [
        "--from",
        "git+https://github.com/one-matrix/mcp-http",
        "run",
        "mcp-http"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
one-matrix
Star
-
Language
-
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)

8 hours ago
Alloy

2 days ago