{"id":5312,"library":"mcp-atlassian","title":"MCP Atlassian Integration","description":"The Model Context Protocol (MCP) Atlassian integration is an open-source implementation that bridges Atlassian products (Jira and Confluence) with AI language models following Anthropic's MCP specification. This project, currently at version 0.21.1, enables secure, contextual AI interactions with Atlassian tools while maintaining data privacy and security. It is actively developed, with releases focusing on bug fixes and feature enhancements, typically without a strict, public release cadence.","status":"active","version":"0.21.1","language":"en","source_language":"en","source_url":"https://github.com/anthropic/mcp-atlassian","tags":["atlassian","jira","confluence","ai","llm","mcp","integration","tooling"],"install":[{"cmd":"pip install mcp-atlassian","lang":"bash","label":"Install stable version"}],"dependencies":[{"reason":"Used for configuration validation and schema definition.","package":"pydantic"},{"reason":"Core web framework for the API server.","package":"Flask"},{"reason":"Handles OpenAPI/Swagger specification for the Flask application.","package":"connexion"},{"reason":"Facilitates loading environment variables from .env files.","package":"python-dotenv"},{"reason":"Provides Python bindings for interacting with Atlassian APIs.","package":"atlassian-python-api"}],"imports":[{"symbol":"AtlassianConfig","correct":"from mcp_atlassian.config import AtlassianConfig"},{"symbol":"AtlassianConfigSchema","correct":"from mcp_atlassian.config import AtlassianConfigSchema"},{"symbol":"AtlassianContextManager","correct":"from mcp_atlassian.lib.atlassian_context_manager import AtlassianContextManager"}],"quickstart":{"code":"import os\nfrom mcp_atlassian.config import AtlassianConfig, AtlassianConfigSchema\nfrom mcp_atlassian.lib.atlassian_context_manager import AtlassianContextManager\n\n# Set dummy environment variables for demonstration/validation.\n# In a real scenario, these would be loaded from your shell environment or a .env file.\nos.environ['ATLASSIAN_SUBDOMAIN'] = os.environ.get('ATLASSIAN_SUBDOMAIN', 'your-subdomain')\nos.environ['ATLASSIAN_USERNAME'] = os.environ.get('ATLASSIAN_USERNAME', 'email@example.com')\nos.environ['ATLASSIAN_API_TOKEN'] = os.environ.get('ATLASSIAN_API_TOKEN', 'your-api-token')\nos.environ['CONFLUENCE_SPACE_ID'] = os.environ.get('CONFLUENCE_SPACE_ID', 'YOURSPACE')\nos.environ['JIRA_PROJECT_KEY'] = os.environ.get('JIRA_PROJECT_KEY', 'YOURPROJ')\n\ntry:\n    # Load configuration from environment variables\n    config: AtlassianConfig = AtlassianConfigSchema().load(os.environ)\n    print(\"Configuration loaded successfully.\")\n    print(f\"Atlassian Subdomain: {config.atlassian_subdomain}\")\n\n    # Initialize the Atlassian Context Manager\n    # This step demonstrates setup but will require valid credentials for actual API calls.\n    context_manager = AtlassianContextManager(config)\n    print(\"AtlassianContextManager initialized.\")\n    # To perform an actual operation, you would use methods like:\n    # confluence_doc = context_manager.get_confluence_document('page-title')\n    # jira_issue = context_manager.get_jira_issue('JIRA-123')\n\nexcept Exception as e:\n    print(f\"Error loading configuration or initializing: {e}\")\n    print(\"Please ensure all required ATLASSIAN_* environment variables are set correctly.\")\n","lang":"python","description":"This quickstart demonstrates how to programmatically load the `mcp-atlassian` configuration from environment variables and initialize the `AtlassianContextManager`. It showcases the core configuration and component setup, which is essential for any interaction with the library. Note that actual Atlassian API calls would require valid credentials and specific method calls on the `context_manager` object."},"warnings":[{"fix":"Ensure all required environment variables are correctly defined in your shell environment or provided via a `.env` file (which `python-dotenv` can load automatically) before running the application or initializing components.","message":"Configuration for `mcp-atlassian` relies heavily on specific environment variables (e.g., `ATLASSIAN_SUBDOMAIN`, `ATLASSIAN_API_TOKEN`, `CONFLUENCE_SPACE_ID`). Incorrectly set or missing variables are the most common source of runtime errors.","severity":"gotcha","affected_versions":"All versions"},{"fix":"For most use cases, it's recommended to interact with the library via its provided CLI or server commands. If programmatic embedding is required, carefully review the official documentation and source code to understand component dependencies and expected environment setup.","message":"The library is primarily designed to function as a standalone service or CLI (`mcp-atlassian run-server` or `mcp-atlassian cli`). While individual core components can be imported, their setup and expected operational context often assume the environment is configured as if running the full service, which might not be immediately intuitive for direct programmatic embedding.","severity":"gotcha","affected_versions":"All versions"},{"fix":"Pin your `mcp-atlassian` dependency to a specific version (e.g., `mcp-atlassian==0.21.1`) and thoroughly review the release notes or GitHub commit history for any breaking changes when planning an upgrade to a newer minor version.","message":"As a pre-1.0 library (currently `0.21.1`), `mcp-atlassian` does not guarantee strict semantic versioning. Breaking changes to API interfaces, configuration schemas, or core logic may be introduced in minor version increments (e.g., `0.x.y` to `0.x+1.z`).","severity":"breaking","affected_versions":"<1.0.0"}],"env_vars":null,"last_verified":"2026-04-13T00:00:00.000Z","next_check":"2026-07-12T00:00:00.000Z"}