Base44
Build and edit Base44 apps from an AI assistant, and query data your app's users submit.
Publish APIs and developer portals from an AI agent.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Swagger MCP server connects SmartBear's API platform — the SwaggerHub registry and Swagger Portal — to Claude, ChatGPT and any MCP-compatible agent. It searches API definitions, generates and standardises specifications with AI, and builds and publishes developer documentation portals. Sign-in is OAuth against SmartBear's identity service.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
openid, profile, email and offline_access. No boundary falls between reading an API definition and publishing a portal or deleting a product — the consent screen cannot express the difference. The server's RFC 9728 descriptor names the authorization server and declares no scopes_supported at all.patch_api and the entire outbound-request path.swagger_ plus the lower-cased title. The directory and SmartBear's own Swagger documentation both use the unprefixed form, which is what this page uses.preview defaults to false.standardize_api and patch_api both overwrite the current version unless a new version is supplied.create_test plus run_test is a general-purpose HTTP client with attacker-controllable URL, method, headers and body..data suffix, which is where the tool tables on this page come from.Yes, and that is its default behaviour. The publish_portal_product tool takes a preview boolean that SmartBear's source defaults to false, meaning live publication. A single call makes a product's current draft content visible to portal visitors. Preview mode exists but the agent has to ask for it, so an unqualified instruction publishes.
Yes, through the Functional Testing tools. SmartBear documents that create_test accepts request steps with URL, HTTP method, headers and body, and run_test executes them. There is no allowlist tying a test to your own APIs. This makes the verb census misleading, because two tools reach any host the runner can route to.
Thirty-eight, not the 22 Anthropic's directory lists. SmartBear's open-source repository defines 27 Swagger tools plus 11 Functional Testing tools at release v0.37.0. The directory's 22 names all appear in that set, so nothing is fabricated, but five Swagger tools and all 11 testing tools are missing from the listing.
Four scopes, none of which narrow anything. SmartBear's authorization server at auth.swaggerhub.com advertised openid, profile, email and offline_access on 2026-08-22. All four are OpenID identity claims. Nothing at the OAuth grant separates reading an API definition from publishing a portal or deleting a product.
Yes, two tools delete. delete_portal_product removes a product from a portal, and delete_table_of_contents removes a navigation entry. SmartBear documents that the second is a soft delete that also removes the associated document content, and that it supports recursive deletion of nested items via a recursive flag.
Yes, unless you pass a new version. SmartBear documents that standardize_api sends findings to SmartBear AI, saves the corrected definition back to the registry, and that omitting the newVersion argument overwrites the current version. The docs recommend supplying a patch bump instead. The same overwrite applies to patch_api.
Whatever network the tunnel is deployed into. SmartBear's schemas accept a tunnelAgentName on both suite creation and suite runs, overriding each test's saved tunnel. A tunnel agent exists to reach APIs that are not publicly routable, so a test run through one reaches internal hosts your agent could not otherwise call.
Because its cached OAuth dynamic client registration expired. SmartBear's troubleshooting page names the error as unknown or expired client_id and gives the fix: open the Command Palette, run Authentication Remove Dynamic Authentication Providers, remove the stale provider, then restart VS Code and sign in again. SmartBear links VS Code issue 250960.
d0e2df7 (retrieved 2026-08-22). Tool definitions and safety annotations read from src/swagger/client/tools.ts, src/swagger/client/tool-constants.ts, src/swagger/client/portal-types.ts, src/swagger/client/registry-types.ts and src/swagger/client/functional-testing-types.ts. · retrieved 2026-08-22www-authenticate OAuth challenge naming the resource metadata document (2026-08-22) · retrieved 2026-08-22Connect Swagger once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.