ClawTrust
4.9k Downloads
Overview
Integrate with Jira Cloud via the Maton managed OAuth gateway to search, create, update, transition, and manage Jira issues and projects from within an agent or workflow.
Key Advantages
1.Managed OAuth via Maton removes the need to handle raw Jira OAuth flows directly.
2.Covers the most common Jira Cloud operations: JQL search, CRUD on issues, transitions, comments, user lookup, and key metadata (issue types, priorities, statuses).
3.Clear, concrete HTTP patterns and examples in Python and JavaScript make it straightforward to reason about what the skill is doing.
4.Explicit error semantics and troubleshooting guidance (400/401/429, passthrough Jira errors, API key verification) support robust handling in agents.
5.Supports multiple Jira connections with explicit selection via Maton-Connection header, enabling multi-tenant or multi-instance use cases.
Use Cases
- Building agents that search and summarize Jira issues using JQL for support, product, or engineering teams.
- Automating ticket creation, updates, and assignments from chat or other event-driven workflows (e.g., incident bots, support bots).
- Managing Jira workflows by listing transitions and moving issues across statuses programmatically.
- Adding and reading comments on Jira tickets as part of collaborative troubleshooting or approval flows.
- Fetching project and issue metadata (projects, issue types, priorities, statuses) to drive dynamic forms or validation in conversational UIs or internal tools.
Evaluation Scores
7.7
/ 10
Reliability
7.2
Functionality
8.2
Usability
7.8
Safety
8.0
Performance
7.3
Compatibility
7.5
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
7.7/103/19/2026▼
OS: linux-arm64LLM: z-ai/glm-5
**Judgement:** A solid, practical Jira Cloud integration suitable for production-style agents that need to work with issues, projects, and workflows, assuming you are comfortable configuring the Maton API key and OAuth connections.
**What it does well**
- Uses a **managed OAuth gateway** (`gateway.maton.ai` + `ctrl.maton.ai`) so the skill doesn’t need to implement Jira’s OAuth dance itself.
- Supports a **wide slice of core Jira Cloud APIs**: JQL search, get/create/update/delete issues, transitions, comments, user lookup, and metadata for issue types/priorities/statuses.
- Provides **clear REST patterns and examples** (Python, JS) that match Jira’s own API, making behavior predictable and easy to debug.
- Handles **multi-connection scenarios** via the `Maton-Connection` header, which is useful for multi-tenant or multi-instance agents.
**Key risks / limitations**
- **External dependency on Maton**: everything goes through `gateway.maton.ai` and `ctrl.maton.ai`, so availability and latency depend on that service as well as Atlassian.
- **Configuration overhead**: requires a `MATON_API_KEY`, setting up a Jira OAuth connection, and obtaining the Jira Cloud ID before most calls; misconfiguration will cause 400/401 errors.
- **Rate limiting**: explicitly limited to ~10 requests/second per account; high-throughput or bulk-processing agents must be rate-aware.
- **Scope coverage**: focuses on Jira core REST v3; Agile/board APIs and other advanced Jira features may require additional scopes and coordination with Maton support.
**Recommended scenarios**
- Agents that **triage, create, and maintain Jira issues** (e.g., incident management, customer support, bug intake, and status-update bots).
- Internal tools or copilots that need to **search Jira via JQL and summarize or filter results** for humans.
- Workflow automation that **updates statuses (transitions)**, assigns users, or posts comments based on external events.
- Multi-tenant or consulting scenarios where a single agent needs to **operate across multiple Jira instances** using separate Maton connections.
Comments (0)
No comments yet. Be the first!