MCP server for AI clients
Tiger ships a Model Context Protocol server. AI clients such as Claude can discover your collections, inspect request definitions, and send requests in agentic workflows without any extra tooling or scripts.
Tiger
Compare
Tiger vs Bruno: Git-Native API Clients Compared
Tiger and Bruno share the same starting conviction: API collections belong in your Git repository, not in a vendor's cloud. Both are account-free, offline-capable and open source. Bruno is excellent, well-established and has a large community. This page covers the differences honestly so you can choose the right tool for your team.
Side by side
Both tools store collections as plain files in Git and require no account. The table below focuses on where they differ.
| Capability | Tiger | Bruno |
|---|---|---|
| Collections stored as plain files in Git | Yes — .tiger files | Yes — .bru files |
| Account required | Never | Never |
| Works fully offline | Yes | Yes |
| License | MIT | MIT |
| MCP server for AI clients Tiger only | Yes — Claude and other MCP clients can list and run requests | No |
| SOAP / XML body editor Tiger only | Yes — dedicated SOAP envelope body type | No — REST and GraphQL only |
| Built-in performance runs Tiger only | Yes — p50 + p95 latency, bounded concurrency, no subscription | No — requires an external tool (k6, wrk, etc.) |
| Request chaining via capture Tiger only | Yes — capture response values and pass them to the next request | Scripts only — possible via pre/post-request JavaScript |
| Team sync | Git — one-button commit + push in the UI | Git — manual workflow outside the app |
| GraphQL with schema introspection | Yes | Yes |
| OAuth 2.0 client credentials | Yes | Yes |
| Import from Bruno | Yes | Native format |
| Import from Postman / Insomnia / OpenAPI | Yes | Yes |
| Maturity and community Bruno leads | Newer — smaller community, active development | Established — tens of thousands of GitHub stars, launched 2022 |
| Scripting ecosystem Bruno leads | Built-in capture + variables | Broad — JavaScript pre/post-request scripts, assertions, community plugins |
| Collection file format documentation Bruno leads | Internal | Documented .bru spec — ecosystem of third-party tooling built on it |
What Tiger brings to a Git-native workflow
These are the capabilities Tiger has that Bruno does not currently ship.
01
02
SOAP and XML bodies
Tiger has a dedicated SOAP envelope body editor alongside REST and GraphQL. Teams maintaining legacy enterprise integrations or XML-based services get first-class support without reaching for a separate client.
03
Built-in performance runs
Fire any request hundreds of times with bounded concurrency and read back p50 and p95 latency right inside the app. No monitor subscription, no external runner to configure.
04
Request chaining via capture blocks
Declare a capture block on any request to pull values from the response and inject them into subsequent requests automatically. Useful for multi-step flows like auth, resource creation and teardown.
05
One-button Git sync in the UI
Tiger surfaces a plain-language commit-and-push flow inside the app so the whole team can participate in version control without opening a terminal or a Git GUI.
06
Persistent per-environment cookie jar
Cookies set by one request are available to the next automatically. The jar is scoped per environment so staging and production sessions never overlap.
Choose Bruno if... / Choose Tiger if...
Both tools are solid. The right choice depends on what your team values most.
Choose Bruno if...
- You want a tool with years of real-world use and a large public community to draw on.
- Your workflow depends on JavaScript pre- and post-request scripting with a mature assertion library.
- Your team already uses the .bru file format and has tooling built around it.
- You want the broadest possible plugin and integration ecosystem today.
- Your requests are REST or GraphQL only, with no SOAP requirement.
- You prefer a tool with documented file format specifications.
Choose Tiger if...
- You want AI clients (Claude, Cursor, etc.) to read and send your API requests via MCP.
- Your team maintains SOAP or XML-based services alongside REST APIs.
- You want built-in load and performance runs without wiring up a separate tool.
- You need request chaining via declarative capture blocks rather than scripts.
- You want Git commits and pushes accessible inside the API client for non-terminal users.
- You are migrating from Bruno and want full import support with no data loss.
Common questions
01Can Tiger import Bruno collections?+
Yes. Tiger reads Bruno's .bru folder structure directly. Collections, environments, headers, query parameters and request bodies carry over. Variable references in double-brace syntax are preserved.
02Does Bruno have an MCP server for AI assistants?+
Not at the time of writing. Bruno does not ship a Model Context Protocol server. Tiger includes one, so AI clients such as Claude can list, inspect and send requests in your collections without any extra tooling.
03Does Tiger support Bruno's .bru file format?+
Tiger imports .bru collections but stores requests in its own plain-text .tiger format, which is also version-control friendly. You can export back to Postman v2.1 or curl from Tiger.
04Which tool has a bigger community?+
Bruno has a significantly larger community. It launched in 2022, has tens of thousands of GitHub stars and a broad ecosystem of community-built extensions and integrations. Tiger is newer and smaller, but adds capabilities Bruno does not currently have.
05Can both Tiger and Bruno run performance tests?+
Tiger has built-in performance runs: fire any request hundreds of times with bounded concurrency and read p50 and p95 latency inside the client. Bruno does not include a built-in performance runner; you would need an external tool such as k6 or wrk.
06Does Bruno support SOAP requests?+
Bruno focuses on REST and GraphQL and does not have a dedicated SOAP body editor. Tiger includes a SOAP envelope body type alongside REST and GraphQL, which matters for teams working with legacy enterprise services.
Try Tiger alongside Bruno
Import your Bruno collections in minutes. Both tools keep your data in Git and neither requires an account.
Free and open source (MIT). No accounts, no telemetry of your request data.