consigliere-connect-atlassian

You connect Claude Code to Jira and Confluence read-only by configuring a secure per-user OAuth 2.1 connection to Atlassian MCP. This one-time setup registers MCP endpoints and updates Claude settings to enforce read-only permissions for Atlassian Cloud.

Yes, Atlassian MCP supports per-user OAuth 2.1 scopes for Claude Code. The setup configures specific read scopes per user, ensuring Claude Code only retrieves data without exposing credentials or allowing workspace changes.

The best way to enforce read-only permissions for Atlassian is by updating the .claude/settings.json file with guardrails. This configuration restricts MCP endpoints to read operations, preventing any accidental writes to Jira or Confluence.

You verify a read operation against Jira by validating access through the /mcp command after the initial setup. Running a test read operation confirms the OAuth 2.1 connection and read scopes are correctly configured for Atlassian Cloud.

Yes, you can deploy read access across Jira and Confluence without writes using this setup. It registers MCP endpoints with enforced read-only guardrails, acting as a digest-source while Atlassian logs audit the access.

Claude Code needs a one-time setup for Atlassian MCP endpoint registration to establish the secure OAuth 2.1 connection and configure per-user read scopes. This process ensures only authorized read operations occur against Jira and Confluence.