Jira and Confluence Cloud
Your agent works in Jira and Confluence Cloud with your key, and never holds it.
- 7 days free
- Cancel anytime
- Nothing to install
- Kind of work
- Projects and issues
- How you connect
- Sign in with your account
- Account name and key
- What waits for you
- Nothing, until you turn on asking
What your agent can do there
Create and update tasks and issues, move them along, leave comments.
- Jira
- Confluence
- issues
- tickets
- wiki
- project management
Jira and Confluence Cloud also runs a remote MCP server of its own. Connect it the same way, and your agent gets its tools too. See the remote MCP servers
At the provider
Technical details
- Hosts
- api.atlassian.com, *.atlassian.net
- Key type
- oauth2-ac
- Key goes in
- Authorization
Which calls read, write or destroy
| When | Class |
|---|---|
| GET HEAD ^(/ex/jira/[^/]+)?/rest/(api/[23]/webhook(/failed)?|builds/0\.1/pipelines/[^/]+/builds/[^/]+)$ | read |
Without a matching rule, GET, HEAD and OPTIONS read, POST, PUT and PATCH write, and DELETE and any other method destroy. A recipe rule only raises a GET the vendor changes something with to a write. No recipe rule makes a call destructive.
Token IP filtering
If the provider can limit a token to IP addresses, allow Sallyport's outbound address. The connection form shows it, ready to copy.
Bring a service the catalogue has never seen
Add its web address and your key, and your agent uses it like any of the 827. If your agent runs into a service you haven’t added, it sends you a link.
- 7 days free
- Cancel anytime
- Nothing to install