Http
Probe REST and webhook endpoints from the agent via MCP with curl-like requests and structured responses.
Overview
io.github.Dave-London/http is an MCP server for the Build phase that runs HTTP requests and returns structured, token-efficient responses for agent-driven API work.
What is this MCP server?
- MCP-backed HTTP client with curl-style requests
- Structured, token-efficient response bodies and metadata for agents
- Stdio npm package `@paretools/http` (v0.7.1) from Pare
- Useful for smoke-testing staging APIs without leaving the agent session
- npm package `@paretools/http` at version 0.7.1
- stdio MCP transport
- Repository: github.com/Dave-London/Pare
Community signal: 128 GitHub stars.
What problem does it solve?
Pasting raw curl output and large JSON bodies into agent chats wastes tokens and obscures the fields that matter for integration bugs.
Who is it for?
Builders debugging REST integrations, OAuth callbacks, or webhooks from inside Claude Code or Cursor.
Skip if: Load testing, browser-only flows, or production observability that needs persistent tracing and SLO dashboards.
What do I get? / Deliverables
Once connected, agents can call your APIs through MCP and work from compact structured HTTP results.
- Agent-invokable HTTP request tools with structured responses
- Faster integration debugging without manual curl copy-paste
Recommended MCP Servers
Journey fit
How it compares
Agent-side HTTP MCP tool, not Postman collections, not a dedicated API documentation skill.
Common Questions / FAQ
Who is io.github.Dave-London/http for?
Developers who want their MCP agent to send HTTP requests and read responses in a compact structured form during API integration work.
When should I use io.github.Dave-London/http?
Use it while building backends or SaaS features when you need quick request/response checks against local or staging URLs from the agent.
How do I add io.github.Dave-London/http to my agent?
Install `@paretools/http` via npm, add the server with stdio transport to your MCP config, and ensure outbound network access from the MCP host process.