Back to integrations

Jira integration for background agents

Enable Jira issue access, triggers, and optional Jira CLI in sandbox.

Book a demo

Integration details

Connection

  • MCP via Personal API token
  • MCP via Service account API token
  • MCP via Service account OAuth client credentials

Agent actions

Jira CLI

  • Use Jira CLI

    Run Jira CLI commands with the configured Jira connection.

Jira MCP

  • jira_auth_whoami

    Show the Jira account behind the current auth context.

  • jira_project_list

    List Jira projects visible to the connected caller.

  • jira_issue_get

    Fetch a single Jira issue by key.

  • jira_issue_search

    Search Jira issues with a JQL query.

  • jira_issue_create

    Create a Jira issue.

  • jira_issue_delete

    Delete a Jira issue by key.

  • jira_issue_comment_add

    Add a comment to a Jira issue.

  • jira_issue_comment_delete

    Delete a comment from a Jira issue.

  • jira_issue_assign

    Assign or clear the assignee on a Jira issue.

  • jira_issue_transition_list

    List workflow transitions currently available for a Jira issue.

  • jira_issue_transition

    Transition a Jira issue to a new workflow state.

  • jira_issue_update

    Update summary, description, or other editable fields on a Jira issue.

  • jira_issue_editmeta

    Show edit metadata for a Jira issue.

Credential safety

Credential-less sandboxes

Mistle lets agents access connected services without placing provider credentials inside the sandbox. Approved outbound requests are routed through Mistle's credential proxy, where authentication happens outside the agent runtime.

Credentials stay encrypted in Mistle's control plane and are applied only when a request is authorized for the calling sandbox and organization.

Read the credential-less sandboxes article
Diagram showing sandbox traffic routed through an egress proxy before credential injection.