Skip to content

feat(examples): add Atlassian expert agent example#2963

Merged
dgageot merged 1 commit into
docker:mainfrom
maxcleme:co-add-atlassian-expert-example
Jun 2, 2026
Merged

feat(examples): add Atlassian expert agent example#2963
dgageot merged 1 commit into
docker:mainfrom
maxcleme:co-add-atlassian-expert-example

Conversation

@maxcleme
Copy link
Copy Markdown
Member

@maxcleme maxcleme commented Jun 2, 2026

No description provided.

Signed-off-by: maxcleme <maxime.clement@docker.com>
Copy link
Copy Markdown

@docker-agent docker-agent left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assessment: 🟢 APPROVE

The new examples/atlassian-expert.yaml is a clean and correct addition.

What was checked:

  • OAuth configuration: The absence of an explicit oauth: block is correct and intentional. The runtime automatically handles OAuth via RFC 7591 Dynamic Client Registration when connecting to SaaS MCP endpoints like Atlassian. This matches the same pattern used by notion-expert.yaml.
  • Transport type: streamable is a valid alias for the Streamable HTTP transport (equivalent to streamable-http per the source code in pkg/tools/mcp/remote.go).
  • Model config: Using a named models: block with the sonnet alias is a valid and consistent pattern, matching other examples like alloy.yaml and coder.yaml.

@maxcleme maxcleme marked this pull request as ready for review June 2, 2026 08:14
@maxcleme maxcleme requested a review from a team as a code owner June 2, 2026 08:14
Copy link
Copy Markdown

@docker-agent docker-agent left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assessment: 🟡 NEEDS ATTENTION

toolsets:
- type: mcp
remote:
url: https://mcp.atlassian.com/v1/mcp/authv2
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[MEDIUM] Atlassian MCP endpoint may require OAuth credentials that are not configured

The URL https://mcp.atlassian.com/v1/mcp/authv2 contains /authv2 in the path, which strongly suggests this endpoint requires OAuth 2.0 authentication. No oauth block is configured under remote, which may cause the agent to fail at runtime when the Atlassian MCP server rejects the unauthenticated connection.

If the docker-agent runtime supports Dynamic Client Registration (RFC 7591) or browser-based OAuth flows without a static oauth block, this may work as-is. However, if Atlassian's MCP server does not support DCR, explicit credentials are required. The examples/remote_mcp_oauth.yaml file shows the pattern for servers that require static OAuth credentials:

remote:
  url: "https://mcp.atlassian.com/v1/mcp/authv2"
  transport_type: streamable
  oauth:
    clientId: "your-atlassian-client-id"
    clientSecret: "your-atlassian-client-secret"
    callbackPort: 8080
    scopes:
      - "read:jira-work"
      - "read:confluence-space.summary"

Please verify whether the Atlassian MCP server supports Dynamic Client Registration or whether explicit OAuth credentials should be documented (even as placeholder values) in this example.

@dgageot dgageot merged commit 1133c75 into docker:main Jun 2, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants