

Tiger API Client
Like
Free, open source, git-native API client. A local-first, account-free Postman alternative with a built-in MCP server, SOAP/GraphQL, request chaining and performance runs.
Features
Properties
- Privacy focused
- Local-First
Features
Git Support
- Works Offline
- Ad-free
- No registration required
- Dark Mode
- No Tracking
- OAUTH
- OpenAPI Integration
- Variables
Git integration
GraphQL integration
- Keyboard Navigation
- SOAP API
- Support for Keyboard Shortcuts
Tiger API Client News & Activities
Highlights All activities
Recent activities
- POX updated Tiger API Client
- POX added Tiger API Client as alternative to Postman, Insomnia REST Client, Yaak and ApiArk
- POX updated Tiger API Client
- POX added Tiger API Client
Tiger API Client information
No comments or reviews, maybe you want to be first?
What is Tiger API Client?
Tiger is an open source API client where every request is a plain .tiger text file on disk. Commit your collections, branch them, and review API changes in pull requests the same way you review code. No account required. No cloud sync. No lock-in.
On top of the git-friendly storage model, Tiger adds a glass UI with light and dark themes, a full importer suite, an MCP server so AI assistants (Claude, Cursor) can run requests directly, and a request chaining system to capture response values into variables for the next call.
Why Tiger?
- Collections as plain text in Git. A collection is a folder of .tiger files. Diff them, branch them, and review API changes in pull requests. Every field is human-readable.
- No account, fully offline, local-first. Tiger never phones home for your data. Everything lives in a folder you own.
- MCP server for AI assistants. Claude, Cursor, and any MCP-compatible assistant can list, read, and run requests from your collection without leaving the chat. Tiger is the only MCP API client built this way from the ground up.
- Environments and secrets. Named variable sets with {{variable}} interpolation in URLs, headers, query params, bodies, and auth fields. Secret variables are masked in the UI.
- Request chaining. Capture values from a response (status code, header, or a JSON path like body.data[0].id) and write them into environment variables for the next request.
- Dynamic variables. {{$uuid}}, {{$timestamp}}, {{$isoTimestamp}}, and {{$randomInt}} are re-evaluated on every send.
- OAuth 2.0, proxy, client certificates (mTLS). Client credentials grant, Bearer, Basic, and API key auth. HTTP/HTTPS/SOCKS proxy support. Custom CA bundles and client certificate authentication via PEM pair or PFX/PKCS12 file.
- GraphQL. Dedicated body type with a separate variables pane.
- SOAP and XML. Send raw XML bodies for SOAP/WS-* APIs the same way you would for REST.
- JSON prettify and minify. Format button and syntax highlighting in the editor and response panel, with Pretty/Raw and word-wrap toggles.
- Collection runner. Run every request in a collection or folder sequentially with live pass/fail verdicts from your script tests, capture chaining between requests, and a stop button.
- Performance runs. Fire N requests with a configurable concurrency level and get back min, max, avg, p50, and p95 timings.
- Multipart and file upload. multipart/form-data bodies mix text fields and file rows with a per-row file picker; file paths live in the .tiger format as @file: values.
- Response power tools. Search inside any response with Cmd/Ctrl+F (match cycling and highlights), preview HTML responses in a sandboxed frame, and view image responses inline.
- Code generation. Turn any request into a curl command or a JavaScript fetch snippet.
- Cookie jar. Persist cookies between sends and sessions, with automatic cross-origin stripping on redirects.


