Claude Swagger connectorWhat Claude can do in your Swagger account.
The Claude Swagger connector exposes 22 tools, 10 in read and 12 in write. Claude searches your API registry, scans definitions against your organisation's rules, generates or fixes APIs, and creates, edits, publishes or deletes portal products and pages.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can work in Swagger
Swagger's directory caption sums it up: design, govern and document APIs. With the connector, you describe the job to Claude: it finds the API, runs the standardisation scan, proposes or applies fixes, and updates the documentation pages of your portal, all under your SmartBear login and roles.
Checking an API against house rules. Claude locates it with search_apis_and_domains, pulls the resolved definition through get_api_definition, and scan_api_standardization lists the violations by severity.
Fixing or drafting APIs. standardize_api corrects a non-compliant definition with SmartBear AI, ideally into a new version, and create_api_from_prompt generates a new API from a description with governance rules applied.
Running a developer portal. Claude can add a product with create_portal_product, edit a page through update_document, then preview or go live with publish_portal_product.
What it will not do: it only sees portals where you hold at least a designer role, and no source describes a confirmation of its own before the twelve writing tools. Nothing runs on a schedule either: Claude acts only while it answers you. The Claude connectors hub lists other developer connectors, and the Integrations page covers automation platforms.
Five words before you connect
The Claude vocabulary behind this connector, in one minute.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named thing the connector lets Claude do on that account. Claude picks the ones it needs, and the directory sheet lists them by name.
- Authorization
- The SmartBear sign-in screen where you give Claude the access it will use from then on. Granted once per person, and it can be revoked.
- Approval
- The confirmation Claude waits for before it goes ahead with something that changes an account, shown in the chat when it matters.
- MCP
- The shared standard behind connectors: it is what lets an assistant such as Claude talk to an outside service like Swagger.
Connecting Swagger to Claude in three steps
- 01
Find Swagger in Claude
Open Claude's settings, go to Customize then Connectors, and search for Swagger. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector first so members can then sign in one by one.
- 02
Start the connection
Click Connect on its row. SmartBear says a browser window opens for a SmartBear OAuth login, with no API token or environment variable to set. If the connection breaks later, use Disconnect and connect again.
- 03
Read the authorization screen
Look at the authorization screen before you accept. It belongs to SmartBear, not to Claude, and it decides what the access covers. You can also remove that access later from your SmartBear account.
The 22 Swagger tools, sorted by what they do
Swagger gives Claude 22 tools: 10 that read your account, 12 that change something in it.
SmartBear's own server code describes every one of them, with a read-only or modifying flag. Names stay as Claude shows them.
- 10 read
- 12 write
What Claude reads (10)
10 toolsTen tools that search, open and scan APIs and portal content without altering them.
list_portals
Searches the developer portals available to you in Swagger, returning only those where you hold at least a designer role, at product or organisation level.
get_portal
Retrieves the details of one portal, identified by its UUID or subdomain, so Claude knows how it is configured before touching anything inside.
list_portal_products
Returns the products of one portal that match your criteria, each of them grouping API documentation for visitors, and lists them so Claude can work through them one at a time.
get_portal_product
Opens one product, found by its UUID or by the portal subdomain and product slug, and returns its settings and metadata.
list_portal_product_sections
Lists the sections inside a portal product, page by page, optionally with their tables of contents embedded, so Claude can map how the docs are organised.
list_table_of_contents
Returns the table of contents of one section, page by page, and can embed the linked SwaggerHub API so Claude sees which reference sits where.
get_document
Fetches the content and metadata of a document by its ID, typically the HTML or Markdown behind a table of contents entry.
search_apis_and_domains
Searches the SwaggerHub registry for APIs and domains by text, owner, tag, publication state or type, and returns their name, owner, version and summary.
get_api_definition
Fetches the resolved definition of one API version from the registry, as JSON by default or as the original YAML text on request.
scan_api_standardization
Checks a raw YAML or JSON definition against your organisation's governance and standardisation rules, and returns the issues found, grouped by severity, with a total count.
What Claude can create, change or delete (12)
12 toolsTwelve tools that build portals, products and pages, publish them, or generate and fix APIs. No source describes a confirmation of their own: the general rule below applies.
create_portal
Approval: see the ruleSets up a new Swagger portal linked to your organisation, with a subdomain, a display name, a renderer choice and whether it starts offline or requires credentials.
update_portal
Approval: see the ruleEdits a portal's configuration: display name, subdomain and therefore URL, custom domain, analytics key, visibility, routing, credentials and renderer.
create_portal_product
Approval: see the ruleAdds a product to a portal, either from scratch or as a copy of an existing one, with name, slug, description, and public or hidden settings.
update_portal_product
Approval: see the ruleChanges a product's name, slug, description, public visibility or presence in the portal navigation menus.
delete_portal_product
Approval: see the ruleRemoves a product from a portal, which SmartBear's own code marks as a destructive operation.
publish_portal_product
Approval: see the rulePublishes a product's current content, either as a preview for testing or live for portal visitors, and returns the resulting URL and publication status.
create_table_of_contents
Approval: see the ruleAdds an entry to the table of contents of a product section, pointing to an API reference, an HTML page or a Markdown page.
delete_table_of_contents
Approval: see the ruleSoft-deletes an entry from a table of contents and can do so recursively for nested items below it.
update_document
Approval: see the ruleRewrites the content or the source setting of an existing portal document, in HTML or Markdown.
create_or_update_api
Approval: see the ruleCreates a new API in the SwaggerHub registry or overwrites an existing one from a definition you supply, detecting OpenAPI or AsyncAPI automatically.
create_api_from_prompt
Approval: see the ruleGenerates and saves a new API, or a new version of one, from a natural-language description using SmartBear AI, applying your organisation's governance rules along the way.
standardize_api
Approval: see the ruleScans an API in the registry for standardisation errors and fixes them automatically with SmartBear AI, returning the error count and the corrected definition.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before any action it takes on an account in your place. With twelve tools that write, several of which SmartBear flags as destructive, that default deserves to stay on.
On Team and Enterprise workspaces, owners decide whether a member may let some actions through without being asked again, and they can bound what a connector may do for the whole organisation, keeping reads and closing writes for instance. Nobody bypasses that from their own account. Claude also works with your Swagger rights only: SmartBear's own portal listing returns just the portals where you hold at least a designer role, so what your login cannot reach stays out of the conversation.
Which plans include it
None of the 819 sheets in the official directory displays availability by plan. Connector by connector, the answer is published nowhere: it is a real gap in the catalogue.
What is published is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organisation before each member signs in. For the current state of this one, check its sheet in the official directory. Note that only SmartBear documents it; no Claude help article covers it.
Where the Claude Swagger connector stops
A connector is not an automation. Claude calls these tools while it answers you: no scan runs when someone pushes a new API version.
The tool list is an observed floor, not a promise: an administrator can open actions that no public sheet shows. The partner badge in the directory is not a security audit, and Anthropic says on every sheet that it does not choose the tools a publisher exposes and cannot guarantee they behave as announced. Connect only what comes from a publisher you trust, here SmartBear, whose server code is the source describing these tools.
Need help connecting Swagger to Claude?
A person reads every message.
