Integrations index
Port offers a wide variety of integrations for popular tools and platforms. These integrations come with default data models and mappings configured by us to provide you with a fast plug & play experience.
Once installed, you can fully customize and extend these integrations to fit your exact needs.
Don't see your desired tool in the available integrations below?
No problem! Port can be integrated with any tool or platform via a custom integration.
GitHub (Ocean)
GitHub (sunset)
GitLab v2
GitLab (deprecated)
BitBucket
BitBucket server
AzureDevops
Jenkins
Octopus Deploy
ArgoCD
Komodor
Istio
FluxCD
Knative
Kyverno
OpenShift
Trivy
Jira
Jira server (self-hosted)
Linear
Kubernetes
AWS (self-hosted)
AWS (hosted by Port)
Azure
GCP
Terraform
Datadog
New Relic
Sentry
Prometheus
Snyk
Wiz
SonarQube
Aikido
Checkmarx
Armorcode
Launchdarkly
PagerDuty
StatusPage
FireHydrant
OpsGenie
ServiceNow
Rootly
Dynatrace
Azure Monitor
Kubecost
Opencost
Kafka
Okta
Microsoft Entra ID
Amplication
Backstage
Slack
Zapier
Ocean custom
Github Copilot
Claude AI
Cursor
OpenAI
n8n
Integrations vs. MCP connectors
Integrations are not the only way to connect external tools to Port. Port also supports MCP connectors, which give Port AI real-time access to a tool without syncing data into the catalog.
Use an integration when you need persistent data in Port - for ownership, relations between resources, scorecards, or workflow automation.
Use an MCP connector when you want Port AI to query a tool on demand without modeling its data. MCP connectors require minimal configuration and are a good starting point before committing to a full catalog integration.
For many tools, you'll end up using both: the integration models the data you care about governing, while the MCP connector gives AI access to the tool's full surface area.