[ overapi ] · a powerful API client, built for agents
Bring in any API — a server on your Mac, a spec, SOAP, or a web app you record — and work with it like the best desktop clients. Then one reviewed pass makes it agent-ready, and it’s an MCP server in Claude Code or your team’s overgo. No account, no cloud; secrets stay in the keychain.
[ ways in ] · bring it in however you can
Swagger behind a login, SOAP, a wiki page, a Postman export — or nothing but the calls a web app makes. Every way in ends as requests you can send, and any token it finds goes to the keychain, never into the project.
New API lists what’s listening locally and imports a served spec in one click. Spec behind a login? Paste a token and it fetches it anyway.
:4010 Acme Orders node ✓ spec · 7No spec at all? Your own claude reads the service’s routes, request and response classes and sign-in — read-only — and drafts every endpoint.
✦ Read its codeOpenAPI 3, Swagger 2, GraphQL, a HAR capture, a Postman v2 collection, or a WSDL. GraphQL queries become reads and mutations writes; SOAP operations get typed arguments.
acme-orders.openapi.yaml“Copy as cURL” from the network tab. Ids in the path become arguments, the values you sent become the example.
curl '…/orders/1002' -H 'Authorization: Bearer …'PDFs, Markdown, a docs URL or pasted wiki text. claude finds the real spec files if the site links to them, and drafts one if it doesn’t.
Draft the APIUse the app in overapi’s browser — or your own Chrome, password manager and all — and its API calls become requests.
chrome · app.acme.exampletip: copy a cURL, a spec URL or a docs page and press ⌘V anywhere in the app · ⌘K jumps to any request
[ the workbench ] · use it like any API client
What’s being sent sits on top, one line each; everything else the request takes waits below as chips. An id another request gives back is picked by name from what it answered — or taken from it fresh each time — and path values show by name right in the URL bar.
1 — sent as picked, or taken from the list each run[ record ] · no spec? use the app
Sign in and use a web app in overapi’s browser — or your own Chrome, on overapi’s own profile so your password manager stays — and every call it makes to its backend is kept. overapi spots the sign-in, follows ids from one response into the next, and turns routes into requests with real examples.
Or press Explore for me and it clicks around on its own, reading only: it never submits a form or presses anything like buy, delete, send or sign out, and any request that isn’t a read is stopped before it leaves the browser.
[ agent-ready ] · one reviewed pass
Point an agent at an API raw and it gets ids it can’t find and a DELETE it shouldn’t see. Make it agent-ready tidies what a recording picked up, fixes values that never change and connects the chains — then your own claude or codex writes descriptions, argument help, clearer names, what to hide, a brief for the agent and example questions.
Tidying, fixed values and chains are worked out by rules, so they’re the same every time. AI only writes what needs words.
Past about 40 tools, agents pick worse and pay for the list every turn. The Tools tab shows the budget and suggests what to turn off, and why.
Leaked secrets, what agents can reach, prompt injection in descriptions, personal data in examples. Critical and high findings block team publishing until fixed or accepted with a reason.
Ask a question in plain words. Your claude answers through this API’s own MCP server, read-only, and you watch every call — then save the run as a test.
[ tests ] · proof, not a promise
Every Try as an agent run can be saved as a test: the calls the agent made, in order. So can a recording of you using the app. overapi passes ids from one response into the next and checks every answer’s status and shape — so when the API changes underneath your agents, a test fails loudly before an agent fails quietly.
Run them in the app before you publish, or in CI with overapi test --junit. Writes are opt-in per step and never run on production. Load tests of reads are there too, behind a setting that’s off by default.
[ safety ]
Every tool is read, write or destructive — POST …/search counts as a read; DELETE and POST …/delete are destructive. Write tools stay hidden until an environment allows writes, and destructive ones also need confirm: true and carry destructiveHint, so clients ask you first.
Secrets live in the keychain and are scrubbed from everything shown or returned. A project someone else shared — a clone, a pull — can’t use your secrets until you’ve reviewed where it sends requests and how it signs in, and allowed it. Your browser sign-ins never publish.
[ workspaces ] · the APIs of one product
Group the services that belong together. One of them signs the others in, one grid sets where each runs in every environment, and they’re served together as a single MCP server — with ids flowing from one service to the next.
Each stays its own API; the workspace only adds what they share.
[ publish ] · one project, every agent
Each install is its own MCP server for one environment: the same tools, that environment’s base URL, sign-in and writes setting. A running server notices edits within seconds and tells the client its tools changed — no restart. And the Publish sheet shows whether its tests pass before anything goes out.
Adds the environment to Claude Code — and so to overcli, which uses the same list. Codex and any MCP client get a config to paste. Nothing is uploaded.
claude mcp add acme-orders-staging --scope user \ --env API_TOKEN=<API_TOKEN> -- \ overapi serve overapi.json --env staging
A project is a folder — overapi.json and a .gitignore that keeps .env out. That’s the shared collection: no account, no cloud workspace. Teammates open it in overapi or serve it from the command line.
overapi check overapi.json
overapi call overapi.json list_orders \
--env local --args '{"status":"open"}'
overapi serve overapi.json --env local[ download ] · grab a build
overapi 0.1.0 is pre-1.0, and it updates itself — on the stable channel, or beta if you’d rather. The macOS builds are Developer-ID signed and notarized by Apple, with the same Developer ID as the rest of the family, so they open on a double-click. It comes with a fictional REST API, a SOAP service and a web app to try it on.
macOS only for now. The AI steps — reading code or docs, Make it agent-ready, Try as an agent — use your own claude or codex CLI, signed in. Every build and its checksums are on the releases page.
[ faq ]
Generators are the easy part, and they need a spec. overapi starts from whatever you have — a server on your Mac, its source code, a WSDL, the docs, or a recorded web app — and spends its effort on what generators skip: one reviewed pass that names, connects and documents the tools, a budget so there aren’t too many, a security scan, writes kept from agents until you allow them, and tests from real traffic.
No. overapi is an API client that runs on your machine. Projects are JSON files on disk, secrets are in the keychain, and the MCP server it makes runs locally when Claude Code or Codex starts a session. The only copy that ever leaves is one you publish to your own org’s overgo — without secret values.
Environments start read-only, and tools that change data aren’t even listed until an environment allows writes. Allowing writes on production means typing its name. Destructive tools also need confirm: true on every call and carry the MCP destructiveHint, so clients that ask first will ask. A tool that isn’t on doesn’t exist, as far as the agent can tell.
Only where you use it. Discovery from documentation sends your docs to the claude or codex CLI already on your machine, which reads them with file-reading tools only — no shell, no web, no MCP. It writes an OpenAPI draft that goes through the normal importer, and drafted requests are marked until you’ve sent them once. The agents you publish to see what the tools return, capped by each tool’s response limit.
Nothing. Like the rest of the family it’s Apache 2.0, with no account and no paid tier. The AI features use a CLI you already have and are already signed in to.
Anything you add to Claude Code from overapi shows up in overcli too, since it uses the same list. Publishing to your org goes through overcli, which signs in to your overgo; an admin approves it there and workers can be given it as a tool — the same way overdb hands over a database connection.
[ family ] · over your tools, not instead of them
One window over your agent CLIs — then put them in a loop.
overgit →A better git client — and one ticket across many repos.
overdb →Every environment at once — and branches of your data.
A powerful API workbench — ready for agents.
overcli for your whole team — on your own server.