Official descriptionOpen source5d ago
wirebench/wirebench
Open-source desktop workbench for SOAP, REST, GraphQL, gRPC and WebSocket APIs — WSDL, OpenAPI and .proto…
Official descriptionOpen-source desktop workbench for SOAP, REST, GraphQL, gRPC and WebSocket APIs — WSDL, OpenAPI and .proto import, WS-Security, environments, history, a CLI and an MCP server. Projects are plain files made for git. Electron + TypeScript.
- Star count
- 1 ★ · wirebench/wirebench · read from the GitHub search API · (checked 2026-10-16 20:00:20)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-12 · last seen 2026-10-16 · seen 7× · listed by 1 sources
- Score
- score 103 · 1 ★ · 1 sources · repo
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository wirebench/wirebench;first catalogued 2026-10-12;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
Third-party quality signals






Wirebench
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
**A contract-first desktop workbench for SOAP, REST, gRPC and WebSocket APIs.**
Import a WSDL, OpenAPI, AsyncAPI or .proto contract, get correct requests generated from it, send them,
and keep everything as plain files in git.
Website ·
Download ·
User guide ·
Changelog
Why Wirebench
- **It reads the contract.** Requests are generated from the schema — the right elements, in the right order,
in the right namespaces — and responses are validated against it.
- **One tool for a mixed estate.** SOAP, REST, gRPC and WebSocket share one project, one set of environments,
one history and one HTTP stack.
- **Projects are files.** A project is a folder of small YAML and XML files, made to be reviewed and versioned
in git. Credentials never go in them.
- **Local-first, no account.** The app is fully usable on its own. Teams can share over git, a synced folder,
or a self-hosted server.
- **Built for automation.** The same saved requests run in CI from the command line, and coding agents can
drive the engine over MCP — with no AI inside the app.
Features
| Area | What you get |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **SOAP** | WSDL import with every import and include cached byte for byte; generated envelopes and a form editor; WS-Security, WS-Addressing, MTOM/SwA attachments; schema and WS-I validation |
| **REST** | OpenAPI 3.x, Swagger 1.x/2.0 and Postman Collection import; folders of requests; every body kind; cookies and redirects; response validation against the contract; Server-Sent Events rendered event by event |
| **gRPC** | .proto import and server reflection; unary and every streaming shape over HTTP/2, including interactive bidirectional streams; a JSON message editor with completion |
| **WebSocket** | AsyncAPI 2.x/3.0 import; a request per channel; a live frame timeline and a composer for text and binary messages |
| **Auth** | Basic, NTLM, Bearer, API key and OAuth2 across protocols; client certificates and custom CA bundles |
| **Inspect** | HTTP Log with a timing waterfall, search, compare and HAR export; XPath 3.1, XQuery 3.1 and JSONPath queries; History with re-send and diff; copy as curl |
| **Test** | Declarative assertions on every request; sequences with property transfer; sandboxed TypeScript pre-request scripts typed from the contract; snapshot regression against golden responses |
| **Environments & secrets** | Workspace-wide environments and endpoint overrides; ${…} property expansion; secrets kept outside project files |
| **Webhooks** | Outbound webhooks with signatures; catch URLs and callback assertions on a server-shared workspace |
| **Collaboration** | Shared workspaces over git or a synced folder, with in-app Sync and a conflict resolver; encrypted team secrets |
| **Migration** | Import of legacy single-file SOAP projects — interfaces, endpoints, saved requests, properties and environments — with a report of everything not carried over |
All of the above is in 6.1.0; the changelog says which release brought each.
A REST request and its response
Syncing a shared workspace
Install
Download the installer for macOS, Windows or Linux from the
latest release. macOS builds are signed and notarised;
Windows signing is in progress (#114). The
installation guide has per-platform
notes and silent installs.
To build from source you need Node 24 and pnpm 9 (corepack enable):
Quick start
From nothing to a real SOAP response in five minutes:
- Source
- github
· https://github.com/wirebench/wirebench
- Browse by field
- Open source
- Traction
- 1 ★
- added
- yesterday
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.
Browse all fields →
← Back to index