Integrations for AI coding agents

Azure DevOps repositories and pull requests as cited context, so agents and developers can ask how the code works and why it changed.

repositories, pull requests, code history

Repositories and pull requests from Bitbucket Cloud and Data Center — kept current as your team pushes, and cited as sources in answers.

repositories, pull requests, code history

Repositories, pull requests, issues, discussions, and full code history — indexed, kept in sync on every push, and cited in answers.

repositories, pull requests, issues, discussions, code history

Repositories and merge requests from GitLab.com and self-managed instances — indexed with full history and cited in answers as your team pushes changes.

repositories, merge requests, code history

The CI Failure Agent analyzes failed Bitbucket Pipelines builds on your selected repositories and posts root-cause reports to the pull request.

pipeline runs, CI failure analysis, PR triage reports

The CI Failure Agent reads Buildkite build logs, analyzes failures across your pipelines, and posts root-cause reports to the pull request.

builds, build logs, CI failure analysis

The CI Failure Agent watches your selected CircleCI projects via webhook, analyzes failed builds, and posts root-cause reports to the pull request.

builds, CI failure analysis, PR triage reports

Unblocked’s CI Failure Agent analyzes failed GitHub Actions runs on your selected repositories and posts root-cause reports to the pull request.

workflow runs, CI failure analysis, PR triage reports

The CI Failure Agent analyzes failed GitLab pipeline runs on your selected projects and posts root-cause reports to the merge request.

pipeline runs, CI failure analysis, MR triage reports

The CI Failure Agent analyzes failed Jenkins builds on your connected repositories and posts root-cause reports to the pull request.

builds, CI failure analysis, PR triage reports

Documents from your Coda Enterprise organization — select files or folders and Unblocked indexes them as cited sources in answers.

documents, folders

Pages and blog posts from the Confluence spaces you select — including rendered macro content — indexed and cited in answers.

pages, blog posts, spaces

Any public web page you specify — vendor docs, API references, standards — crawled and cited alongside your internal sources.

web pages

Google Docs, Sheets, Slides, text files, and PDFs from the files, folders, and shared drives you choose — searchable alongside code and engineering history.

Google Docs, Google Sheets, Google Slides, text files, PDFs, folders, shared drives

Your whole Google Workspace Drive — all current and future content, or the files, folders, and drives you pick — connected once by an administrator and answered with document-permission awareness.

Google Docs, Google Sheets, Google Slides, text files, PDFs, shared drives, personal drives, users, groups, and content permissions

Documents and pages from the SharePoint sites you select, referenced in answers with links back to the source.

documents, pages, sites

Pages from your Notion workspaces, indexed as cited sources so answers can draw on specs, wikis, and design docs.

pages, workspaces

Internal questions, answers, and articles from Stack Overflow for Teams, so hard-won troubleshooting knowledge shows up in answers.

questions, answers, articles

Dashboards, notebooks, surveys, experiments, and feature flags from your selected PostHog projects, connected to code and engineering context so agents can investigate product usage and the changes behind it.

dashboards, notebooks, surveys, experiments, feature flags

A live schema wiki and read-only SQL access to your Snowflake databases, reconciled with your code, pull requests, and docs.

schema wiki, read-only SQL queries, table relationships

Projects, tasks, and comments from your Asana workspaces, surfaced as cited context with their project names attached.

projects, tasks, comments

Issues and projects from Jira Cloud and Data Center — with sprint-aware answers that connect tickets to the code and PRs behind them.

issues, projects, sprints

Issues from the Linear teams you select, indexed so answers can trace a feature or bug from ticket to the code that shipped it.

issues, teams

Support tickets from the Zendesk brands you select, indexed and linked back to the original ticket so answers stay grounded in real customer issues.

tickets, brands

Public and private channel conversations from Microsoft Teams — indexed with access permissions respected, with Q&A via @mention.

channels, threads, @mention Q&A

Public and private channels and threads — indexed with access permissions respected, plus in-Slack Q&A by @mentioning Unblocked.

channels, threads, @mention Q&A

Incidents, logs, metrics, monitors, and hosts from Datadog — referenced in answers so investigations connect symptoms to recent changes.

incidents, logs, metrics, monitors, hosts

Live, read-only access to Compute, Cloud Logging, and Cloud Monitoring in the Google Cloud projects you connect, queried through Google’s native MCP services.

Compute, Cloud Logging, Cloud Monitoring

Issues, errors, and events from Sentry — connected to the code and pull requests behind them for faster root-cause analysis.

issues, errors, events

Any MCP server you can reach over public HTTPS, connected as a data source — Unblocked calls the read-only tools you select while it answers, with nothing ingested or indexed.

read-only MCP tools, live tool results, tool discovery