Integrations
Integrations
Connect Jenkins, Jira, Grafana, databases and MCP tools so they appear in the app and the assistant can use them.
Integrations connect tools you already use. Two things happen when you add one: it gets a screen in DevOps Agent, and the assistant can use it in a chat.
| Integration | What you get | Guide |
|---|---|---|
| Jenkins | Job and build overview, and an audit that scores a controller against a standards checklist | Jenkins |
| Jira | A board, issues, comments and transitions, without leaving the app | Jira |
| Grafana | Your dashboards embedded, and the assistant able to query them | Grafana |
| MCP servers | Any MCP-compatible tool — GitHub and others | MCP |
| MySQL | A read-only database connection the assistant can query | MySQL |
Two rules that apply to all of them
They belong to a project. Everyone who can see the project can use the integration. There is no per-person integration.
Only Owners and Admins can add, edit or remove them. Operators and Viewers use what exists. See Roles.
Tokens and safety
Every token you provide is encrypted with AES-256-GCM before it is stored, decrypted only on our server when making a call you asked for, and never shown back to you or to the AI model. See How we protect your credentials.
Give each integration the smallest permissions that work. A read-only Jenkins token, a Jira token from an account that can only see the right projects, a Grafana viewer service account. If a token only reads, nothing — including a confused assistant — can use it to change anything.