--- title: "Integrations · Frazer" description: "215 integrations in one catalog. An admin connects each one once for the organization; projects, devboxes, agents and knowledge bases use it through grants, and every page says what leaves Frazer." url: https://frazer.ai/integrations index: https://frazer.ai/llms.txt tokens: 7922 --- > For agents: every page on frazer.ai is indexed at https://frazer.ai/llms.txt. # Integrations · Frazer **Integrations** frazer.ai # Connect once. Use it everywhere, with grants. 215 integrations in one catalog, from source control and identity to model providers and agent tools. An admin connects each one once for the organization; projects, devboxes, agents and knowledge bases use it through grants. Credentials stay in Frazer Secrets, and every page says what leaves Frazer. [Browse the catalog](#catalog) [Request an integration](#request) 00 · The catalog Fig. 1 · catalog UI, demo organization ## The catalog Search the catalog ### Featured curated, not paid - **GitHub** By Frazer Environments, builds on push, Reviewer, GitHub runners; MCP tools for agents. installed MCP - **Slack** By Frazer Alerts, approval links, agent channels, Knowledge source. installed MCP - **OVHcloud** By Frazer Bring servers from your account with their private network. BYO servers - **Anthropic** By Frazer LLM gateway upstream, Messages passed through natively. installed upstream - **Hugging Face** By Frazer Model and dataset imports, gated models with your access. upstream - **Okta** By Frazer SSO and SCIM; groups follow the directory. identity - **Linear** By Frazer Issues for agents and incidents; MCP server through your connection. MCP - **Google Artifact Registry** By Frazer Import images into Frazer Registry in a migration window. import - **Datadog** By Frazer Export metrics, logs and traces; Frazer keeps the original. export ### Agent tools (MCP) 14 · read-only by default - **Frazer MCP server** By Frazer Frazer’s own tools for any MCP client, scoped tokens. MCP - **Context7** By partner · verified before listing Library documentation for coding agents. MCP - **Custom remote MCP server** Yours Any Streamable HTTP server by URL; scanned before it is allowed. MCP ### All integrations - **GitHub** By Frazer Environments, builds on push, Reviewer, GitHub runners; MCP tools for agents. installed MCP - **GitHub Enterprise Server** By Frazer The five Frazer GitHub Apps, registered from a manifest on your server and reached over Frazer Link or Frazer Access. - **GitLab (SaaS and self-managed)** By Frazer Environments from GitLab repositories, Knowledge source, push events. - **Bitbucket Cloud** By Frazer Environments and builds on push. - **Gitea and Forgejo** By Frazer Environments from self-hosted Git. - **Azure DevOps Repos** By Frazer Environments from Azure Repos. - **GitHub Actions** By Frazer Push signed images to Frazer Registry, write digests, run frazer with no stored key. - **GitLab CI** By Frazer Push signed images to Frazer Registry, write digests, run frazer with no stored key. - **Buildkite** By Frazer Push signed images to Frazer Registry, write digests, run frazer with no stored key. - **CircleCI** By Frazer Push signed images to Frazer Registry, write digests, run frazer with no stored key. - **Bitbucket Pipelines** By Frazer Push signed images to Frazer Registry, write digests, run frazer with no stored key. - **Jenkins** By Frazer Build, push and deploy steps. - **Azure Pipelines** By Frazer Build, push and deploy steps. - **Argo Workflows** By Frazer Pipelines in the project's cluster (installed through the cluster's GitOps) call Frazer as the cluster. - **Tekton** By Frazer Pipelines in the project's cluster (installed through the cluster's GitOps) call Frazer as the cluster. - **Renovate** By Frazer Reads tags in Frazer Registry to update digests in environment repositories. - **Google (sign-in)** By Frazer Sign in with Google. identity - **GitHub (identity link)** By Frazer Link a person's GitHub login for "on behalf of @user" attribution and review assignment. identity - **Google Workspace** By Frazer Org SSO; groups synced into Frazer groups. identity - **Microsoft Entra ID** By Frazer SSO and SCIM provisioning. identity - **Okta** By Frazer SSO and SCIM; groups follow the directory. identity - **JumpCloud** By Frazer SSO and SCIM. identity - **OneLogin** By Frazer SSO and SCIM. identity - **Ping Identity** By Frazer SSO. identity - **Any SAML 2.0 provider** By Frazer SSO through the Ory Polis sidecar. identity - **Any OIDC provider** By Frazer SSO for Keycloak, Authentik, Zitadel and others. identity - **SCIM 2.0** By Frazer Provision people and groups; deprovision revokes that org's sessions and tokens. identity - **Email** By Frazer Notification channel and every system email; needs no integration. - **Slack** By Frazer Alerts, approval links, agent channels, Knowledge source. installed MCP - **Microsoft Teams** By Frazer Notifications, and approvals from the Frazer Teams app. - **Discord** By Frazer Notifications. - **Google Chat** By Frazer Notifications. - **Mattermost** By Frazer Notifications. - **Telegram** By Frazer Chat with the agent on your devbox through the box’s gateway. - **PagerDuty** By Frazer Page on incidents; acknowledge and resolve stay in sync. - **Opsgenie** By Frazer Page on incidents, only until Opsgenie shuts down on 2027-04-05; PagerDuty is the lasting choice. - **Jira Service Management** By Frazer Alerts and on-call. - **incident.io** By Frazer Frazer alerts as an alert source; incident links both ways. - **Rootly** By Frazer Alert source. - **FireHydrant** By Frazer Alert source. - **Grafana IRM** By Frazer Alert source for teams already on Grafana Cloud IRM. - **SMS and voice** By Frazer Paging without an on-call tool. - **Linear** By Frazer Issues for agents and incidents; MCP server through your connection. MCP - **Jira** By Frazer Issues from incidents, findings and reviews; agent sessions from issues; Knowledge source; MCP tools. MCP - **GitHub Issues** By Frazer Issues from findings and incidents through the Frazer App. - **GitLab Issues** By Frazer Issues through the GitLab connection. - **Notion** By Frazer Knowledge source; tasks in a Notion database; MCP tools. MCP - **Asana** By Frazer Tasks from incidents and findings. - **ClickUp** By Frazer Tasks from incidents and findings. - **Shortcut** By Frazer Stories from incidents and findings. - **monday.com** By Frazer Items from incidents and findings. - **OpenTelemetry (OTLP)** By Frazer Export a project's metrics, logs and traces to any OTLP endpoint. export - **Prometheus remote write** By Frazer Export metrics to your Prometheus-compatible store (Mimir, Thanos, VictoriaMetrics). export - **Grafana Cloud** By Frazer Export metrics, logs and traces over OTLP. export - **Datadog** By Frazer Export metrics, logs and traces; Frazer keeps the original. export - **New Relic** By Frazer Export over OTLP. export - **Honeycomb** By Frazer Export traces and logs over OTLP. export - **Sentry** By Frazer Errors linked to services, release markers on rollout, DSN bound as a secret; MCP tools. MCP export - **Loki** By Frazer Export logs to your Loki. export - **Elastic** By Frazer Export logs to Elasticsearch or Elastic Cloud. export - **Splunk (HEC)** By Frazer Export logs through the HTTP Event Collector. export - **Log archive to a bucket** By Frazer Long-term log archive in your S3, GCS or Azure Blob. export - **Grafana dashboards** By Frazer Import dashboard JSON into the project's dashboards. import - **Prometheus rules** By Frazer Turn alerting rules into Frazer alert policies. import - **Google Cloud Monitoring** By Frazer One-time import of uptime checks and alert policies during a migration. import - **Splunk (SIEM)** By Frazer Findings, threats and the audit log as OCSF over HEC. export - **Microsoft Sentinel** By Frazer Findings, threats and the audit log as OCSF, through the Logs Ingestion API. export - **Google Security Operations** By Frazer Findings, threats and the audit log as OCSF, through its ingestion API. export - **Panther** By Frazer Findings, threats and the audit log as OCSF, as an HTTP log source. export - **Elastic Security** By Frazer Findings, threats and the audit log as OCSF, into Elasticsearch. export - **Sumo Logic** By Frazer Findings, threats and the audit log as OCSF, to an HTTP source. export - **Wazuh** By Frazer Findings, threats and the audit log as OCSF, for self-hosted SIEM. export - **OCSF webhook** By Frazer Any SIEM: findings and audit events as signed OCSF JSON. export - **Vanta** By Frazer Pulls control evidence from a read-only service account (compliance:read). - **Drata** By Frazer Pulls control evidence from a read-only service account. - **Secureframe** By Frazer Pulls control evidence from a read-only service account. - **Snyk** By Frazer Snyk issues for images and repositories shown in Findings. - **Socket** By Frazer Supply-chain alerts on dependencies shown in Findings. - **GitHub code scanning and Dependabot** By Frazer Alerts shown in Findings through Frazer Reader. - **Wiz** By partner · verified before listing Inventory and findings to Wiz through Wiz's own integration program. - **CrowdStrike Falcon** By Frazer The Falcon sensor allowed on BYO servers by profile; detections shown in Threats. - **Docker Hub** By Frazer Pull-through cache in Frazer Registry; an org token lifts pull limits. upstream - **GitHub Container Registry** By Frazer Pull-through cache in Frazer Registry. upstream - **Quay.io** By Frazer Pull-through cache in Frazer Registry. upstream - **Public registries (registry.k8s.io, mcr.microsoft.com, public.ecr.aws)** By Frazer Pull-through cache in Frazer Registry. upstream - **Helm repositories and Artifact Hub** By Frazer Charts proxied and stored as OCI. upstream - **NVIDIA NGC** By Frazer Pull from nvcr.io under your license; NIM only with NVIDIA AI Enterprise. upstream - **Google Artifact Registry** By Frazer Import images into Frazer Registry in a migration window. import - **Amazon ECR** By Frazer Replicate repositories into Frazer Registry once, or for a migration window. import - **Azure Container Registry** By Frazer Replicate repositories into Frazer Registry once, or for a migration window. import - **GitLab Container Registry** By Frazer Replicate repositories into Frazer Registry once, or for a migration window. import - **Harbor** By Frazer Replication from another Harbor. import - **JFrog Artifactory** By Frazer Replicate repositories into Frazer Registry once, or for a migration window. import - **Google Secret Manager** By Frazer Import into Frazer Secrets, once or synced during a migration window. import - **AWS Secrets Manager** By Frazer Import into Frazer Secrets, once or synced during a migration window. import - **AWS Systems Manager Parameter Store** By Frazer Import into Frazer Secrets, once or synced during a migration window. import - **Azure Key Vault** By Frazer Import into Frazer Secrets, once or synced during a migration window. import - **HashiCorp Vault and OpenBao** By Frazer Import into Frazer Secrets from KV v1 and v2, once or synced during a migration window. import - **1Password** By Frazer Import chosen vaults into Frazer Secrets, once or synced during a migration window. import - **Doppler** By Frazer Import into Frazer Secrets per config, once or synced during a migration window. import - **Infisical** By Frazer Import into Frazer Secrets, once or synced during a migration window. import - **Kubernetes Secrets (attached cluster)** By Frazer Import from an attached cluster. import - **.env file** By Frazer Upload, values go straight to Frazer Secrets. import - **Frazer DNS** By Frazer Delegate a subdomain and Frazer manages records and certificates. - **Cloudflare DNS** By Frazer DNS records and certificate challenges in one zone. DNS - **Amazon Route 53** By Frazer DNS records and certificate challenges in one zone. DNS - **Google Cloud DNS** By Frazer DNS records and certificate challenges in one zone. DNS - **Azure DNS** By Frazer DNS records and certificate challenges in one zone. DNS - **DigitalOcean DNS** By Frazer DNS records and certificate challenges in one zone. DNS - **OVHcloud DNS** By Frazer DNS records and certificate challenges in one zone, through a webhook. DNS - **RFC 2136 (BIND, PowerDNS, Knot)** By Frazer DNS records and certificate challenges in one zone. DNS - **Akamai Edge DNS** By Frazer DNS records and certificate challenges in one zone. DNS - **NS1** By Frazer DNS records and certificate challenges in one zone. DNS - **Other DNS providers** By Frazer DNS records and certificate challenges in one zone, where the cluster's DNS and certificate controllers support the provider. DNS - **Cloudflare** By Frazer Purge cache on rollout; Cloudflare ranges into firewall policies; authenticated origin pulls. - **Fastly** By Frazer Purge on rollout; origin allowlist. - **Bunny.net** By Frazer Purge on rollout; pull zone origin. - **Akamai** By Frazer Purge on rollout. - **OVHcloud** By Frazer Bring servers from your account with their private network. BYO servers - **Hetzner** By Frazer Provider account: rescue boot and install. BYO servers - **Latitude.sh** By Frazer Provider account. BYO servers - **Vultr bare metal** By Frazer Provider account. BYO servers - **Scaleway Elastic Metal** By Frazer Provider account. BYO servers - **Any Linux server** By Frazer Install command, agent joins. BYO servers - **AWS EC2 and bare metal** By Frazer frazer servers add, or the install command in cloud-init, on instances you run. BYO servers - **Google Compute Engine** By Frazer frazer servers add, or the install command in cloud-init, on instances you run. BYO servers - **Azure Virtual Machines** By Frazer frazer servers add, or the install command in cloud-init, on instances you run. BYO servers - **Boot image (ISO, iPXE, qcow2)** By Frazer Clean install by Frazer. BYO servers - **Redfish BMC** By Frazer Zero-touch through a Site Gateway. BYO servers - **Attached Kubernetes clusters** By Frazer Any CNCF cluster (EKS, GKE, AKS, k3s, RKE2, OpenShift) observed, connected or managed. - **Terraform** By Frazer Frazer provider frazer-ai/frazer. - **OpenTofu** By Frazer The same provider in the OpenTofu registry. - **Pulumi** By Frazer Through Pulumi's Terraform bridge. - **Backstage** By Frazer Frazer plugin: catalog entities, links, rollouts. - **Port** By Frazer Ocean integration that syncs Frazer resources. - **S3-compatible storage (S3, R2, B2, Wasabi, MinIO)** By Frazer Import into Frazer Storage and AI volumes; copies of backups out. import export - **Google Cloud Storage** By Frazer Migration import into Frazer Storage. import - **Azure Blob Storage** By Frazer Migration import into Frazer Storage. import - **BigQuery (billing export)** By Frazer FOCUS billing export landed in your bucket for loading. export - **Snowflake** By Frazer Load the FOCUS export and usage from the export bucket. export - **Fivetran** By Frazer Reads Frazer managed Postgres: replication user, private endpoint or IP allowlist. - **Airbyte** By Frazer Reads Frazer managed Postgres: replication user, private endpoint or IP allowlist; or run Airbyte on Frazer. - **Kafka and Confluent Cloud** By Frazer Event and log export destination. export - **Anthropic** By Frazer LLM gateway upstream, Messages passed through natively. installed upstream - **OpenAI** By Frazer LLM gateway upstream. upstream - **Google Gemini API** By Frazer LLM gateway upstream (OpenAI-compatible). upstream - **Mistral** By Frazer LLM gateway upstream. upstream - **DeepSeek** By Frazer LLM gateway upstream. upstream - **Groq** By Frazer LLM gateway upstream. upstream - **Together AI** By Frazer LLM gateway upstream (OpenAI-compatible). upstream - **Fireworks AI** By Frazer LLM gateway upstream (OpenAI-compatible). upstream - **xAI** By Frazer LLM gateway upstream (OpenAI-compatible). upstream - **OpenRouter** By Frazer LLM gateway upstream: the org's key or Frazer's account. upstream - **Any OpenAI-compatible URL** By Frazer LLM gateway upstream. upstream - **Cohere** By Frazer Embeddings and rerank for Knowledge. - **Voyage AI** By Frazer Embeddings and rerank for Knowledge. - **Amazon Bedrock** By Frazer LLM gateway upstream on your AWS account. upstream - **Google Vertex AI** By Frazer LLM gateway upstream on your Google account. upstream - **Azure OpenAI** By Frazer LLM gateway upstream on your Azure tenant. upstream - **Hugging Face** By Frazer Model and dataset imports, gated models with your access. upstream - **Weights & Biases** By Frazer Experiment tracking: key injected into jobs that opt in. - **MLflow (external)** By Frazer Tracking URI for jobs, or a managed MLflow per project. - **Langfuse** By Frazer OTLP traces from model endpoints and the gateway. export - **LangSmith** By Frazer OTLP traces from model endpoints and the gateway. export - **Arize Phoenix** By Frazer OTLP traces from model endpoints and the gateway. export - **Kaggle** By Frazer Models and datasets by handle. - **Civitai** By Frazer Diffusion checkpoints and LoRAs, safetensors only. - **Ollama and GGUF** By Frazer Small GGUF models, served by Frazer’s inference engine. - **Google Drive** By Frazer Files and Docs into Knowledge with sharing mapped. - **Website** By Frazer Pages from a sitemap or crawl. - **Upload and push API** By Frazer Documents pushed with their principals. - **Confluence** By Frazer Pages with space permissions. MCP - **SharePoint and OneDrive** By Frazer Files with item permissions. - **Gmail** By Frazer Threads with mailbox permissions. - **Databases (Postgres)** By Frazer Rows rendered by a template from a saved query. - **Zendesk** By Frazer Tickets and help-center articles. - **Intercom** By Frazer Conversations and articles. - **Gong** By Frazer Call transcripts. - **Salesforce** By Frazer Accounts, cases and knowledge articles. - **HubSpot** By Frazer CRM notes and knowledge base. - **Dropbox and Box** By Frazer Files with sharing mapped. - **Frazer MCP server** By Frazer Frazer’s own tools for any MCP client, scoped tokens. MCP - **Frazer Knowledge MCP** By Frazer One MCP server per knowledge base, with the person's scopes. MCP - **GitHub MCP server** By partner · verified before listing GitHub's remote MCP server, token minted from the GitHub connection. MCP - **Linear MCP server** By partner · verified before listing Linear's remote MCP server. MCP - **Notion MCP server** By partner · verified before listing Notion's remote MCP server. MCP - **Sentry MCP server** By partner · verified before listing Sentry's remote MCP server. MCP - **Atlassian MCP server** By partner · verified before listing Jira and Confluence tools. MCP - **Stripe MCP server** By partner · verified before listing For teams building on their own Stripe account. MCP - **Cloudflare MCP servers** By partner · verified before listing For teams that run Cloudflare in front of Frazer. MCP - **Context7** By partner · verified before listing Library documentation for coding agents. MCP - **Composio** By partner · verified before listing Aggregator: toolkits through your own Composio account. MCP - **Zapier MCP** By partner · verified before listing Aggregator: your Zapier actions as tools. MCP - **Pipedream Connect** By partner · verified before listing Aggregator: managed-auth tools through your Pipedream project. MCP - **Custom remote MCP server** Yours Any Streamable HTTP server by URL; scanned before it is allowed. MCP - **Frazer app** By Frazer Frazer’s own app: sessions, boxes, deploys, models. - **Frazer extension for VS Code** By Frazer Boxes, sessions, Plans and chat in VS Code and the editors built on it. - **Other VS Code-based editors** By Frazer Open boxes over remote-SSH with the Frazer extension from Open VSX. - **JetBrains** By Frazer Toolbox remote development; the Frazer plugin for JetBrains Toolbox lists your boxes. - **Zed** By Frazer Zed's headless server on the box over SSH. - **Hermes Desktop and TUI** By Frazer Hermes connects to the box’s gateway through Frazer’s plugin. - **Claude Code** By Frazer Managed settings from provisioning profiles; models through the LLM gateway. - **Codex CLI** By Frazer Provider set to the LLM gateway by profile. - **Terminal and frazer CLI** By Frazer frazer devboxes ssh, device-flow login. - **Stripe** By Frazer Frazer's own payment processor: cards, ACH, invoices, tax. Not a customer connection. - **Billing export (FOCUS)** By Frazer Hourly cost files to your bucket (S3, GCS, Azure Blob, Frazer Storage). export - **Partner resources on the Frazer bill** By Frazer Marketplace products billed through the billing account. - **Frazer status pages** By Frazer Built-in public or private status pages. - **Atlassian Statuspage** By Frazer Component status from Frazer incidents. - **Instatus** By Frazer Component status from Frazer incidents. - **Better Stack** By Frazer Component status from Frazer incidents. - **Webhooks** By Frazer Frazer events to any HTTPS endpoint, signed (Standard Webhooks). - **Zapier** By Frazer A Frazer app on Zapier: triggers from Frazer events, actions on the API. - **Make** By Frazer A Frazer app on Make: triggers from Frazer events, actions on the API. - **n8n** By Frazer A Frazer node for n8n: triggers from Frazer events, actions on the API. No entry matches. [Request an integration](#request) Fig. 1: the integrations catalog, product UI with a demo organization (the installed marks are its own). A **Who built it, on every tile** By Frazer, by a verified partner, or yours. Featured is chosen by us, never bought. B **A section for agents** Every MCP server is verified before listing and read-only until a grant says otherwise. C **An exact count** 215 entries in 21 categories, from the same registry as the console. 01 · How outside services fit Fig. 2 ## Six roles, written down. Nothing else runs outside. Your images, secrets, logs and metrics live on Frazer. Other services connect in one of six roles, and the catalog shows which. Model providers are the one deliberate exception: requests leave Frazer through the LLM gateway, labeled with their data policy. - Frazer: registry, secrets and observability, the only runtime backends. - Import source: read once, or sync for 90 days (artifact registries, secret stores, buckets). - Upstream: pull-through; Frazer keeps the copy (container hubs, Hugging Face, Helm repos). - Your DNS: the DNS controller writes one zone (Cloudflare, Route 53, Cloud DNS, OVHcloud). - Identity provider: people sign in, groups sync (Google Workspace, Entra ID, Okta, SAML, OIDC). - Export destination: a copy goes out, the original stays (OTLP, Datadog, Splunk, FOCUS billing files). - Your servers: machines join Frazer (OVHcloud, Hetzner, Linux in your clouds). - Six roles: an outside service is never a runtime dependency of your workloads. **Fig. 2** The roles an integration can play 02 · Every integration page has the same parts Fig. 3 ## What it does, what it needs, and what leaves Frazer. Slack Alerts, approval links, agent channels and a Knowledge source ### What Frazer does with it Sends alerts and incident updates to the channels you pick, carries agent conversations through Frazer’s channel gateway, and indexes public channels into Knowledge with Slack’s own permissions. ### Capabilities, and the scopes they need notify.send Post alerts and agent messages to chosen channels chat:write channels.read List channels to pick from channels:read knowledge.read Index public channels into Knowledge channels:history agents.channel Talk to agents in threads, sender verified app\_mentions:read ### Data flow **Leaves Frazer** Alert titles, states and links; agent replies. Never secret values or log bodies. **Frazer stores** Channel IDs, the bot token in Frazer Secrets, message metadata for 30 days; indexed text only if Knowledge is granted. Publisher By Frazer Categories Communication · Knowledge sources Auth OAuth app, bot token rotated every 12 h Scope Organization connection, granted per project Works with agents Yes, through Frazer’s channel gateway Health Healthy · Expiring · Needs re-auth · Degraded · Error · Paused Docs /docs/integrations/slack **Fig. 3** An integration page · Slack as the example fields from the catalog registry 03 · Governed connections ## One place to see, rotate and revoke every outside credential. - ### Connect once An admin installs it for the organization, with the organization’s app or bot identity, not a person’s account. - ### Grant, narrowly Projects, devboxes, agents and knowledge bases get capabilities, not tokens; more scope needs a new consent. - ### No stored credentials outside Boxes and agents get tokens of an hour or less from the broker, or none at all: the gateway injects them. - ### Health you can see Hourly checks, six states, emails 30, 7 and 1 days before anything expires. - ### Owned, not orphaned Every connection has an owner; it survives the installer leaving, and ownership transfers with a plan. - ### Uninstall with a preview See every project, agent and dashboard that uses it before you remove it. 04 · Events out ## Every change, signed and delivered. About 60 event types across servers, clusters, deploys, data, AI, agents, security, access and billing, signed with Standard Webhooks and shaped like CloudEvents. Events carry identifiers and states, never secret values. event.json { "specversion": "1.0", "type": "ai.frazer.releases.rollout.v1.succeeded", "source": "projects/acme-production", "subject": "environments/production/apps/checkout-api", "id": "evt\_01J9W3…", "time": "2026-10-02T10:52:11Z", "data": { "revision": "checkout-api-00042", "image": "sha256:4e1c…", "by": "users/noah" } } Delivery POST https://hooks.acme.example/frazer webhook-id: msg\_2mQ8… webhook-timestamp: 1759402331 webhook-signature: v1,K5oZfzN95Z9UVu1EsfQmfVNQhnkZ2pj9o9NDDsrqsHU= retries for about 3 days · delivery log 30 days · redeliver failed since T $ frazer webhooks listen --forward-to localhost:8080 $ frazer webhooks trigger ai.frazer.releases.rollout.v1.succeeded 05 · Build on Frazer ## Missing something? Ask for it, or build it. **API and SDKs** Go, TypeScript and Python from one contract; every console action is an API call. **OpenTofu and Terraform** A provider for every Frazer resource, with the same plans. **MCP** mcp.frazer.ai for any agent, read-only by default, scoped tokens. **Frazer OAuth apps** Build a product on Frazer: your app asks for scopes, the org approves. **Verified publishers** List your integration with a “By” line people can trust. ### Request an integration Tell us the service and what Frazer should do with it. A request goes by email to support@frazer.ai. Service name What should Frazer do with it? [Send request by email](mailto:support@frazer.ai?subject=Integration%20request) ## 215 integrations, one set of rules. Connect what you already use. [Browse the catalog](#catalog) [Read the docs](https://frazer.ai/docs)