smartbear.com
SmartBear exposes 3 remote MCP servers on `*.mcp.smartbear.com` authenticated by OAuth browser login (SmartBear ID for Swagger and BugSnag, Atlassian OAuth for Zephyr) plus the Zephyr Essential Cloud REST API at `https://prod-api.zephyr4jiracloud.com/v2` authenticated with a bearer API token generated from `Zephyr Essential API keys` in Jira, and a BugSnag Error Reporting API at `https://notify.bugsnag.smartbear.com` whose auth was not determined from the recorded evidence.
- Zephyr Essential Cloud APIdiscovered
- BugSnag Error Reporting APIdiscovered
Point your MCP client at the server URL and approve access in the browser. The server supports OAuth Dynamic Client Registration (RFC 7591), so the client registers itself automatically — no developer-portal app, client_id, or client_secret to create.
Point your MCP client at the server URL and approve access in the browser. The server supports OAuth Dynamic Client Registration (RFC 7591), so the client registers itself automatically — no developer-portal app, client_id, or client_secret to create.
In Jira, click your Atlassian profile picture and choose Zephyr Essential API keys, then generate an access token as described in the Zephyr Essential authentication guide. Use it as a bearer token.
conventions · 1/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✓https://smartbear.com/llms.txt
- API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing