# SmartBear Swagger MCP connector The SmartBear Swagger connector lets Claude, ChatGPT, Cursor and the Elaichi Agent search your APIs and domains in Swagger Studio, create or update API definitions, and run standardization checks, with each person signed in as themselves. Source: https://elaichi.ai/connectors/smartbear-swagger/ ## Facts | | | | --- | --- | | Application | SmartBear Swagger | | Category | Application Development | | Authentication | Connects over OAuth | | Bring your own OAuth app | No | | Native MCP | Yes. SmartBear Swagger builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top | | Support for its tools | support.smartbear.com/swagger | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead | ## What you can ask once SmartBear Swagger is connected - Find every API in Swagger Studio that mentions payments - Draft an API definition for the orders service from this brief - Run standardization checks on the customer API and list what fails ## Connect SmartBear Swagger in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick SmartBear Swagger. 2. Optionally set Share with, then press Connect. 3. Approve it in SmartBear Swagger. SmartBear Swagger's own window opens. Whoever approves it decides what this connection can reach. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which SmartBear Swagger tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## SmartBear Swagger MCP connector for Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## SmartBear Swagger MCP connector for ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## SmartBear Swagger MCP connector for Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect SmartBear Swagger to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a SmartBear Swagger tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with SmartBear Swagger through Elaichi ### Find the API before building another Platform engineering. Ask whether an API for a given capability already exists in Swagger Studio and get the matching definitions back, so nobody drafts a duplicate. ### Draft a new API definition from a brief API product. Turn a short description of a service into a first API definition in SmartBear Swagger, ready for the team to review and refine. ### Check a definition against the house standards Architecture. Run standardization checks on an API definition and get a plain list of what fails and why, before it reaches a review meeting. ### Keep shared domains current Developer experience. Update a shared domain in Swagger Studio when a common model changes, so every API that reuses it picks up the fix. ### Catch standards failures before review QA. Ask for the open standardization failures on an API and work through them one by one, then rerun the check to confirm they are gone. ### Answer what an API actually exposes Partner engineering. When a partner asks what a public API offers, search Swagger Studio for the definition and summarize its endpoints and fields in an answer. ## Elaichi vs Zapier MCP vs Composio for SmartBear Swagger All three can connect SmartBear Swagger to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay. | What to check | Elaichi | Zapier MCP | Composio | | --- | --- | --- | --- | | Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. | | Control over SmartBear Swagger tools | Allow or restrict single SmartBear Swagger tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. | | Record of calls | One audit entry per SmartBear Swagger call. | A History tab of tool calls. | A log of every tool call. | | Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. | | Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. | Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026. Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/). ## Frequently asked questions ### How do I connect SmartBear Swagger to Claude? Open Elaichi, choose SmartBear Swagger, and sign in with your SmartBear account when the OAuth screen appears. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi, and from then on it can work with your APIs in Swagger Studio. ### Does SmartBear Swagger work with ChatGPT and Cursor as well as Claude? Yes. The SmartBear Swagger connector is reached through the same endpoint, https://api.elaichi.ai/mcp, from Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. You connect SmartBear Swagger once in Elaichi and every client you use picks it up. ### What can an AI agent actually do with my SmartBear Swagger data? An agent can search the APIs and domains in your Swagger Studio, create a new API definition or update an existing one, and run standardization checks and tell you what fails. Short, concrete asks work best, such as asking for the definition of one named API or a check on one definition rather than a long paragraph of instructions. ### Does connecting SmartBear Swagger give the AI every API in my organization? No. The agent works inside the access of the person who signed in to SmartBear Swagger, so it only sees the APIs and domains that person can already open in Swagger Studio. Elaichi can narrow that further with roles and restrictions, and it can never widen what SmartBear Swagger itself allows. ### Can my team share one SmartBear Swagger connection? Yes. One person connects SmartBear Swagger in Elaichi and shares it with a team, and nobody else ever handles a credential. Each teammate still signs in to Elaichi as themselves, so every search, definition update and check in the audit log carries that person's name. ### Can I stop an agent from changing API definitions in SmartBear Swagger? Yes. Restrictions in Elaichi apply per action, so you can allow searching Swagger Studio and running standardization checks while blocking the creation or update of API definitions. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it. ### What happens to a SmartBear Swagger connection when someone leaves? Offboarding that person in Elaichi ends their access to SmartBear Swagger through every client at once. A shared SmartBear Swagger connection keeps working for everyone else on the team. If you want the connector gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client. ### Does the SmartBear Swagger MCP connector work with Gemini, Codex, Claude Code or other MCP clients? Yes. SmartBear Swagger is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs. ### Is Elaichi an alternative to Zapier MCP for SmartBear Swagger? Yes. Both let Claude, ChatGPT or Cursor use SmartBear Swagger. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every SmartBear Swagger call. ### How is Elaichi different from Composio for SmartBear Swagger? Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to SmartBear Swagger: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.