SYS ONLINESTATUSOPEN FOR WORK
LunaByte
Back to Blog

How I Connected Claude Code to Linear & Atlassian (And Why You Should Too)

6 min read
Claude CodeLinearAtlassianMCPProductivityDevelopment Tools

Update: Claude Code now natively supports OAuth authentication for remote MCP servers! Check out Anthropic's announcement for the latest simplified setup process. The workarounds described below are no longer necessary, but I'm keeping this article up for historical context.

I hit a wall trying to switch contexts between my terminal and project management tools every 15 minutes. After the fifth time logging into Jira to update a ticket status, I decided enough was enough. There had to be a better way to connect Claude Code to team management tools. Spoiler alert: there is! But it wasn't as straightforward as I hoped, and after some late-night troubleshooting, I figured out how to connect Claude Code to Linear and Atlassian's MCP servers. The result? A complete game-changer.

What You'll Need

If you're already using Claude Code, you'll just need:

  • Node.js v18+ (I'm using v22)
  • npm
  • Your Linear and/or Atlassian login credentials
  • About 10 minutes of setup time

Understanding MCP Authentication

Here's what took me forever to figure out: Claude Code works great with local tools but gets confused when trying to authenticate with remote MCP servers like Linear and Atlassian. These servers use OAuth (you know, the "Login with X" flows we're all used to), but Claude Code doesn't natively handle this. The solution is a little adapter called mcp-remote that basically plays translator between Claude Code and these remote servers. Once I discovered this, everything clicked into place rather effortlessly.

Setting It Up (I Promise It's Not That Bad)

Step 1: Install the adapter

First, let's install the adapter globally:

npm install -g mcp-remote

Step 2: Clean slate

If you've attempted this setup before, clear out any failed authentication attempts:

rm -rf ~/.mcp-auth

Step 3: Configure Claude Code

Now we need to tell Claude Code how to connect. Edit your config file (on my Mac it's at ~/.claude/claude_code_config.json):

{
  "mcpServers": {
    "linear": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.linear.app/sse"]
    },
    "atlassian": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.atlassian.com/v1/sse"]
    }
  }
}

Step 4: Restart & authenticate

Quit Claude Code completely, then relaunch it:

claude --mcp-debug

The first time you run it, you'll see a browser window pop open asking you to log in to Linear or Atlassian. Go ahead and authorize the connection. This is a one-time thing, so don't worry about having to do this every day.

Does It Actually Work?

Absolutely! I've been using this setup for a while now, and it's been surprisingly smooth. But the real magic isn't in simple issue updates - it's in what Claude can do when it has access to your entire project context.

The Game-Changing Workflows

Intelligent Code-to-Issue Sync:

"

"Look at my last 5 commits on this feature branch. Find all related Linear issues, update their status based on the code changes, add comments summarizing what was implemented, and flag any issues that might be affected by these changes but aren't linked in the commits"

This saves me 20-30 minutes of context switching after every coding session. Claude analyzes the actual code changes, understands the impact, and updates everything accordingly.

Cross-Project Pattern Detection:

"

"Search all Confluence pages and Linear issues for similar authentication timeout problems we've faced before. Summarize the root causes and solutions, then create a new Linear issue with a proposed fix based on what worked previously"

Instead of reinventing the wheel, Claude becomes your institutional memory - finding patterns across hundreds of issues and docs that no human would have time to review.

Automated Documentation That Actually Stays Current:

"

"Compare the current API implementation in src/api with the Confluence documentation for the Payment Service. Update the docs with any endpoint changes, add any missing error codes, and create Linear issues for any breaking changes that need team discussion"

This is the dream - documentation that updates itself based on your actual code. No more outdated wiki pages that mislead new team members.

Sprint Intelligence and Planning:

"

"Analyze my team's completed Linear issues from the last 3 sprints. Identify which types of tasks consistently take longer than estimated, what blockers keep appearing, and suggest more accurate story point estimates for similar upcoming work"

Claude becomes your retrospective assistant, spotting trends humans miss and helping you plan more realistically.

Troubleshooting (Because Tech Is Never Perfect)

401 Errors Keep Popping Up

This usually means the authentication didn't complete properly. This can happen occasionally when using a VPN. Try:

rm -rf ~/.mcp-auth

And then restart Claude Code with:

claude --mcp-debug

Look for a URL in the console that you can copy/paste if the browser doesn't open automatically.

Authentication Starts But Never Finishes

This drove me nuts until I realized it was a port issue. Try adding a custom port:

"args": ["-y", "mcp-remote", "https://mcp.linear.app/sse", "--port", "8888"]

Why This Matters

The biggest win hasn't been the time saved (though that's significant): it's the mental bandwidth. I used to completely lose my train of thought switching between coding and updating Linear issues. Now I can just tell Claude to "update the status of PROJ-134 to In Review and add a comment that the API refactoring is complete but needs tests." Done. Back to code.

Looking Forward

This setup isn't perfect - it's clearly a bridge solution until Claude Code natively supports OAuth flows for remote MCP servers. But for now, it works surprisingly well.

What excites me most is that we're just scratching the surface. With Claude having context about your code, tickets, and documentation all at once, it can spot connections and suggest improvements that would take hours to discover manually. It's like having a (sometimes) senior engineer who's read every ticket, every doc, and every line of code in your organization.

The real value isn't in automating individual tasks - it's in having an AI that understands your entire development workflow and can help you work smarter, not just faster.

Have you connected Claude Code to other tools? I'd love to hear what workflows you've automated! Reach out on socials or shoot me an email!

Back to all posts