SmartBear MCP Server
OFFICIAL SERVEROne MCP server for SmartBear's BugSnag, Swagger, PactFlow, Zephyr, QMetry, Reflect and other QA tools
SmartBear's hosted endpoint for managing Swagger Studio APIs and Swagger Portal content
Official · smartbear.com Remote (hosted) · Streamable HTTP Developer tools
Opens the app, which asks before it adds the server.
{
"servers": {
"smartbear-swagger": {
"type": "http",
"url": "https://swagger.mcp.smartbear.com/mcp"
}
}
}{
"mcpServers": {
"swagger-remote": {
"url": "https://swagger.mcp.smartbear.com/mcp"
}
}
}https://swagger.mcp.smartbear.com/mcpclaude mcp add --transport http smartbear-swagger https://swagger.mcp.smartbear.com/mcp{
"mcpServers": {
"swagger": {
"type": "http",
"url": "https://swagger.mcp.smartbear.com/mcp",
"oauth": {
"oauthScopes": []
},
"disabled": false,
"autoApprove": []
}
}
}This is the hosted version of the Swagger part of SmartBear's MCP server. Instead of running the @smartbear/mcp npm package with a Swagger API key, you point an MCP client at https://swagger.mcp.smartbear.com/mcp over streamable HTTP and sign in through a browser with your SmartBear account.
It covers two Swagger products. On the Studio side (the SwaggerHub Registry) it can search APIs and domains, fetch a definition as JSON or as its YAML source, validate and scan definitions against your organization's governance rules, create or update APIs, apply small search-and-replace patches, and generate or fix definitions with SmartBear AI. On the Portal side it lists, creates and updates portals and their products, manages sections, tables of contents and documentation pages, and publishes a product live or as a preview.
The endpoint's OAuth protected-resource metadata names https://auth.swaggerhub.com as its authorization server, so the sign-in is the SwaggerHub one rather than a generic SmartBear page. SmartBear's remote-server guide also shows that Swagger Functional Testing tools, which the local package offers with their own token, are not part of this hosted server.
A SmartBear (SwaggerHub) account with access to Swagger Studio and, for the portal tools, Swagger Portal. An MCP client that can connect to a remote HTTP server and complete an OAuth browser sign-in. Nothing is installed locally and no Node.js or API key is needed.
Only Swagger Portal and Swagger Studio tools are served; Swagger Functional Testing, Reflect, QMetry, PactFlow and Collaborator are only in the local @smartbear/mcp package. list_portals returns only portals where you are an owner or designer. create_api_from_prompt fails if the API version already exists. patch_api accepts only OpenAPI and AsyncAPI definitions and saves nothing unless every edit applies. The docs describe on-premise base paths only for the local package; the hosted endpoint targets SmartBear's cloud.
Suits API teams on SwaggerHub's cloud who want an assistant to read, validate, standardize and edit API definitions, or to maintain portal documentation, without handling an API key. Since most tools can create, change, publish or delete, it suits people who already have designer or owner rights and review what is sent. Pick the local smartbear-mcp package instead for an on-premise SwaggerHub, for Functional Testing tools, or to combine Swagger with other SmartBear products in one connection; SmartBear also hosts separate BugSnag and Zephyr endpoints.
search_apis_and_domainsget_api_definitioncreate_or_update_apiscan_api_standardizationscan_api_standardization_from_registryvalidate_apicreate_api_from_promptstandardize_apipatch_apilist_organizationslist_portalsget_portalcreate_portalupdate_portalresolve_organization_portallist_portal_productsget_portal_productcreate_portal_productupdate_portal_productdelete_portal_productpublish_portal_productlist_portal_product_sectionscreate_table_of_contentslist_table_of_contentsdelete_table_of_contentscreate_documentation_pageget_documentupdate_document