Paperclip’s Jira MCP connector gives your AI agents tools to read issues, add comments and update work items. Each tool can be Allowed, Ask first or Off.
Agents reach issues the authorizing account can access on the selected site, subject to project permissions and issue security. Paperclip has no project picker.
What agents can do with Jira
- Read an issue before commenting
getJiraIssue·addOrEditJiraIssueComment - Review and update a work item
getJiraIssue·editJiraIssue - Review before changing issue status
getJiraIssue·transitionJiraIssue
How to connect Jira
- In Paperclip, open Connectors and select Jira.
- On the Access step, choose the identity and which agents may use the connection.
- Select Sign in with Jira and authorize in Atlassian’s browser flow. Choose the intended site if Atlassian asks.
Jira tools for agents11
Write 11
addOrEditJiraIssueCommentAdd a comment, or edit an existing one.
atlassianUserInfoGet the current authenticated user's account information.
createJiraIssueCreate a new Jira work item.
discoverNatural-language search over the deferred tool catalogue.
Full description
Natural-language search over the deferred tool catalogue. Returns a list of potentially related tools, their toolSchema and operations for running on execute.
editJiraIssueEdit an existing work item; only fields editable on that work item can be set.
executeDestructiveExecution pathway to run any deferred tools identified via discovery.
Full description
Execution pathway to run any deferred tools identified via discovery. Utilisation of each execute type is used to apply agent-level confirmation.
Show all 11 Write tools
Write tools 7–11
executeReadExecution pathway to run any deferred tools identified via discovery.
Full description
Execution pathway to run any deferred tools identified via discovery. Utilisation of each execute type is used to apply agent-level confirmation.
executeWriteExecution pathway to run any deferred tools identified via discovery.
Full description
Execution pathway to run any deferred tools identified via discovery. Utilisation of each execute type is used to apply agent-level confirmation.
getAccessibleAtlassianResourcesList all Atlassian sites and apps accessible to the authenticated user, including their cloudId values.
Full description
List all Atlassian sites and apps accessible to the authenticated user, including their cloudId values. Required first call for any tool because every tool call needs a cloudId.
getJiraIssueGet a Jira work item by ID or key.
transitionJiraIssueTransition an work item to a new status, and/or assign it to a sprint or backlog.
Tool availability and permissions
This list describes the reviewed tools. Your selected method, provider access and action permissions determine what agents can use.
These lists use a conservative permission policy. Read requires a provider read-only hint or a reviewed Paperclip read rule. Evidence that an action changes data or submits information elsewhere puts it in Write. Write also includes actions we cannot verify as read-only. Read describes the reviewed evidence; it does not guarantee that an action has no side effects. A connected account can group actions differently.
This list includes the provider’s directly exposed Primary tools. Deferred operations and Confluence tools are excluded. executeRead, executeWrite and executeDestructive are provider tools; their individual API operations are not separate tools.
Connection policies
Discovered actions follow the connection’s policies. Review their permissions and set actions to Ask first or Off as needed. Comments and changes are attributed to the authorizing account.
Jira connector FAQ
Can I require approval for actions?
Set an action to Ask first to require human approval of each call or Off to prevent calls. Allowed actions run without approval. Read and Write grouping is separate from these settings.
What can agents reach in Jira?
Agents reach issues the authorizing account can access on the selected site, subject to project permissions and issue security. Paperclip has no project picker.
What do I need before connecting?
Use Jira Cloud and an Atlassian account with access to the intended site and projects. Tenant administrators may need to approve the client.
