OAuth servers
Some MCP templates in the catalog authenticate with OAuth2 instead of a key or token. These are platform-managed: qRaptor holds the OAuth client, so you don’t paste any credentials — you just authorize access by signing in with the provider. OAuth is only available through the template catalog, not manual setup.
The built-in OAuth template is Atlassian Jira (Jira Cloud). The steps below use it as the example.
The OAuth flow
Because the OAuth client is managed by the platform, connecting is a single redirect — there’s no Instance URL or Credentials step to fill in.
Steps
Choose the OAuth template
In the Add MCP server wizard, pick the OAuth template (Atlassian Jira) from the catalog. You’re taken straight to the Connect step.
Connect
The Connect step reads “Connect with Atlassian Jira” and explains you’ll be redirected to authorize access, then returned here. Click Connect with Atlassian Jira.
You’re taken to the provider to:
- Sign in to your account.
- Select the site to grant access to (for Jira, the Atlassian site).
- Approve the requested permissions.
On return, qRaptor shows Connecting… then Connected! and continues to tool discovery — from there, review and enable tools exactly as with any server.
Platform-managed templates need no credential setup. A self-hosted or custom OAuth provider may additionally ask for an instance URL or client credentials before the Connect step, but the built-in catalog templates don’t.
OAuth connection status
An OAuth server’s status reflects its token, shown on the server card and detail page:
| Status | Meaning |
|---|---|
| Connected | Token is valid. |
| Token Expired | The token expired; it may refresh automatically. |
| Reconnect Needed | Refresh failed — reconnect the server. |
| Revoked | Access was revoked at the provider. |
| Not Connected | No token yet. |
If a server needs attention, its detail page shows a Reconnect action. See Manage a server.
Disconnect
To remove an OAuth connection, open the server and click Disconnect. The dialog (“Disconnect {server}?”) warns: “This will revoke the OAuth token and remove the MCP server connection. All tools from this server will become unavailable. This cannot be undone.”
Disconnecting revokes the token and makes every tool from that server unavailable to agents. It can’t be undone — you’d reconnect from scratch.
Common issues
- “Failed to initiate OAuth flow” — the platform’s OAuth client for this provider isn’t configured. Contact your administrator.
- Returned to a “Connection Failed” screen — the authorization didn’t complete; use Go back and try again.
- Status shows Reconnect Needed — the token couldn’t refresh; open the server and Reconnect.