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.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect SmartBear Swagger to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect SmartBear Swagger once
-
Open Connections, choose Add connection, and pick SmartBear Swagger.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in SmartBear Swagger. SmartBear Swagger's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
SmartBear Swagger MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect SmartBear Swagger to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with SmartBear Swagger through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Platform engineering
Find the API before building another
Ask whether an API for a given capability already exists in Swagger Studio and get the matching definitions back, so nobody drafts a duplicate.
-
API product
Draft a new API definition from a brief
Turn a short description of a service into a first API definition in SmartBear Swagger, ready for the team to review and refine.
-
Architecture
Check a definition against the house standards
Run standardization checks on an API definition and get a plain list of what fails and why, before it reaches a review meeting.
-
Developer experience
Keep shared domains current
Update a shared domain in Swagger Studio when a common model changes, so every API that reuses it picks up the fix.
-
QA
Catch standards failures before review
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.
-
Partner engineering
Answer what an API actually exposes
When a partner asks what a public API offers, search Swagger Studio for the definition and summarize its endpoints and fields in an answer.
Try asking
- “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”
Compare
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
See it in Elaichi
What connecting SmartBear Swagger gets you
5 screens from the product, each doing one job for your SmartBear Swagger account.
The agent
Ask about your APIs in plain language.
Search Swagger Studio, draft definitions and run standardization checks without opening a tab.
- apis
- domains
- definitions
- checks
Ask Elaichi to work across your apps.
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
Also runs in Claude, ChatGPT or Cursor
MCP clients
SmartBear Swagger works from every MCP client.
Claude, ChatGPT and Cursor share one governed endpoint, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Toolboxes
Each team gets its own SmartBear Swagger toolbox.
Platform, architecture and QA each see the SmartBear Swagger tools their work needs.
- Platform engineering
- API product
- Architecture
- Developer experience
ElaichiToolboxesShared connections
Share one SmartBear Swagger connection, keep the credential.
Teammates search and update API definitions through your connection without ever seeing a credential.
- Platform
- Architecture
- API product
- QA
ElaichiConnectionsAudit log
Every SmartBear Swagger call is on the record.
Who changed which API definition, when, and from which client, in one append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
Schedules run SmartBear Swagger checks end to end.
New API definitions are fetched, grouped and summarized, approved by a person, then posted back.
SmartBear Swagger digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch apis
SmartBear Swagger
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
SmartBear Swagger
Queued
Collections and dashboards
API health numbers arrive without anyone asking.
Definitions created, checks run and failures by team, refreshed on a schedule with no model involved.
SmartBear Swagger health
Refreshed 4 minutes ago · every 15 minutes · from the apis collection
Apis
1,284 ↓ 12%
Domains
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Apis created
Last 14 days
By team
Share of activity
Platform 34%
Architecture 27%
API product 21%
QA 18%
FAQ
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 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.
Put SmartBear Swagger in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.