MCP Atlassian

Created By
final-ila year ago
MCP Server handling Jira integrations
Overview

What is MCP Atlassian?

MCP Atlassian is a Model Context Protocol (MCP) server designed for integrating with Atlassian products, specifically Confluence and Jira, supporting both Cloud and Server/Data Center deployments.

How to use MCP Atlassian?

To use MCP Atlassian, you need to set up authentication tokens for Confluence and Jira, install the server using methods like pip or Docker, and configure it with the necessary command line arguments for your specific use case.

Key features of MCP Atlassian?

  • Supports integration with both Confluence and Jira.
  • Compatible with Cloud and Server/Data Center deployments.
  • Provides various tools for managing Confluence pages and Jira issues.
  • Allows configuration through command line arguments or environment variables.

Use cases of MCP Atlassian?

  1. Automating the management of Confluence pages.
  2. Streamlining Jira issue tracking and updates.
  3. Integrating Confluence and Jira for enhanced project management.

FAQ from MCP Atlassian?

  • What products does MCP Atlassian support?

MCP Atlassian supports both Confluence and Jira.

  • Is there a specific version requirement for Server/Data Center?

Yes, Confluence version 6.0+ and Jira version 8.14+ are required for Server/Data Center deployments.

  • How can I install MCP Atlassian?

You can install it using pip, Docker, or other methods as described in the setup guide.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
final-il
Star
0
Language
Shell
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago