mcp-atlassian is a Model Context Protocol server that lets AI assistants work with Atlassian's Confluence and Jira services. Developers use it to search documentation, find issues, create tickets, and update Jira work through an assistant, with support for Cloud and Server/Data Center deployments. The catalogue entries provide instructions and settings for using the server.
Borrowing it
Nothing to install: this file belongs to sooperset/mcp-atlassian. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sooperset/mcp-atlassian/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/sooperset/mcp-atlassianWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/sooperset/mcp-atlassian/copilot-instructions)<a href="https://agentmods.dev/instructions/sooperset/mcp-atlassian/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/sooperset/mcp-atlassian/copilot-instructions/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/sooperset/mcp-atlassian/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/sooperset/mcp-atlassian/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.01180 | $0.01180 |
| Opus 5.5 | $0.00472 | $0.00472 |
| Sonnet 5.5 | $0.00236 | $0.00236 |
| Haiku 4.5 | $0.00118 | $0.00118 |
Grade A, and why
mcp-atlassian copilot-instructions.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
8 near-identical copies found in the catalogue:
- ai_agent_mcp_jira copilot-instructions.md — 100% identical, 0 lines differ
- mcp-atlassian copilot-instructions.md — 100% identical, 0 lines differ
- jira-mcp copilot-instructions.md — 100% identical, 0 lines differ
- AtlMCPforDC copilot-instructions.md — 100% identical, 0 lines differ
- atlassian-mcp-server copilot-instructions.md — 100% identical, 0 lines differ
- atlassian-mcp copilot-instructions.md — 100% identical, 0 lines differ
- mcp-atlassian-with-bitbucket copilot-instructions.md — 100% identical, 0 lines differ
- mcp-atlassian-dc copilot-instructions.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Atlassian - Development Guide
Model Context Protocol (MCP) server for Atlassian products (Jira & Confluence). Python ≥3.10.
Build, Test, and Lint
Dependencies:
uv sync --frozen --all-extras --dev # Install all dependencies
Code Quality (required before commit):
pre-commit run --all-files # Run all checks: ruff, prettier, mypy
Testing:
# Run all tests
uv run pytest
# Run with coverage
uv run pytest --cov=mcp_atlassian
# Run single test file
uv run pytest tests/unit/test_preprocessing.py
# Run single test function
uv run pytest tests/unit/test_preprocessing.py::test_specific_function
Running the Server:
uv run mcp-atlassian # Start MCP server
uv run mcp-atlassian --oauth-setup # OAuth configuration wizard
uv run mcp-atlassian -v # Verbose logging mode
Architecture
Mixin-Based Composition
Functionality is organized into focused mixins that compose together:
- Jira:
JiraFetcherinherits from 13 feature mixins (ProjectsMixin, IssuesMixin, WorklogMixin, etc.) - Confluence:
ConfluenceFetcherinherits from 7 feature mixins (SearchMixin, PagesMixin, SpacesMixin, etc.)
Each mixin lives in its own module under src/mcp_atlassian/jira/ or src/mcp_atlassian/confluence/.
Client + Fetcher Pattern
- Client classes (
JiraClient,ConfluenceClient): Authentication, configuration, and API session management - Fetcher classes (
JiraFetcher,ConfluenceFetcher): Business operations by composing mixins; inherit from Client
Protocol-Based Dependencies
Mixins declare dependencies via Protocol interfaces instead of direct imports:
class IssuesMixin(AttachmentsOperationsProto, FieldsOperationsProto):
# Mixin knows it needs attachment and field operations
# Protocols define the contract without circular imports
The final Fetcher class satisfies all protocols through multiple inheritance.
Data Models
- All models extend
ApiModelbase class withfrom_api_response()for deserialization - Use
TimestampMixinfor timestamp handling across Jira/Confluence models - Models support
to_simplified_dict()for MCP tool responses - Located in
src/mcp_atlassian/models/
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 136 lines · 1,180 tokens per session scan A 45a5eaee76b1
mcp-atlassian copilot-instructions.md is an instructions file published in the GitHub repository sooperset/mcp-atlassian (6,056 stars, last pushed 1mo ago), licensed MIT. It adds 1,180 tokens to every session, about $0.0047 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.