M
metamug/plunger
Your AI agent calls the API.
★ 11·更新 2026-11-07
在 GitHub 查看 ↗直链 · 无中转页
我们没有从该仓库取到可核对的安装命令,也没有公开的远端端点。这两样都没有时,我们不出配置——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 11 ★ · metamug/plunger · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 11 ★ · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
metamug/plunger;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
Plunger
以下摘录自该仓库的 README(片段)
Unclog your API.
Your AI agent calls the API. Plunger shows you what it actually sent and what came back.
An HTTP client built for AI agents. An MCP server and a command line that send requests safely (a secret never reaches the output,
an undefined variable is refused), return only the values the agent asked for, and write every change to a tamper-evident log,
plus a small native window to see and check what the agent did.
Make the request. See the JSON. Move on.
Get it from the Microsoft Store
· Windows zip (about 3.6 MB, no installer, not code-signed)
· Linux (command line and MCP server tested; the window is not yet)
· MIT license
The real app: every request an agent sends appears in your window, tagged MCP , with secrets kept hidden. Setup and details .
Watch the 2½ minute walkthrough on YouTube (narrated with a synthetic voice).
## Why?
Sometimes you don't need another platform. You just need to see what the API returned.
AI can write the code. AI can build the pipeline. We still look at the diff before we push. We still look at the logs when something feels wrong. And we still look at the JSON when an API doesn't do what we expected.
Seeing is believing. Plunger is for the moment between "I think it works" and "I can see it works."
We wanted a plunger. So we made one.
## What is Plunger?
A small desktop app that sends an HTTP request and shows you what came back.
Request: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS. Params, headers and a Bearer token field.
Body: JSON, XML, form-urlencoded, raw text, or multipart form-data with real file uploads.
Response: status, time and size, the headers, and the body as a collapsible JSON tree. Copy it or save it to a file.
Variables: {{name}} anywhere in the request, plus {{$uuid}}, {{$timestamp}}, {{$timestampMs}}, {{$isoTimestamp}}, {{$randomInt}}, {{$randomHex}}, {{$randomString}} and {{$env:NAME}} for reading an OS environment variable at send time. A request with an undefined variable is refused, never sent with the placeholder in it.
Import and export: paste a curl command (bash or Windows cmd, including -F uploads) or a PowerShell Invoke-WebRequest / Invoke-RestMethod command, such as DevTools' Copy as cURL or Copy as PowerShell; or open a HAR file. Copy any request back out as curl (bash), curl (Windows cmd), PowerShell or a JavaScript fetch call with Ctrl+Shift+C or File > Export request, shown with syntax highlighting.
Keep what matters: local history, named saved requests (Ctrl+S) and tabs (Ctrl+T).
Local HTTPS: skip certificate checks for a self-signed dev server, with a warning that stays visible while it's on.
Behind a proxy: Plunger uses your system proxy settings and the HTTP_PROXY, HTTPS_PROXY and NO_PROXY environment variables.
Find it again: the sidebar filter searches your whole history and saved requests by URL, method, name or status; right-click a value in a JSON response to copy its path or value.
It's a native program, not a web page, so it reaches whatever your machine can reach: localhost, a dev box on your network, an API that sends no CORS headers.
## For AI agents
See the JSON, even when an AI sent the request.
Your AI agent calls the API. Plunger shows you what it actually sent and what came back.
An HTTP client built for AI agents. An MCP server and a command line that send requests safely (a secret never reaches the output,
an undefined variable is refused), return only the values the agent asked for, and write every change to a tamper-evident log,
plus a small native window to see and check what the agent did.
Make the request. See the JSON. Move on.
Get it from the Microsoft Store
· Windows zip (about 3.6 MB, no installer, not code-signed)
· Linux (command line and MCP server tested; the window is not yet)
· MIT license
The real app: every request an agent sends appears in your window, tagged MCP , with secrets kept hidden. Setup and details .
Watch the 2½ minute walkthrough on YouTube (narrated with a synthetic voice).
## Why?
Sometimes you don't need another platform. You just need to see what the API returned.
AI can write the code. AI can build the pipeline. We still look at the diff before we push. We still look at the logs when something feels wrong. And we still look at the JSON when an API doesn't do what we expected.
Seeing is believing. Plunger is for the moment between "I think it works" and "I can see it works."
We wanted a plunger. So we made one.
## What is Plunger?
A small desktop app that sends an HTTP request and shows you what came back.
Request: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS. Params, headers and a Bearer token field.
Body: JSON, XML, form-urlencoded, raw text, or multipart form-data with real file uploads.
Response: status, time and size, the headers, and the body as a collapsible JSON tree. Copy it or save it to a file.
Variables: {{name}} anywhere in the request, plus {{$uuid}}, {{$timestamp}}, {{$timestampMs}}, {{$isoTimestamp}}, {{$randomInt}}, {{$randomHex}}, {{$randomString}} and {{$env:NAME}} for reading an OS environment variable at send time. A request with an undefined variable is refused, never sent with the placeholder in it.
Import and export: paste a curl command (bash or Windows cmd, including -F uploads) or a PowerShell Invoke-WebRequest / Invoke-RestMethod command, such as DevTools' Copy as cURL or Copy as PowerShell; or open a HAR file. Copy any request back out as curl (bash), curl (Windows cmd), PowerShell or a JavaScript fetch call with Ctrl+Shift+C or File > Export request, shown with syntax highlighting.
Keep what matters: local history, named saved requests (Ctrl+S) and tabs (Ctrl+T).
Local HTTPS: skip certificate checks for a self-signed dev server, with a warning that stays visible while it's on.
Behind a proxy: Plunger uses your system proxy settings and the HTTP_PROXY, HTTPS_PROXY and NO_PROXY environment variables.
Find it again: the sidebar filter searches your whole history and saved requests by URL, method, name or status; right-click a value in a JSON response to copy its path or value.
It's a native program, not a web page, so it reaches whatever your machine can reach: localhost, a dev box on your network, an API that sends no CORS headers.
## For AI agents
See the JSON, even when an AI sent the request.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/metamug-plunger/)
- 来源
- awesome · https://github.com/metamug/plunger
- 按领域浏览
- MCP 服务
- Traction
- 11 ★
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。