List tickets from a saved perspective or find a ticket by number. Specify perspective ID or name to filter results, or use a ticket number for direct lookup.
Produce a ticket-ready remediation payload for a chokepoint, containing summary, justification, change plan, and rollback note for direct paste into Jira or ServiceNow.
Retrieve the full field-level change history for a ticket, including status, assignee, tags, and custom field changes, to trace how a ticket evolved over its lifetime.
Resolve a Jira ticket, create a local branch with auto-generated name, fetch project README from Bitbucket for conventions, and get a next-steps summary. Use issue key or free-text search.
An MCP server that builds a local webpage to view AI plans, reports, and diagrams, so the AI only needs to send a URL pointer instead of long text. It provides three tools (view_plan, view_report, view_diagram) and tracks project changes for diff viewing.
Record investigation steps, evidence, findings, or remediation actions directly on a Jira ticket. Preserves the audit trail of security incident responses.
Lists folders in a Postman collection, showing name, ID, path, and request count. Verify a folder exists for a Jira ticket before running its requests.
Retrieves and consolidates Jira ticket requirements, comments, architecture docs, and coding standards. Call this first when starting work on a ticket.
Create a git worktree for a ticket or feature, giving you an isolated directory for parallel work without switching branches. Name the branch automatically from a ticket ID.
Retrieve all available Jira fields with their metadata and field IDs for a specific ticket or project. The returned mapping enables accurate field updates.