Cliff Dev
Shuttle APIAPI, Socket, and MCP clientiOSmacOSiPadOS
Coming soon to the App Store

Every protocol.
One native client.

HTTP, GraphQL, WebSocket, Socket.IO, SSE, gRPC, MQTT and MCP in a single app for Mac, iPhone and iPad, with scripts, tests, a collection runner, a mock server, native Git and an assistant that does the work. No sign-in, and no server of ours.

Mac App StoreComing soonApp StoreComing soon

Version 1.0.0 · macOS 14 or later · iOS 17 or later

GETList ordersMQTTTemperature
HTTPGET{{baseUrl}}/v1/orders?status={{status}}Send
ParamsHeadersBodyAuthScriptDocstimeoutms
HeadersBulk edit+ Add
AuthorizationBearer {{token}}
X-Api-Version{{apiVersion}}
200 OK142 ms1.2 KB
ResponseHeadersConsoleTests 3/3WirePrettyRaw
{  "orders": [    {      "id": "ord_8412",      "status": "shipped",      "total": 49.90,      "paid": true    }  ],  "next": "/v1/orders?page=2"}

Protocols

Not just REST

Each transport gets the panel it actually needs. Pick one to see what it looks like.

HTTPGET{{baseUrl}}/v1/ordersSend
HTTP200 OK · 142 ms · 1.2 KB
{  "orders": [    {      "id": "ord_8412",      "status": "shipped",      "total": 49.90,      "paid": true    }  ],  "next": "/v1/orders?page=2"}

HTTP

  • Every method, plus a custom one for a server that insists on its own.
  • Six body types (JSON, text, XML, file, multipart, URL-encoded), JSON and XML highlighted as you type.
  • HTTP version, redirects, timeout, URL encoding and SSL verification are all yours to set.
  • A cookie jar per collection, matched by domain and path per RFC 6265, that you can read and edit.

Assistant

An assistant that does the work

Ask in plain words. It reads your collections, makes and changes requests, writes their tests and docs, sends them and runs folders, and every change waits for your Allow.

Anthropic · claude-sonnet-5+ New conversation
Write tests for the open request's response
Read “List orders”
Read the last response of “List orders”

Three tests: the status is 200, orders is a list, and every order has an id. I'll add them to the request.

Change “List orders”
AllowDenyAllow all in this conversation
Ask the assistant…Send

What you ask, and what the assistant reads to answer, goes to Anthropic. Secret values never do.

  • Claude or OpenAI's models with your own API key, or a model you run yourself with Ollama or LM Studio: no key, and nothing leaves your computer.
  • Each change, send and run is a card with Allow and Deny, and a change to a request or a folder stays in Collection History to undo.
  • Secret variables, secret headers and Auth credentials reach the model as •••, and credentials nobody marked secret are held back too.
  • It reads what a WebSocket, Socket.IO, SSE or MQTT connection received, and calls your MCP servers' tools.
  • Code suggestions in the script editors, dimmed after the caret, taken with Tab.
  • Conversations kept to go back to, and no assistant at all until you choose a provider.
AnthropicOpenAIOllamaLM Studio

Beyond the request

The parts you miss once the easy call works

Scripts, runs, specs, mocks, the response and the collection itself, each with its own panel.

Scripts that run natively, tests that count

Pre-request and post-response JavaScript on JavaScriptCore, with a timeout so a runaway loop cannot hang the app.

  • test() and expect() with the usual matchers and Chai's chain, JSON Schema included; results counted on the Tests tab itself.
  • Scripts written for Postman, Bruno or Insomnia run as written: pm, bru, insomnia, CryptoJS, fetch. Bruno's assert rows become tests.
  • An Assertion menu drops in a ready-made check; a Snippet menu handles HMAC, JWT, fresh ids.
  • A folder's scripts wrap every request inside it, and require('./helpers.js') loads a module kept in the folder.
  • ctx.visualize draws a response as a table or as HTML of your own, a chart included; Postman's visualizer works too.
Tests
// post-responsetest("is 200", () => {  expect(ctx.response.status).toBe(200)})test("has orders", () => {  expect(ctx.response.json().orders).to.be.an('array')})ctx.setEnv('next', ctx.response.json().next) ✓ is 200✓ has orders

Built for teams

Your repository. Your vault.

Keep a collection in Git and read its secrets from the vault your team already runs. Both are built in, with nothing else to install.

Native Git

Link a collection to a repository on GitHub, GitLab or any host that speaks Git over HTTPS: the whole repository, or a folder in it.

GitHubGitLabHTTPS + token
Git · shop
northwind/shop · main✓ synced · 2 min ago orders/list-orders.yaml  name: List orders  requestType: http  method: GET− url: "{{baseUrl}}/v1/orders"+ url: "{{baseUrl}}/v2/orders"  params: []  headers: Commit  "Move orders to v2"↑ Push   1 commit → main
  • One readable YAML or JSON file per request, folder and environment. Secrets never go in.
  • It syncs on its own, or by hand as in a Git client: commit, push, pull, stash, branches.
  • Merged request by request: when you both changed the same thing, you see both sides and pick.
  • Import a collection from a repository, its saved specs and mocks beside it.

Secrets from your vault

A secret variable says where its value is. Shuttle reads it when you send, keeps it in memory, and never saves, syncs or exports it.

HashiCorp VaultAWS Secrets ManagerAzure Key VaultGoogle Cloud Secret Manager
Secrets
HashiCorp Vault · namespace team-a✓ Signed in to Vault as approle stripeKey    → prod/api#stripedbPassword   → db/orders#password Send  read once, held in memoryAuthorization: Bearer •••• Export · Git → the reference, never the value
  • HashiCorp Vault (KV 1 and 2, AppRole, namespaces), AWS Secrets Manager, Azure Key Vault and Google Cloud Secret Manager.
  • The vault's own credentials stay in the Keychain; Test connection says who you signed in as, or for Azure, which tenant.
  • The reference travels with an export or a repository; the value never does.

Environments

Same request. Different target.

Write the request once with {{variables}}, then switch where it goes. Secrets live in the Keychain and stay out of exports unless you ask for a full backup.

HTTPGET{{baseUrl}}/v1/orders?status={{status}}Send
sends tohttps://api.staging.northwind.com/v1/orders?status=paid
VariableValueDefined in
{{baseUrl}}https://api.staging.northwind.comEnvironment
{{token}}••••••••KeychainEnvironment
{{status}}paidCollection
{{apiVersion}}2024-04-01Folder

Collection and folder variables stay the same whichever environment is picked, so a shared value is written once. When two scopes define the same name, the narrowest wins: the folder over the environment, the environment over the collection. A name nothing defines is shown greyed and struck through, and goes out as typed, so the error names it. Type {{ for every name in scope, with its value.

{{$uuid}}

and 41 more, made fresh each time

{{response …}}

a value from another request's last response

{{?OTP code}}

asked each time you send

/orders/:id

path variables, each with a row of its own

Authentication

Ten ways in

Each one is set on the request, or written once on a folder for every request inside it set to Inherit.

BearerBasicDigestAPI key

The usual

Bearer and Basic as you would expect; Digest answers the server's challenge, MD5 or SHA-256; an API key wherever the server wants it.

OAuth 2.0OAuth 1.0

OAuth

All five OAuth 2.0 grants with PKCE and refresh on send, plus several saved tokens per request, each named after the environment it came from.

AWS SigV4Hawk

Signed

AWS Signature v4 is signed at send time, after your pre-request script, since the signature covers the finished request.

NTLMAkamai EdgeGrid

Enterprise

Windows challenge-response and Akamai's own management APIs. Client certificates sit outside this list, set per host and built in memory rather than imported into your keychain. Behind a company proxy, HTTP, GraphQL and MCP requests go through the system's or your own, with its sign-in, and you can add your own CA certificate.

And also

The small things that add up

Tabs and shortcuts

Requests open in tabs on Mac and iPad, and most Mac shortcuts can be rebound.

Your look

Light, dark or system, four editor themes and a font size; on a Mac, the response below or beside.

Accessible

Labels for VoiceOver, clearer secondary text under Increase Contrast, and panels that stop sliding under Reduce Motion.

Docs built in

A Docs tab on each request and folder; export a folder's as one HTML page or as Markdown.

A manual inside

A welcome tour and a manual you can search, in all twenty-one languages.

Quick editing

Edit a table as text, put a note on a param, header or variable, import a .env file as variables.

A keyboard bar

On iPhone and iPad, the punctuation a request needs sits one tap above the keyboard.

Hard to break

An HTTP response over 64 MB is stopped and a gzip bomb is refused, with a message rather than a crash.

Why Shuttle

What changes

Against how most API clients are built today.

ShuttleMost clients
The app itselfNative SwiftUIWeb wrapped in Electron
Getting startedNo account, everAn account for most features
Where your data livesYour device, your iCloud, your GitTheir cloud, to sync
Protocols8, including gRPC, MQTT, MCPFive to eight, MQTT rarely
AI assistantAn agent on your own key or a local modelOn their cloud, or no agent at all
GitBuilt in, one readable file per requestBehind an account or a paid plan
Team vaultsHashiCorp, AWS, Azure, GoogleTheir top paid tier, if at all
Contract testingEvery HTTP response, against the specWritten by hand, test by test
Interface languageTwenty-one languagesEnglish, at most one more
iPhone and iPadThe same collections, nativeDesktop only

Migration

Bring what you have

Pick the app a file came from, or paste a collection or give its URL and Shuttle works the format out. Each import lands as a new collection, its folders nested as they were, each with its own settings; nothing already there is replaced. Postman, Insomnia and Bruno scripts come too, and run as written.

Import from

PostmanInsomniaBrunoThunder ClientHAR.http / .restOpenAPI 3

Export as code

cURLC#C++DartGoJavaNode.jsKotlinPHPPythonRubyRustSwift+8

Twenty-one languages

EnglishFrenchSpanishGermanItalianDutchSwedishPolishCzechPortugueseRomanianGreekTurkishRussianUkrainianHindiIndonesianJapaneseKoreanChinese (Simplified)Chinese (Traditional)

No account, ever

Nothing to sign up for, no server of ours between you and the API, no analytics of any kind.

Secrets in the Keychain

Auth credentials, secret variables, cookie values and client keys live in the system Keychain, not in the JSON files, and stay out of exports unless you ask for a full backup.

Your own iCloud

Turn on iCloud sync and collections, environments and history follow you between your Mac, iPhone and iPad, with your Git, vault and assistant settings too if you choose. Tokens and keys stay in each device's Keychain.

Ready when you are

A native API client for the Mac, and the same collections on your iPhone and iPad.

Mac App StoreComing soonApp StoreComing soon

Version 1.0.0 · macOS 14 or later · iOS 17 or later