# Integration catalogue > Integrations that install into a running connector without a rebuild. Each shows where it connects, what it asks for and which tools it gives the model. Marketplace # Integrations and tools An integration connects Buff to your system — a tracker, a service, an internal API — and stays inside your network. It installs into a running connector, without a rebuild. For each one you can see where it will be able to go and which tools it will give the model. The list comes from the signed catalogue the connector itself reads. Checked on 2026-10-05. Category All Issue trackers Company documents Design Internet Access Read only No credentials Sort by name by update 14 integrations in the catalogue - [Bitbucket Cloud 1.1.0 · buff Questions and answers right in bitbucket.org pull requests — where the review happens. Issue trackers 3 of 4 read only webhooks](https://buff.systems/en/marketplace/bitbucket-cloud) - [Bitbucket Data Center 1.1.0 · buff Questions and answers right in the pull requests of your Bitbucket Data Center or Server — where the review happens. Issue trackers 3 of 4 read only webhooks](https://buff.systems/en/marketplace/bitbucket-dc) - [Confluence 1.1.0 · buff The team’s knowledge base as context for answers — and questions right in the page discussion. Data Center, Server and Cloud. Company documents 3 of 4 read only webhooks](https://buff.systems/en/marketplace/confluence) - [Figma 1.1.0 · buff Designs as context: parameters, tokens and screen structure for any model, the picture for one that can see. Questions in design comments. Design 7 of 8 read only webhooks](https://buff.systems/en/marketplace/figma) - [Files on disk 1.0.3 · buff Folders on the server and SMB network folders as context: Word, Excel, PowerPoint — new and old formats — PDF and text. Read only, no index. Company documents 3 of 3 read only](https://buff.systems/en/marketplace/files) - [Gitea 1.1.0 · buff Questions and answers right in the issues and pull requests of your Gitea or Forgejo — where the team already discusses the code. Issue trackers 3 of 4 read only webhooks](https://buff.systems/en/marketplace/gitea) - [GitHub 1.1.0 · buff Questions and answers right in GitHub issues and pull requests — both in the github.com cloud and in Enterprise Server inside your network. Issue trackers 3 of 4 read only webhooks](https://buff.systems/en/marketplace/github) - [GitLab 1.1.0 · buff Questions and answers right in the issues and merge requests of your GitLab — your own installation or gitlab.com, either way. Issue trackers 3 of 4 read only webhooks](https://buff.systems/en/marketplace/gitlab) - [Google Drive 1.1.0 · buff Google Docs, Sheets and Slides as context for answers, and questions right in comments. The research report comes back as a document in the same folder. Company documents 5 of 7 read only](https://buff.systems/en/marketplace/google-drive) - [Internet 1.0.3 · buff Search and read public pages from your perimeter, within the admin’s allow and block lists. DuckDuckGo without a key, your own SearXNG, Brave with a key. Internet 2 of 2 read only](https://buff.systems/en/marketplace/web) - [Jira 1.5.0 · buff Tasks, questions and answers right in Jira Data Center and self-hosted Server tickets — without leaving the tracker your team already works in. Issue trackers 2 of 3 read only webhooks](https://buff.systems/en/marketplace/jira) - [Jira Cloud 1.1.0 · buff Tasks, questions and answers right in Jira Cloud tickets — without leaving the tracker your team already works in. Issue trackers 2 of 3 read only webhooks](https://buff.systems/en/marketplace/jira-cloud) - [Notion 1.1.0 · buff Notion pages and databases as context for answers — and questions right in the page discussion. The research report comes back as a page. Company documents 6 of 8 read only webhooks](https://buff.systems/en/marketplace/notion) - [Redmine 1.1.0 · buff Questions and answers right in Redmine issues — in the tracker you already have, which is not going anywhere. Issue trackers 2 of 3 read only](https://buff.systems/en/marketplace/redmine) ## What an integration can and cannot do These rules are the same for every integration, whoever wrote it and whenever. - ### Signed by us The catalogue holds only integrations we built and signed. The connector checks the signature on its side, before writing to disk. - ### They go only where you said Outward traffic goes only through the connector and only to the addresses in the integration’s settings; internet search stays within your allow and block lists. Everything else is rejected. - ### They do not see your tokens Credentials are stored in the connector, which inserts them into requests itself — the one exception is the network folder password, which the integration receives. Each integration is a separate process under its own OS user. - ### They install without a rebuild One click on the connector’s local page or one command in the console. There is no need to reinstall the agent. More in the [security section](https://buff.systems/en/security) and the [connector documentation](https://buff.systems/en/docs/connector). The integration you need is not there? [Send a request](https://buff.systems/en/contact) — we curate the catalogue, so no third-party code gets into your perimeter. You can also connect your own tool yourself — [as your own MCP server](https://buff.systems/en/docs/connector/custom-mcp): your administrator marks which of its functions the model sees.