HTTP MCP Server

HTTP/REST client with saved collections, env secrets, and SSRF-safe host allowlisting.

Local serverstdioTypeScript

What is the HTTP MCP server?

Most developer tooling work still happens through a UI a human drives. HTTP MCP server moves it into the conversation instead. HTTP/REST client with saved collections, env secrets, and SSRF-safe host allowlisting.

The short version

Each server lives in its own folder under servers/ and publishes to npm as an independent package, while sharing tooling through an npm workspace. Connect them to any MCP client — Claude Desktop, Claude Code, Cursor, and more.

The tools it exposes

The server publishes 4 tools. What each one is for:

  • Pure — JS/WASM by default; native only when genuinely required.** Servers run via npx/MCPB on any
  • Sandbox — first, layered design.** Each server keeps a thin index.ts (tool registration only) over
  • Token — efficient by default.** Pagination, head/tail/section reads, snippets, and compact graph refs
  • Server — Description

Getting it running

The server ships on npm as @abhishekmcp/notes, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What it needs from you

Configuration is passed through the environment: NOTES_DIR. 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.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. HTTP's toolset — Pure, Sandbox, Token and 1 more — is a fair guide to whether it matches your workflow. It is maintained by Abhishekkumar2021; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • 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.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
PureJS/WASM by default; native only when genuinely required.** Servers run via npx/MCPB on any
Sandboxfirst, layered design.** Each server keeps a thin index.ts (tool registration only) over
Tokenefficient by default.** Pagination, head/tail/section reads, snippets, and compact graph refs
ServerDescription

How to install the HTTP MCP server

{
  "mcpServers": {
    "http": {
      "command": "npx",
      "args": ["-y", "@abhishekmcp/notes"],
      "env": {
        "NOTES_DIR": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
NOTES_DIRFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use HTTP to Pure.
  • Use HTTP to Sandbox.
  • Use HTTP to Token.

Frequently asked questions

It connects HTTP to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (Pure, Sandbox, Token, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with HTTP directly.