Features

API client, webhook inspector, localhost tunneling, SSH terminal, and 24/7 monitoring — all in one desktop app.

Act III

The details that
make it click.

COLLECTIONS

One drag from Postman.
Or Bruno. Or Insomnia.

Import your existing collection in a single drop — Postman v2.1, Bruno, Insomnia, OpenAPI 3.x. Environments, variables, auth flows, and scripts come with it. No reformatting, no rewriting, no “starting fresh.”

drop postman_collection.json 7.2 KB
→ imported 48 requests · 4 environments
# auth scripts preserved · variables resolved
READY stripe / staging → send
HTTP WS SSE MQTT MCP
WS wss://ws.kraken.com/v2 · open
← {"channel":"ticker","data":[...]}
SSE /v1/events/stream · listening
MQTT device/+/telemetry · subscribed
MCP filesystem-server · 12 tools

CROSS-PROTOCOL

One client for
every protocol.

HTTP, WebSocket, SSE, MQTT, and an MCP server inspector — first-class clients for each, not afterthoughts. Stream tickers, listen to event feeds, debug an MCP tool call, all in the same workspace.

PRIVACY

Your data stays on
your machine.

Collections saved as .kite files. Commit them to Git alongside your code. No cloud sync forced on you. No account required for local features. For teams: self-host the backend on your infra.

Git-friendly No CORS issues Open source
project/
src/
package.json
stripe.kite
environments.kite
ssh-hosts.kite
.gitignore
$ git add *.kite && git commit -m "update collection"

REMOTE SSH

SSH into servers.
Run requests from there.

Built-in terminal with full SSH host management. Import from ~/.ssh/config on first launch. The killer feature: hit “Send from staging” and your API request executes on that server — solving IP whitelisting, geo-restrictions, and “run curl from prod” workflows without leaving Kite.

SSH terminals Port forwarding SFTP Snippets
ubuntu@staging root@prod-bastion
ubuntu@staging:~$
# Request sent FROM staging server
POST api.stripe.com/v1/charges
source: staging-server (52.14.88.201)
200 OK · 234ms · IP whitelisted
Forwards: localhost:5432 → staging-db:5432 active

Port forwarding

→ localhost:5432 via staging → rds:5432
→ localhost:6379 via prod-bastion → redis:6379

SFTP

put ./build.tar.gz → /srv/releases/
get /var/log/app.log

Snippets

⌘+/ → restart-pm2
⌘+/ → tail-app-logs

EVERYTHING ELSE

Port-forward, SFTP,
saved commands.

All the SSH-adjacent things you actually use, in the same window. Tunnel a remote Postgres to localhost. Copy a build artifact up to a release dir. Bind your most-used remote commands to keyboard shortcuts. No third tab required.