Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/theam/claude-dev-kit/atlassiangit clone --depth 1 https://github.com/theam/claude-dev-kitGrade A, and why
atlassian 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 2d 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.
This is a copy
92% identical to atlassian — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"atlassian": {
"type": "http",
"url": "https://mcp.atlassian.com/v1/mcp"
}
}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.
- 2d ago First seen · 6 lines scan A dbcfcd6888ff
atlassian is an MCP server published in the GitHub repository theam/claude-dev-kit (11 stars, last pushed 2d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. It is 92% identical to atlassian, differing in 2 lines, and is treated as a copy.
Other mcp servers, from other repositories
sidekick
MCP server "sidekick" as configured in hesedcasa/sdkck. Launched with sdkck mcp start.
mcp-jira-stdio
MCP server for Jira Cloud — issues, search, comments, attachments, transitions. Runs locally from the mcp-jira-stdio npm package. Needs 5 environment variables to run.
jira-alerts-mcp
MCP server for Jira Service Management Operations — alerts, on-call schedules and responders. Runs locally from the jira-alerts-mcp npm package. Needs 4 environment variables to run.
mcp-atlassian-extended
Extended MCP tools for Jira and Confluence — attachments, agile boards, sprints, calendars. Runs locally from the mcp-atlassian-extended Python package. Needs 5 environment variables to run.
atlassian-server-mcp
Unified stdio MCP server for Jira, Confluence, and Bitbucket Data Center. Runs locally from the @zaimokuza/atlassian-server-mcp npm package.
jira-mcp
MCP server exposing the Jira REST API (boards, sprints, issues, JQL, and a generic passthrough) for Jira Cloud and Data Center. Runs locally from the @thammarongg/jira-mcp npm package.