atlas

codeownersnet/atlas

3.2

If you are the rightful owner of atlas and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to dayong@mcphub.com.

Go MCP Atlassian is a high-performance server implementation of the Model Context Protocol (MCP) designed for seamless integration with Atlassian products like Jira, Confluence, and Opsgenie.

Tools
3
Resources
0
Prompts
0

Go MCP Atlassian

A high-performance Go implementation of the Model Context Protocol (MCP) server for Atlassian products (Jira, Confluence, and Opsgenie). This server enables AI assistants like Claude to seamlessly interact with your Atlassian instances through secure, controlled access.

Go Version

Why Use This MCP?

Control Your AI's Access

This MCP server gives you granular control over what your AI assistant can access and modify in your Atlassian environment:

  • Lock down to specific projects - Restrict Jira access to only the projects you approve
  • Limit to specific spaces - Confine Confluence access to designated spaces
  • Enable only the tools you need - whitelist specific MCP tools for precise control
  • Disable entire services - Turn off Jira, Confluence, or Opsgenie independently

Save Context Token Budget

Instead of sending your entire workflow or documentation to the AI, let it retrieve the relevant information on-demand:

  • Query Jira for specific issues without copying/pasting
  • Search Confluence for documents and retrieve only what's needed
  • Access real-time data from your Atlassian instances

Built-in Guardrails

Security features to keep your data safe:

  • Read-only mode - Run in a mode that prohibits any write operations
  • Tool filtering - Only expose the tools you explicitly enable
  • Project/space filtering - AI can only access resources you've approved
  • Service-level controls - Disable entire Atlassian products selectively

Features

  • 65 Tools Total: 29 Jira tools + 11 Confluence tools + 25 Opsgenie tools
  • Multi-Platform Support: Cloud and Server/Data Center deployments
  • Multiple Auth Methods: API Token, Personal Access Token, Bearer Token (BYO OAuth)
  • Production Ready: Built-in retry logic, proxy support, SSL verification
  • Flexible Configuration: Environment variables, .env files, CLI flags
  • Security: Read-only mode, tool filtering, project/space filtering, credential masking
  • High Performance: Native Go implementation with efficient HTTP client

Supported Platforms

ProductDeploymentStatus
JiraCloud✅ Supported
JiraServer/Data Center (8.14+)✅ Supported
ConfluenceCloud✅ Supported
ConfluenceServer/Data Center (6.0+)✅ Supported
OpsgenieCloud✅ Supported

Quick Start

1. Installation

Option A: Homebrew (macOS/Linux)
brew tap codeownersnet/atlas
brew install atlas-mcp
Option B: Download Binary

Download the latest release for your platform from GitHub Releases.

Option C: Using Go Install
go install github.com/codeownersnet/atlas/cmd/atlas-mcp@latest
Option D: Build from Source
git clone https://github.com/codeownersnet/atlas
cd atlas
go build -o atlas-mcp ./cmd/atlas-mcp

2. Authentication

Option A: API Tokens (Cloud - Jira/Confluence)
  1. Go to https://id.atlassian.com/manage-profile/security/api-tokens
  2. Click "Create API token"
  3. Copy the token immediately
  4. Use in configuration below
Option B: API Key (Opsgenie)
  1. Go to Opsgenie → Settings → API Key Management
  2. Create a new API key
  3. Copy the key immediately
  4. Use in configuration below
Option C: Personal Access Token (Server/Data Center)
  1. Go to your profile → Personal Access Tokens
  2. Create a new token
  3. Copy the token immediately
  4. Use in configuration below
Option D: Bearer Token (BYO OAuth - Advanced)

If you manage OAuth tokens externally, you'll need your OAuth access token and cloud ID.

Note: You are responsible for token refresh and management.

3. Configuration

Create a .env file with your credentials from step 2:

# For Jira Cloud
JIRA_URL=https://your-domain.atlassian.net
JIRA_USERNAME=your.email@example.com
JIRA_API_TOKEN=your_jira_api_token

# For Confluence Cloud
CONFLUENCE_URL=https://your-domain.atlassian.net/wiki
CONFLUENCE_USERNAME=your.email@example.com
CONFLUENCE_API_TOKEN=your_confluence_api_token

# For Opsgenie
OPSGENIE_API_KEY=your_opsgenie_api_key
Server/Data Center Configuration 
# For Jira Server/Data Center
JIRA_URL=https://jira.your-company.com
JIRA_PERSONAL_TOKEN=your_personal_access_token
JIRA_SSL_VERIFY=true

# For Confluence Server/Data Center
CONFLUENCE_URL=https://confluence.your-company.com
CONFLUENCE_PERSONAL_TOKEN=your_personal_access_token
CONFLUENCE_SSL_VERIFY=true

# For Opsgenie (Cloud only)
OPSGENIE_API_KEY=your_opsgenie_api_key
Bearer Token (BYO OAuth) Configuration 
# Provide your own OAuth access token
ATLASSIAN_OAUTH_ACCESS_TOKEN=your_oauth_access_token
ATLASSIAN_OAUTH_CLOUD_ID=your_cloud_id

4. Run the Server

./atlas-mcp

5. IDE Integration

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "atlas": {
      "command": "/path/to/atlas-mcp",
      "args": [],
      "env": {
        "JIRA_URL": "https://your-domain.atlassian.net",
        "JIRA_USERNAME": "your.email@example.com",
        "JIRA_API_TOKEN": "your_api_token",
        "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
        "CONFLUENCE_USERNAME": "your.email@example.com",
        "CONFLUENCE_API_TOKEN": "your_api_token",
        "OPSGENIE_API_KEY": "your_opsgenie_api_key"
      }
    }
  }
}
VS Code

For VS Code integration, see the detailed setup guide and configuration samples:

  • Setup Guide:
  • Configuration Samples: directory
Cursor

Open Settings → MCP → Add new global MCP server and configure similarly.

Security & Guardrails

This MCP server provides multiple layers of security control to keep your Atlassian data safe:

Read-Only Mode

Disable all write operations to prevent accidental modifications:

READ_ONLY_MODE=true

When enabled, all write tools (create, update, delete, etc.) will be unavailable to the AI.

Tool Filtering

Restrict access to specific tools only:

ENABLED_TOOLS=jira_get_issue,jira_search,confluence_search,opsgenie_list_alerts

This is a comma-separated whitelist of tool names. Only the tools listed will be available.

Project & Space Filtering

Limit access to specific Jira projects or Confluence spaces:

# Only allow access to these Jira projects
JIRA_PROJECTS_FILTER=PROJ1,PROJ2

# Only allow access to these Confluence spaces
CONFLUENCE_SPACES_FILTER=SPACE1,SPACE2

Service-Level Controls

Disable entire services if you don't need them:

# Disable Opsgenie completely
OPSGENIE_ENABLED=false

# Disable Jira
JIRA_ENABLED=false

# Disable Confluence
CONFLUENCE_ENABLED=false

Guardrails Combinations

You can combine multiple guardrails for maximum security:

# Read-only access to specific Confluence space only
READ_ONLY_MODE=true
JIRA_ENABLED=false
OPSGENIE_ENABLED=false
CONFLUENCE_SPACES_FILTER=DOC

# Full access to one Jira project, no Opsgenie
JIRA_PROJECTS_FILTER=PROD
OPSGENIE_ENABLED=false

Available Tools

Jira Tools (29 total)

Read Operations (14 tools)
  • jira_get_issue - Get issue details with field filtering
  • jira_search - Search issues using JQL queries
  • jira_search_fields - Search for field names (including custom fields)
  • jira_get_all_projects - List all accessible projects
  • jira_get_project_issues - Get all issues in a specific project
  • jira_get_project_versions - Get fix versions for a project
  • jira_get_transitions - Get available status transitions for an issue
  • jira_get_worklog - Get worklog entries for time tracking
  • jira_get_agile_boards - Get agile boards (Scrum/Kanban)
  • jira_get_board_issues - Get issues on a specific board
  • jira_get_sprints_from_board - Get sprints from a board
  • jira_get_sprint_issues - Get issues in a sprint
  • jira_get_issue_link_types - Get available link types
  • jira_get_user_profile - Get user information

When to use Jira: Use Jira tools when you need to track work, manage projects, or query issue status.

Example scenarios:

  • "Show me all high-priority bugs assigned to me"
  • "What's the status of the PROJ-123 issue?"
  • "Create a summary of all issues in the current sprint"
Write Operations (15 tools)
  • jira_create_issue - Create new issues
  • jira_update_issue - Update existing issues
  • jira_delete_issue - Delete issues
  • jira_add_comment - Add comments to issues
  • jira_transition_issue - Change issue status
  • jira_add_worklog - Log time spent
  • jira_link_to_epic - Link issues to Epics
  • jira_create_issue_link - Link issues together
  • jira_create_remote_issue_link - Create external links
  • jira_remove_issue_link - Remove issue links
  • jira_create_sprint - Create new sprints
  • jira_update_sprint - Update sprint details
  • jira_create_version - Create fix versions
  • jira_batch_create_issues - Create multiple issues at once
  • jira_batch_create_versions - Create multiple versions at once

Confluence Tools (11 total)

Read Operations (6 tools)
  • confluence_search - Search content using CQL or plain text
  • confluence_get_page - Get page content by ID or title+space
  • confluence_get_page_children - Get child pages
  • confluence_get_comments - Get page comments
  • confluence_get_labels - Get page labels
  • confluence_search_user - Search for users

When to use Confluence: Use Confluence tools for documentation, knowledge base queries, and wiki content.

Example scenarios:

  • "Find our API documentation in Confluence"
  • "What are the child pages under our product requirements space?"
  • "Summarize the recent changes to our engineering guidelines"
Write Operations (5 tools)
  • confluence_create_page - Create new pages
  • confluence_update_page - Update existing pages
  • confluence_delete_page - Delete pages
  • confluence_add_label - Add labels to pages
  • confluence_add_comment - Add comments to pages

Opsgenie Tools (25 total)

Read Operations (13 tools)
  • opsgenie_get_alert - Get alert details
  • opsgenie_list_alerts - List alerts with filtering
  • opsgenie_count_alerts - Count alerts matching query
  • opsgenie_get_request_status - Get async request status
  • opsgenie_get_incident - Get incident details
  • opsgenie_list_incidents - List incidents with filtering
  • opsgenie_get_schedule - Get schedule details
  • opsgenie_list_schedules - List all schedules
  • opsgenie_get_schedule_timeline - Get schedule timeline
  • opsgenie_get_on_calls - Get current on-call information
  • opsgenie_get_team - Get team details
  • opsgenie_list_teams - List all teams
  • opsgenie_get_user - Get user information

When to use Opsgenie: Use Opsgenie tools for incident management, alert monitoring, and on-call information.

Example scenarios:

  • "Show me all critical alerts from the last hour"
  • "Who is currently on-call for the infrastructure team?"
  • "Get the list of incidents from this week"
Write Operations (12 tools)
  • opsgenie_create_alert - Create new alerts
  • opsgenie_close_alert - Close alerts
  • opsgenie_acknowledge_alert - Acknowledge alerts
  • opsgenie_snooze_alert - Snooze alerts
  • opsgenie_escalate_alert - Escalate alerts
  • opsgenie_assign_alert - Assign alerts to users/teams
  • opsgenie_add_note_to_alert - Add notes to alerts
  • opsgenie_add_tags_to_alert - Add tags to alerts
  • opsgenie_create_incident - Create new incidents
  • opsgenie_close_incident - Close incidents
  • opsgenie_add_note_to_incident - Add notes to incidents
  • opsgenie_add_responder_to_incident - Add responders to incidents

Configuration Options

Security & Access Control

# Run in read-only mode (disables all write operations)
READ_ONLY_MODE=true

# Only enable specific tools (comma-separated)
ENABLED_TOOLS=jira_get_issue,jira_search,confluence_search,opsgenie_list_alerts

# Filter to specific projects/spaces
JIRA_PROJECTS_FILTER=PROJ1,PROJ2
CONFLUENCE_SPACES_FILTER=SPACE1,SPACE2

# Disable specific services
OPSGENIE_ENABLED=false

Logging

# Enable verbose logging
MCP_VERBOSE=true

# Enable debug logging
MCP_VERY_VERBOSE=true

# Log to stdout instead of stderr
MCP_LOGGING_STDOUT=true

Proxy Configuration

# Global proxy settings
HTTP_PROXY=http://proxy.example.com:8080
HTTPS_PROXY=http://proxy.example.com:8080
NO_PROXY=localhost,127.0.0.1

# Service-specific proxy (overrides global)
JIRA_HTTP_PROXY=http://jira-proxy.example.com:8080
CONFLUENCE_HTTPS_PROXY=http://confluence-proxy.example.com:8080
OPSGENIE_HTTP_PROXY=http://opsgenie-proxy.example.com:8080

Custom Headers

# Add custom headers to API requests
JIRA_CUSTOM_HEADERS=X-Custom-Header=value1,X-Another=value2
CONFLUENCE_CUSTOM_HEADERS=X-Custom-Header=value1
OPSGENIE_CUSTOM_HEADERS=X-Custom-Header=value1

Use Cases

AI-Powered Jira Management

User: "Update Jira from our meeting notes"
AI: [Creates/updates issues based on meeting discussion]

Smart Confluence Search

User: "Find our OKR guide in Confluence and summarize it"
AI: [Searches Confluence, retrieves content, provides summary]

Workflow Automation

User: "Show me all urgent bugs in PROJ assigned to me"
AI: [Uses JQL search to filter and display relevant issues]

Documentation Creation

User: "Create a tech design doc for the new feature"
AI: [Creates structured Confluence page with proper formatting]

Incident Management

User: "Show me all critical alerts in Opsgenie and create an incident"
AI: [Lists critical alerts and creates incident with proper responders]

Project Status Reporting

User: "Generate a weekly status report for the PROJ project"
AI: [Queries sprints, issues, and generates formatted report]

Knowledge Base Queries

User: "What do we know about troubleshooting the API service?"
AI: [Searches Confluence knowledge base for relevant documentation]

On-Call Coordination

User: "Who's on-call tonight for the backend team?"
AI: [Queries Opsgenie schedule and returns on-call engineer]

Contributing

We welcome contributions! Please see for details on:

  • Setting up a development environment
  • Building and testing the project
  • Adding new tools and API methods
  • Code style guidelines
  • Pull request process

License

MIT License - see file for details.

Support

Made with ❤️ using Go and the Model Context Protocol