Files
aiturk-hermes-ide/optional-mcps/atlassian/manifest.yaml
T

41 lines
1.3 KiB
YAML

# Nous-approved MCP catalog entry.
# Presence in this directory = approval. Merged via PR review.
manifest_version: 1
name: atlassian
description: >-
Jira issues and Confluence pages via Atlassian's hosted remote MCP.
source: https://support.atlassian.com/rovo/docs/getting-started-with-the-atlassian-remote-mcp-server/
# Official vendor-hosted remote MCP (URL-only — Hermes never spawns a local
# process for this entry). Native OAuth 2.1 + Dynamic Client Registration;
# Hermes's MCP client + mcp_oauth_manager handle discovery, PKCE, token
# exchange, and refresh.
transport:
type: http
# /v1/sse was deprecated by Atlassian after June 30, 2026 (404s since the
# cutover — OAuth succeeded but every handshake failed; issue #91538).
# /v1/mcp/authv2 is the endpoint Atlassian's docs recommend for custom
# clients (Streamable HTTP, native OAuth 2.1 + DCR — verified live).
url: https://mcp.atlassian.com/v1/mcp/authv2
auth:
type: oauth
# Composer-suggestion triggers (desktop brand pills).
suggest:
keywords:
- jira
- confluence
- atlassian
- bitbucket
hosts:
- atlassian.net
- atlassian.com
- jira.com
post_install: |
On first connection Hermes opens a browser to authorize with
Atlassian (or run `hermes mcp login atlassian`). Approve access,
then restart the session so tools load.