MCP Http Client MCP Server

MCP Server for REST API interactions with authentication and Swagger documentation support

Local serverstdioTypeScript

What is the MCP Http Client MCP server?

Connect MCP Http Client to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP Server for REST API interactions with authentication and Swagger documentation support. The mcp http client mcp server is what makes that connection.

What the server does

A Model Context Protocol (MCP) server that provides REST API client functionality with authentication support and Swagger documentation integration.

  • Multiple Authentication Methods — Support for both token-based and login-based authentication
  • Swagger Integration — Automatic endpoint discovery and documentation from OpenAPI/Swagger specs
  • Automatic Token Management — Handles token refresh and re-authentication
  • Comprehensive HTTP Methods — Support for GET, POST, PUT, DELETE, and PATCH requests
  • Error Handling — Robust error handling with retry logic
  • MCP Compatible — Fully compatible with the Model Context Protocol

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Building — The Building tool exposed by this server
  • Running — The Running tool exposed by this server

Installation

npm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Credentials and setup notes

Configuration is passed through the environment: MCP_REST_BASE_URL, MCP_REST_AUTH_TYPE, MCP_REST_TOKEN, MCP_REST_SWAGGER_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Http Client's toolset — Building, Running — is a fair guide to whether it matches your workflow. It is maintained by gyuco; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
BuildingThe Building tool exposed by this server.
RunningThe Running tool exposed by this server.

How to install the MCP Http Client MCP server

{
  "mcpServers": {
    "http-client": {
      "command": "npx",
      "args": ["-y", "npm"],
      "env": {
        "MCP_REST_BASE_URL": "your-value",
        "MCP_REST_AUTH_TYPE": "your-value",
        "MCP_REST_TOKEN": "your-value",
        "MCP_REST_SWAGGER_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
MCP_REST_BASE_URLEndpoint or connection string the server talks to.Yes
MCP_REST_AUTH_TYPEConfiguration value read at startup.Optional
MCP_REST_TOKENCredential the server authenticates with.Yes
MCP_REST_SWAGGER_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use MCP Http Client to Building.
  • Use MCP Http Client to Running.

Frequently asked questions

It connects MCP Http Client to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Building, Running) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Http Client directly.