--- title: "Postman locked your team out. Elva lets them back in. · Elva" description: "Import your Postman collection into Elva. Unlimited teammates, a catalog of every endpoint, and one hosted MCP server, all on the free plan." canonical: "https://getelva.ai/postman" lastModified: "2026-10-07T15:49:49.502Z" --- Animation: in a Postman Free workspace, invites to four teammates each come back "Team plan required". The same workspace then becomes Elva Free: every invite flips to Joined, the team grows to 12 members, and a hosted MCP server appears with Claude, Cursor, and ChatGPT calling it. # Postman locked your team out. Elva lets them back in. Import the collection. Unlimited teammates. One hosted MCP. [Import a collection](https://app.getelva.ai/signup) [See what stays free](#free) - **Unlimited**members - **1 repo**unlimited endpoints - **Spec**generated from code - **1 hosted MCP**1,000 calls a month Postman, March 2026: the Free plan is limited to one user and can’t create a team. [Their docs](https://learning.postman.com/docs/billing/about-plans) Postman Free Elva Free Same collection. Drag the line. Left: Postman Free. Right: Elva Free. 01 Import ## Bring the collection. Import takes a minute. Everything you built in Postman comes with you. Nothing to rewrite. ### Everything comes with it Requests, folders, environments, and auth. The collection works the minute it lands. ### Collection or spec, either works Start from the Postman export or an OpenAPI file. Connect the repo later and the spec comes from code. ### The team comes too The people who already use the collection join with one paste. Seats stay free. 02 Beyond the client ## Everything Postman Free leaves out The client was never the hard part. This is what your APIs need once a team and its agents depend on them. Catalog, insights, and a hosted MCP are on Free. Paid plans add logs and contracts, and raise the volume. acme/payments-api 214 endpoints, 12 services payments 38 endpoints A 92% search 12 endpoints A 90% identity 24 endpoints B 84% webhooks 9 endpoints B 80% reports 31 endpoints C 73% billing 17 endpoints D 61% billing is the weakest, fix it first **Postman:** the API Catalog is an Enterprise-plan feature. [Their docs](https://learning.postman.com/docs/api-catalog/overview) Your API results by category payments-api Design 92% Developer experience 84% AI readiness 71% Security 64% Performance 59% C to B AI readiness, rescored in 42s - 31 descriptions written from code - 12 response schemas typed - Auth documented on billing routes Fix all with AI **On Free:** collection-level scores and 10 AI fixes a month. Paid plans add endpoint-level scores and more fixes. Payments MCP Hosted by Elva $npx elva mcp add payments Live at mcp.elva.dev/acme-payments Claude Desktop 6 tools used 129 calls today Cursor 4 tools used 89 calls today ChatGPT 3 tools used 34 calls today 214 of 1,000 calls this month Free plan **Postman:** the MCP Generator hands you a ZIP to run and host yourself. [Their docs](https://learning.postman.com/docs/postman-ai-developer-tools/mcp-servers/generate/) 847 agent calls in the last 24 hours mcp.elva.dev/acme-payments Requests **847** _up 6.7% on yesterday_ Avg response **138ms** _P95 412ms_ Error rate **3.2%** _27 failed_ Tokens **124k** _1,240 a call_ 14:02:35 Cursor \*\*\*\*3e1b get\_payment\_status 200 71ms 14:02:31 Claude \*\*\*\*7f2a create\_invoice 200 141ms 14:02:27 ChatGPT \*\*\*\*7f2a list\_payments 200 88ms 14:02:23 Partner bot \*\*\*\*a4c0 delete\_webhook 403 12ms 14:02:19 Cursor \*\*\*\*3e1b get\_customer 200 64ms 14:02:15 Claude \*\*\*\*7f2a refund\_payment 200 112ms **On Free,** the hosted server reports its status and calls today. Per-agent and per-key logs come with the gateway on Scale. With a server you host yourself, they are yours to build. Contract · payouts-partner, v1.4 Published to spec, docs, MCP, SDK Partner Internal Public AI agent DELETE /builds/{id} Breaking Build:   id: string \- buildLog: string + logUrl: string (uri) **2** services read buildLog **1** partner affected **1** MCP tool uses the field Publish blocked by policyReview **Postman** has no per-audience contracts. In Elva, Startup adds an internal contract; Scale adds every audience and policies that block a breaking change. 03 Free plan ## What stays free Request testing is a tie. The rest is the team, the catalog, and a hosted MCP. | Feature | Postman Free | Elva Free | | --- | --- | --- | | Team members | 1, can’t create a team | Unlimited | | API catalog | Enterprise plan only | Every endpoint in 1 repo | | Spec from code | You write and sync it | Generated from the repo | | Hosted MCP | Generates a ZIP, you host it | 1 server, 1,000 calls a month | | Collections and request testing | Both. Tie. | | Price shape | Free for one, then per seat | Free for the team, then flat | 04 Switching ## Keep Postman while you switch Some of your team will want the Postman client for a while. Let them. On Scale, every sync writes a fresh Postman collection, so nobody works from a stale copy. Run both for a week, then decide. payments-api activityone commit, everyone in sync 1. **Jake** pushed a change to the repoa91f2c4 add refund reason 14:02 2. **Elva** updated the specPOST /v2/payments/{id}/refund now takes reason 14:02 3. **Elva** exported a fresh Postman collectionpayments.postman\_collection.json v38 14:02 4. **Ryan** imported it into PostmanStill in the client, already up to date 14:05 5. **Claude** called refund\_payment with the new fieldthrough the hosted MCP 14:06 ## Postman locked your team out. Elva lets them back in. Import your collection and bring the whole team. Free on your first repo, no card, no sales call. [Import a collection](https://app.getelva.ai/signup) [See plans](https://getelva.ai/pricing.md) Postman plan details are from Postman’s public documentation as of March 2026. Postman is a trademark of Postman, Inc. Elva is not affiliated with Postman.