How I Gave Claude Code Access to My Entire Company's Knowledge Base (In 30 Minutes)

In a large company, getting one answer can cost you half a day.

You don't just find the information. You find the person who has it. Then you wait for them to reply. Hope they're not in a meeting. Maybe follow up. Eventually get a Slack message with a Confluence link to a page that hasn't been updated since 2023.

I was doing this every week. Same friction, different questions.

Then I discovered MCP servers — and wired Claude Code directly into our company's knowledge stack. Here's exactly how I did it.

The Problem: Information is Always 3 People Away

I needed to understand how our platform was configured. So I opened Confluence — our internal knowledge base. Hundreds of pages. No obvious entry point.

So I went through the usual steps:

Search Confluence, find 12 loosely related pages
Figure out who owns the relevant docs
Ping them on Slack
Wait
Get a partial answer, repeat from step 2

This wasn't a one-time thing. It was a recurring tax on my working day.

The underlying problem: all this institutional knowledge exists — it's just scattered across tools that weren't designed to answer questions. They were designed to store information.

The Discovery: MCP Servers Can Bridge the Gap

MCP (Model Context Protocol) is an open standard that lets AI assistants connect to external tools and data sources. I knew it existed. I hadn't thought to apply it to our internal company tools.

Turns out, there are ready-made MCP servers for Confluence, Jira, and GitHub. Once connected, Claude can query them directly — not web search results, your actual internal data.

The idea clicked: if Claude can read Confluence, it can answer the questions I've been pinging people about for months.

🛠 Step 1: Confluence MCP — Your Internal Knowledge Base

The package is mcp-atlassian, installed via uvx (no manual install needed):

"confluence": {
  "command": "uvx",
  "args": ["mcp-atlassian"],
  "env": {
    "CONFLUENCE_URL": "https://yourcompany.atlassian.net/wiki",
    "CONFLUENCE_USERNAME": "you@yourcompany.com",
    "CONFLUENCE_API_TOKEN": "your-api-token"
  }
}

Get your API token from Atlassian account settings → Security → API tokens.

After this, Claude can search and read your Confluence spaces directly. Not summaries. Your actual internal docs, with exact page references.

I asked Claude the same question I'd been pinging people about for months. It answered in seconds. With the exact page reference.

📌 Pro Tip: uvx runs the tool in an isolated environment — nothing to install globally, no version conflicts.

🔧 Step 2: Jira MCP — Tickets, Blockers, Sprint Status

The package mcp-server-jira-cloud gives Claude full access to your Jira projects:

"jira": {
  "command": "npx",
  "args": ["-y", "mcp-server-jira-cloud"],
  "env": {
    "JIRA_BASE_URL": "https://yourcompany.atlassian.net",
    "JIRA_API_TOKEN": "your-api-token",
    "JIRA_EMAIL": "you@yourcompany.com"
  }
}

Note the env var names: JIRA_BASE_URL and JIRA_EMAIL — different from the Confluence config. Use the same Atlassian API token.

Now instead of opening Jira, switching tabs, filtering by sprint, and cross-referencing three tickets — you just ask:

"What's blocking PROJ-412, and are there related tickets in the current sprint?"

Claude reads the ticket, follows the issue links, checks the sprint board, and gives you a coherent answer. No browser required.

📊 Step 3: GitHub MCP — PR History, Code Context, Review Threads

GitHub ships an official remote MCP server — no local install, just a bearer token:

"github": {
  "type": "http",
  "url": "https://api.githubcopilot.com/mcp",
  "headers": {
    "Authorization": "Bearer your-github-token"
  }
}

This is particularly useful for understanding why code is the way it is — architectural decisions buried in PR review threads become instantly accessible.

"Why was the retry logic changed in the auth service last quarter?"

Claude searches PR history and surfaces the relevant discussion. What used to require git log, git blame, and a browser becomes one question.

🌐 Bonus: Tavily MCP — Web Search When You Need It

For questions that aren't in your internal docs, Tavily gives Claude access to real-time web search:

"tavily-remote-mcp": {
  "command": "npx",
  "args": [
    "-y",
    "mcp-remote",
    "https://mcp.tavily.com/mcp/?tavilyApiKey=your-tavily-key"
  ],
  "env": {}
}

The API key is passed directly in the URL. No extra env vars needed.

The Full Config (Copy-Paste Ready)

Drop this into your Claude Code MCP settings:

{
  "mcpServers": {
    "confluence": {
      "command": "uvx",
      "args": ["mcp-atlassian"],
      "env": {
        "CONFLUENCE_URL": "https://yourcompany.atlassian.net/wiki",
        "CONFLUENCE_USERNAME": "you@yourcompany.com",
        "CONFLUENCE_API_TOKEN": "YOUR_ATLASSIAN_TOKEN"
      }
    },
    "jira": {
      "command": "npx",
      "args": ["-y", "mcp-server-jira-cloud"],
      "env": {
        "JIRA_BASE_URL": "https://yourcompany.atlassian.net",
        "JIRA_API_TOKEN": "YOUR_ATLASSIAN_TOKEN",
        "JIRA_EMAIL": "you@yourcompany.com"
      }
    },
    "github": {
      "type": "http",
      "url": "https://api.githubcopilot.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_GITHUB_TOKEN"
      }
    },
    "tavily-remote-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.tavily.com/mcp/?tavilyApiKey=YOUR_TAVILY_KEY"
      ],
      "env": {}
    }
  }
}

Total setup time: ~30 minutes. One API token per service, one config block each.

graph LR
    A[Claude Code] --> B[Confluence MCP\nuvx mcp-atlassian]
    A --> C[Jira MCP\nmcp-server-jira-cloud]
    A --> D[GitHub MCP\napi.githubcopilot.com]
    A --> E[Tavily MCP\nWeb Search]
    B --> F[Internal Docs]
    C --> G[Tickets & Sprints]
    D --> H[PR History & Code]
    E --> I[Real-Time Web]

The Result: Claude Knows Your Company

After this setup, the experience shifts noticeably.

Before:
Open Confluence → search → find wrong page → find right person → wait

After:
Ask Claude → get answer with exact page reference → keep working

The key distinction: this isn't generic AI knowledge. Claude now has access to your company's architecture docs, your team's tickets, your repo's history.

✅ Questions that used to require a coworker now answer in seconds
✅ Onboarding becomes faster — Claude becomes a guided tour of your stack
✅ Incident investigation is faster — no more context-switching between tools
✅ Setup cost: one afternoon, one token per tool

Which Tool Should You Connect First?

If I had to pick one: Confluence. That's where institutional knowledge lives, and it's where the "3 people away" problem hits hardest.

Jira is a close second if your team is ticket-driven. GitHub MCP earns its place quickly once you're using Claude for debugging or code review — having PR history in context changes how you approach both.