dev.kurlo/kurlo·Dev tools

Kurlo

Run, write and test the API requests saved in a Kurlo workspace, the open source API client.

Stars
7
Version
2.3.2
License
MIT
Review
Passed
Language
TypeScript
Last commit
1h ago
Forks
0
Open issues
6
Registry update
Oct 15, 2026
api-clientdesktop-appgolanggraphqlgrpchttp-clientlocal-firstpostman-alternativerest-clientsveltewailswebsocket

Connect

npm
Terminal
$claude mcp add kurlo \  -- npx -y @kurlo/[email protected]

Environment variables

Nothing to configure — it works as is.

Security review

Review passed

Reviewed 7m ago.

metadata
scanned
packages
1 checked

No findings.

Tools

This server runs on your machine, so its tool list is not fetched before install — the README below describes what it offers.

@kurlo/cli

The command line of Kurlo, a free, open-source desktop API client. It runs the requests and test scripts of a Kurlo workspace, and serves a workspace to AI agents as an MCP server. You don't need the desktop app installed to use it.

npm install -g @kurlo/cli
kurlo --version

EACCES: permission denied on npm install -g

npm could not write to the folder that holds global packages. It happens with Node from the nodejs.org installer, which puts that folder in /usr/local, owned by the system. It is not specific to Kurlo, and any global package fails the same way. Either skip the install and run the CLI with npx -y @kurlo/cli, or move global packages into your home folder once:

mkdir -p ~/.npm-global && npm config set prefix ~/.npm-global
echo 'export PATH="$HOME/.npm-global/bin:$PATH"' >> ~/.zshrc && source ~/.zshrc
npm install -g @kurlo/cli

Node installed with Homebrew, Volta or nvm keeps global packages in your home folder already. Avoid sudo npm install -g: it works, but leaves root-owned files that break later installs.

Connect an AI agent

Add Kurlo to every AI client on your machine (Claude Code, Claude Desktop, Codex, Cursor, VS Code, Windsurf, Gemini CLI):

npx -y @kurlo/cli mcp install --env Staging

Add --project to write the repository's shared .mcp.json and .cursor/mcp.json instead, --dry-run to see the changes first, and run kurlo mcp uninstall to take Kurlo out again. To set it up by hand instead:

Claude Code:

claude mcp add kurlo -- npx -y @kurlo/cli mcp --env Staging

Codex:

codex mcp add kurlo -- npx -y @kurlo/cli mcp --env Staging

Cursor, Claude Desktop and other clients with a JSON config:

{
  "mcpServers": {
    "kurlo": {
      "command": "npx",
      "args": ["-y", "@kurlo/cli", "mcp", "--env", "Staging"]
    }
  }
}

The agent can list your requests and environments, run a saved request or a whole collection with its tests, and send one-off calls that use your {{variables}}. It can also add and change saved requests with their tests, save responses as examples and set environment variables, so the collection stays in step with your code. Secret values are sent to your API and masked as [secret] in everything the model sees, and never written to the workspace. Mark an environment protected in the app to keep agents away from it.

With no workspace argument, kurlo mcp serves the workspace the desktop app has open. Pass the folder that contains kurlo.yml to serve a Git-backed workspace instead:

npx -y @kurlo/cli mcp ./api --env Staging

Run collections in CI

npx -y @kurlo/cli run ./api --env CI --reporters cli,junit

The run exits non-zero when a request fails or a test does not pass.

Docs

Prebuilt binaries are published for macOS, Linux and Windows on x64 and arm64. MIT licensed.

From the server's repository — third-party content, read it before running anything it suggests.

More in Dev tools

Listing from the official MCP Registry · repository facts from GitHub, 10m ago.