Pare Http
Let your coding agent perform GET, POST, and HEAD calls against APIs and webhooks with structured JSON instead of fragile shell curl one-liners.
Overview
Pare HTTP is a MCP server for the Build phase that runs GET, POST, and HEAD HTTP requests and returns typed JSON for agent-driven API and integration work.
What is this MCP server?
- Typed JSON responses for GET, POST, and HEAD requests
- stdio MCP transport via npm package @paretools/http (v0.8.1)
- Part of the Dave-London Pare toolkit on GitHub
- Structured operations replace ad-hoc curl in agent workflows
- Fits API probing, webhook checks, and smoke tests from Claude Code or Cursor
- Server version 0.8.1
- npm package @paretools/http with stdio transport
- 3 HTTP methods documented: GET, POST, HEAD
Community signal: 128 GitHub stars.
What problem does it solve?
Agents default to messy shell HTTP commands whose output is hard to parse and easy to get wrong on headers or methods.
Who is it for?
Indie developers wiring REST or webhook integrations who want repeatable, parseable HTTP from inside Claude Code or Cursor.
Skip if: Teams needing a GUI API client, browser automation, or OAuth-heavy flows with built-in token refresh.
What do I get? / Deliverables
After you register the stdio server, your agent can call live endpoints with consistent JSON results you can chain into fixes and tests.
- Structured JSON results from GET, POST, and HEAD operations
- Repeatable HTTP checks executable from agent tool calls
- stdio MCP server entry wired into your local agent config
Recommended MCP Servers
Journey fit
HTTP calls sit in the build phase when you wire third-party APIs, test endpoints, and validate integrations before ship. Integrations is the canonical shelf because this server exists to call external HTTP services during implementation and debugging.
How it compares
MCP HTTP integration, not a Postman replacement or a full backend framework.
Common Questions / FAQ
Who is pare-http for?
Solo and indie builders using MCP agents who need structured GET, POST, and HEAD calls while building APIs and integrations.
When should I use pare-http?
Use it during build when you are testing endpoints, verifying webhooks, or debugging third-party HTTP from your agent session.
How do I add pare-http to my agent?
Install @paretools/http from npm, configure it as a stdio MCP server in Claude Code or Cursor per your client’s MCP settings, pointing at the published package.