Tiger MCP
A free Postman-style API client with collections in .tiger files and a built-in MCP server so an agent can run your requests.
- 107 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The `run_request` tool sends real requests with your auth data
- Server response bodies enter the model context
Install
- Works in
Manual install
{"mcpServers": {"tiger": {"command": "node", "args": ["/path/to/tiger/out/mcp/server.mjs", "/path/to/your/collection"]}}}The Claude Desktop config from the Connect an AI assistant section. The server is first built with `npm run build:mcp`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The `run_request` tool sends real requests with your auth data
- Server response bodies enter the model context
This is third-party code. Review the repository files before installing.
What it does
Tiger stores each REST, GraphQL or SOAP request as a plain-text `.tiger` file in your folder, so collections can be committed to Git, branched and reviewed. The app for macOS, Windows and Linux works offline with no account or cloud. It has environments with variables and secrets, Bearer, Basic, API key and OAuth 2.0 auth, proxies, client certificates, load testing, code snippets and import from Postman, Insomnia, Bruno, OpenAPI and WSDL. The built-in MCP server gives assistants four tools: `list_requests`, `list_environments`, `get_request` and `run_request`. Every response contains the status code, timing, headers and a pretty-printed body. This way an agent in Claude Code or Cursor calls real endpoints through saved requests with your environments instead of inventing curl. The server is built with `npm run build:mcp`.
Who it is for. API developers and testers who keep requests in Git and want an agent to run them with real URLs and environments.
Good fit when
- An agent should find out why the `create-user` request returns 401 on staging.
- The request collection lives in Git and is reviewed in pull requests.
- A call chain: log in, take the token, then call a protected method.
- A quick health check: run requests and flag non-2xx responses.
- A team moves off Postman and wants files instead of a cloud account.
Not a fit when
- Requests must not hit live servers on the agent's initiative.
- Cloud sharing of collections with in-service comments is needed.
- You do not want to build the MCP server from source: the README shows no ready package.
Example request
List the requests in the collection, run create-user against staging and explain why 401 comes back.MCP
- Transport
- stdio
- Authentication
- not required
Limitations
The MCP server is built from source with `npm run build:mcp`, then the path to `out/mcp/server.mjs` and the collection folder is written into the client config. The `run_request` tool sends real HTTP requests with your auth data, so prefer test environments. The collection stays on disk while server responses enter the model context. The README names versions 0.7.0 and 0.8.1 in different places, so check the releases page. The repository was last updated on 5 November 2026 and uses the MIT licence.
How to disable. Remove the `tiger` entry from the MCP client configuration and the app in the usual way. `.tiger` files stay in the collection folder.
FAQ
Which MCP tools exist?
Four: `list_requests`, `list_environments`, `get_request` and `run_request`. Every response includes status, timing, headers and body.
Is an account needed?
No. The app works offline and collections sit in plain files in your folder.
Where can requests be imported from?
From Postman v2.0 and v2.1, Insomnia v4 and v5, a Bruno folder, OpenAPI 3, Swagger 2, WSDL and a pasted curl command.
Which auth types are supported?
Bearer, Basic, API key and OAuth 2.0 (client credentials), plus proxies and client certificates via PEM or PFX.
How to connect to Claude Desktop?
Add a `tiger` server to `claude_desktop_config.json` with the `node` command and paths to `out/mcp/server.mjs` and your collection.
Discussion
No questions or reviews yet.
Related
MCP serversMCP server: an agent sends GET, POST, PUT, DELETE and PATCH to your REST API and gets back status, headers and body
Postman's official MCP server: workspaces, collections, specs and environments straight from your agent
The SmartBear server gives the agent BugSnag, Swagger, Zephyr, QMetry and PactFlow: errors, API specs, test cases and contracts
A Rust HTTP load-testing tool with an MCP server: an agent runs a benchmark and gets latency percentiles and status breakdowns.
kogiQA MCP gives an agent a browser that finds page elements without selectors, for debugging web apps and writing e2e tests
tapflow MCP server: an agent controls iOS simulators and Android emulators on your Mac and replays flows for CI
README in short
The README presents Tiger as an alternative to Postman and Bruno, gives a download table for three systems and a separate section on connecting AI assistants.