fix: restore Atlassian MCP OAuth by removing stale Passport dependency

[ct3685]

Summary

Commit 1 — fix: Atlassian MCP OAuth 500 error

• Root cause: Commit 0ae736e41 intentionally disabled Passport.js session infrastructure when the AAI JWT/API-key auth system was integrated. The atlassian-dynamic Passport strategy was left in place but never ran because Passport was never initialized — causing a hard 500: Unknown authentication strategy "atlassian-dynamic" on every OAuth callback.
• Fix: Removed Passport from the Atlassian auth flow entirely. Token exchange logic now lives directly in the controller using the already-existing utility functions exchangeCodeForTokens, createCompleteCredentialData, clearPendingRegistration from utils/index.ts.
• Removed dead code: The GET /api/v1/atlassian-auth/ root route and authenticate controller method (both solely called passport.authenticate(...)) are gone.

Commit 2 — feat: pre-fetch cloudId context to prevent null cloudId errors (global fix for all Atlassian actions)

• Root cause: The Atlassian Remote MCP server requires a cloudId parameter for almost every Jira/Confluence tool call (add_comment_to_jira_issue, search_jira_issues, create_jira_issue, write:confluence-content, etc.). Without upfront knowledge of it, the LLM would pass null, receive a -32602 validation error, then self-correct by calling get_accessible_resources before retrying — one wasted round-trip on every first call.
• Fix is global across all Atlassian MCP actions: During getTools() initialization, the node invokes get_accessible_resources using its own MCPTool instance (no new MCP SDK imports), parses the cloud resource list, then iterates every tool returned by the MCP server and appends a cloudId hint to the description of any tool that declares a cloudId parameter in its zod schema. This covers all current and future Atlassian MCP tools automatically — no per-action changes needed.
  • Single site: [cloudId for this Atlassian site: "8ca3c755..." (lastrev — https://lastrev.atlassian.net)]
  • Multi-site: [Available Atlassian cloudIds: "8ca3c755..." → lastrev, "f08c36cd..." → lastrev-new]
• Falls back silently if the pre-fetch fails, so no regression on errors.
• Node version bumped 1.0 → 1.1.

Files changed

File	Change
packages/server/src/controllers/atlassian-auth/index.ts	Removed Passport; inlined OAuth flow using existing utilities; removed dead authenticate method
packages/server/src/routes/atlassian-auth/index.ts	Removed Passport import and middleware; removed dead root route
packages/server/src/config/passport.ts	Removed atlassian-dynamic CustomStrategy and its unused imports
packages/components/nodes/tools/MCP/Atlassian/AtlassianMcp.ts	Added fetchCloudResources + enrichToolsWithCloudContext; bumped version to 1.1

OAuth callback flow (unchanged behavior)

1. UI calls GET /api/v1/atlassian-auth/mcp-initialize → registers dynamic OAuth client, returns sessionId, client_id, authorization_endpoint, redirect_uri, scope
2. UI opens popup → user authenticates → Atlassian redirects to /api/v1/atlassian-auth/callback?code=...&state=<sessionId>
3. Controller exchanges code for tokens using stored client credentials → builds credential object → posts AUTH_SUCCESS to opener

Test plan

• Start local dev server (pnpm dev)
• Navigate to Credentials and create a new Atlassian MCP credential
• Click "Connect with Atlassian" — popup opens and completes without 500 error
• Save credential and add Atlassian MCP node to a chatflow
• Verify the node's "Available Actions" dropdown loads correctly (cloudId hints visible in descriptions)
• Run a Jira action (comment, search, create) — confirm it succeeds on the first attempt without a get_accessible_resources round-trip
• Run a Confluence action — confirm same first-attempt success
• Test with multiple Atlassian sites connected — confirm all cloudIds appear in the hint
• Verify token refresh still works (refreshStoredCredentialTokens path unchanged)
• Verify Salesforce and Google OAuth flows are unaffected

Target branch

staging

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
answerai-docs	Building	Preview	May 15, 2026 3:29pm
the-answerai	Building	Preview	May 15, 2026 3:29pm