JiraGuard
A governed MCP server for Jira Cloud that gives each AI agent its own scoped identity and bearer token, with per-agent policies (allowed projects, tools, fields, write modes of deny/approve/allow, and rate limits). It provides tools for reading and searching issues, commenting, and proposing field changes, with risky writes held in an approval queue showing change diffs. Every read and write is written to an audit log with before/after values, flagged for prompt injection in issue text, and can be reverted. Includes tools like guard_whoami and instant token revocation.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
JiraGuard
JiraGuard is a Forge app that lets a Jira admin connect an AI agent to Jira without handing it one broad credential. Each agent gets its own token and a policy. Risky writes wait for a person. Issue text is marked as untrusted and scanned for instruction-like content. Every call is written to an audit log.
Built for Codegeist 2026. Licensed under MIT.
What an admin can do
Create an agent and copy its token once.
Limit that agent to projects, tools, and a write mode:
deny,approve, orallow.Hold a risky write, read the diff, and approve or reject it.
Read an audit row for each call, including before and after values.
See which injection matchers fired, written as
injection: tool_request, reassign.Revoke an agent. The next call from that token fails.
The desk is under Apps → JiraGuard. A Jira admin can also open it from the gear menu, then Apps. Creating an agent, editing a policy, revoking an agent, and approving a write require the Jira Administer permission.
Related MCP server: mcp-jira-scoped
Connect a client
Install the app on a Jira Cloud site and approve
read:jira-work,write:jira-work, and app storage.Open JiraGuard, then Agents, then Create agent. Start with write mode
approve.Copy the token. It is shown once.
Copy the endpoint URL on the Agents page.
Point an MCP client at that URL with the token as a bearer token.
{
"mcpServers": {
"jira-guarded": {
"url": "https://<endpoint-from-the-agents-page>",
"headers": { "Authorization": "Bearer <AGENT_TOKEN>" }
}
}
}Call
guard_whoami, thenjira_search_issueson an allowed project.
The other tools are jira_get_issue, jira_list_transitions, jira_add_comment, jira_transition_issue, jira_assign_issue, and jira_update_fields.
Day to day
Task | Where |
Review a held write | Approvals tab. Read the diff, then Approve or Reject. |
See what an agent did | Audit tab. Filter by agent, outcome, or date. |
Stop an agent | Agents tab, then Revoke. The next request fails. |
Look for an injection attempt | Audit tab. Turn on Injection flagged. Read the Reason cell. |
Not in this version
One-click revert of a logged change.
Enforced rate limits.
jira_create_issue.Injection modes other than annotate. Flagged text is wrapped and recorded. It is not redacted or blocked.
Injection detection is a set of matchers, not a guarantee. Jira records the write as the app, so use the JiraGuard audit log to see which agent acted.
Develop
npm install
npm testThe Forge app lives in product/. From that directory, npm install and npm run deploy build the page and deploy the development environment. npm test at the repo root is the check for src/.
Docs
React 18 and the Forge SDK build the admin page. esbuild bundles it. Cursor was used during development.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Security gateway for AI agents: policy, approval, and audited execution, no secrets shared.
Governed access to sensitive data, secrets and APIs for AI agents. A signed proof for each decision.
Zero-secret MCP gateway for AI agents: risk-scored, audited calls with human-in-the-loop approval.
Password vault for AI agents with scoped, user-approved access
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to interact with Jira Cloud and Confluence through natural language, performing JQL searches, issue management, and Confluence page creation.106 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage Jira tasks, issues, and projects using Atlassian's modern scoped API tokens, with safety features like read-only default and delete confirmation.72 npm4Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI assistants to securely read and search Jira and Confluence Cloud content while enforcing read-only access and protecting stored credentials.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to create, search, update, and manage Jira issues and Confluence pages via natural language through the Atlassian Cloud REST APIs.MIT