ToolsMCP
Atlassian Extended
Listed in the official MCP Registry with an installable pypi package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- vish288 (GitHub)
- Prerequisites
- Install mcp-atlassian-extended from pypi (stdio transport). Declares 5 secret inputs. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.20.0 · updated
- Official links
Publisher’s description
Jira/Confluence MCP server (MCP 2026-07-28): sprints, boards, attachments; writes or read-only
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.20.0, registry status active. 1 package (pypi)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- vish288 (GitHub)
- Version observed
- 0.20.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.vish288%2Fmcp-atlassian-extended/versions/0.20.0
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Track tasks and tickets | Publisher description mentions “jira”, “sprints”, “boards”. | No connection check or task run. Capability is as described by the publisher. | Rule project-tracking matched: “jira”, “sprints”, “boards”. Rule project-tracking. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
mcp-atlassian-extended(pypi, stdio, 5 secret inputs)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.vish288/mcp-atlassian-extended
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.