Jira and Confluence
Search Jira issues and Confluence pages from one grant, resolved against your Atlassian cloud site.
What a thread can reach, and nothing else.
You grant scopes once in the console. Everything inside them becomes searchable, citable context. Everything outside them stays where it is.
- Jira issues and usersgranted
- Confluence content and spacesgranted
- Confluence searchgranted
- readatlassian_search_jiraSearch Jira issues
- readatlassian_search_confluenceSearch Confluence pages
Anything you did not grant is invisible to the model. Revoke a scope and the content it covered stops being reachable on the next request, with nothing left behind in a thread.
Three steps, then it is just context.
Authorize from the console
OAuth in a couple of clicks. Tokens are stored encrypted and nemu never sees a password.
Pick the scopes
Each one is a separate grant. Approve the ones you want and leave the rest untouched.
Ask, search, index
Granted content answers questions in the chat and is available to the indexing API on your credits.
More in Development
Start with your keys, keep the whole bill.
The gateway, the chat and the computer on one account. Free is enough to evaluate the gateway and the chat on your own keys, and your provider keeps billing the tokens exactly as it does today.