Skip to content
xovris.ai · 5 of 5 fine · 2 Oct, 01:49 UTC
Join early access
Menu

Integrations

Xovris connects to 14,525 services

Whoever you are and whatever you run – a shop, a school, a family’s home network or a developer’s whole stack. Search yours and see whether it is ready today.

services listed
14,525
Every service Xovris can name, across 19 kinds of tool.
install-tested
1,662
Installed from the official release, with its test passed in the last 60 days.
ready-made
25
Set up in one command or one sign-in, then proven with a real event.

The whole catalogue: each square is about 100 services

  • 1,662 Install-tested
  • 12,366 AI tool servers that answered
  • 497 Listed, built when you ask
How these are counted

Counted from the catalogue itself when this page was built, on 1 October 2026 – nothing here is typed by hand. A service counts as install-tested only when its connector was installed from the official release and its test passed in the last 60 days. An AI tool server counts only when it answered with its list of tools in the last 60 days. A service on request is listed, and Xovris builds and tests it before anyone relies on it.

You probably use some of these

A few of the 14,525, each with its own mark. Press one to see its state.

Every kind of tool, not only developer tools

Each tile is sized by how many services it holds. Press one to see every service in it.

Search 14,525 listed services

Every service shows its true state. Supported means Xovris installed its connector from the official release and the test passed. On request means it is listed, and Xovris builds and tests it when you ask.

  • GitHubDeveloper toolsSupported
  • Kafka MetricsMonitoringSupported
  • ElasticsearchMonitoringSupported
  • MongoDBDeveloper toolsSupported
  • MySQLDeveloper toolsSupported
  • RabbitMQProductivitySupported
  • SlackCommunicationSupported
  • TwitterCommunicationSupported
  • Amazon S3Developer toolsSupported
  • AWS CloudWatchMonitoringSupported
  • BirdMarketingSupported
  • ClickHouseMonitoringSupported
  • Google SheetsProductivitySupported
  • HubSpotSales and CRMSupported
  • Jira CloudProductivitySupported
  • MailgunMarketingSupported
  • MastodonCommunicationSupported
  • Microsoft SQL ServerDeveloper toolsSupported
  • OpenWeatherMapMonitoringSupported
  • PagerDutyDeveloper toolsSupported
  • PostmarkCommunicationSupported
  • PrometheusMonitoringSupported
  • PushbulletCommunicationSupported
  • RedditCommunicationSupported
  • RedisMonitoringSupported
  • RingCentralCommunicationSupported
  • SalesforceSales and CRMSupported
  • SendGridCommunicationSupported
  • SnowflakeDeveloper toolsSupported
  • SQLMonitoringSupported
  • TwilioCommunicationSupported
  • ZoomCommunicationSupported
  • ActiveCampaignMarketingSupported
  • Amazon SQSProductivitySupported
  • Apache Web ServerMonitoringSupported
  • AppriseData and analyticsSupported
  • Auth0Cloud inventorySupported
  • AWS HealthMonitoringSupported
  • Azure DevOpsDeveloper toolsSupported
  • Azure MonitorMonitoringSupported
  • Azure OpenAIProductivitySupported
  • BambooHRProductivitySupported
  • BlueskyCommunicationSupported
  • ConsulMonitoringSupported
  • CouchbaseProductivitySupported
  • CouchDBMonitoringSupported
  • DatadogDeveloper toolsSupported
  • DigitalOceanDeveloper toolsSupported

Showing the first 48. Type more of the name to see the rest.

Ready-made: one command or one sign-in

25 integrations Xovris built itself. Each says whether it is released, in beta or planned, when its install was last tested and exactly what it can touch.

  • Next.js

    Beta

    Errors, releases and readable stack traces from your Next.js app, installed by one command or a pull request Xovris opens.

    SDK, set up in one command

    No install test has run yet

    No access to your systems

  • React on Vite

    Beta

    Errors, releases and readable stack traces from your React on Vite app, installed by one command or a pull request Xovris opens.

    SDK, set up in one command

    No install test has run yet

    No access to your systems

  • Node.js (Express, Fastify)

    Beta

    Errors, releases and readable stack traces from your Node.js (Express, Fastify) app, installed by one command or a pull request Xovris opens.

    SDK, set up in one command

    No install test has run yet

    No access to your systems

  • Python (Django, FastAPI)

    Planned

    Planned after the JavaScript stacks. The wizard already recognises a Python project and says so, without changing anything.

    SDK, set up in one command

    No install test has run yet

    No access to your systems

  • GitHub

    Beta

    Xovris opens the setup change as one pull request on a new branch, after you agree to the exact words it shows you.

    Sign in with the provider

    No install test has run yet

    Can fix, within what you allow

  • Vercel

    Beta

    Writes the Xovris variables into each project and environment and reads them back; maps every deployment to its environment and release.

    Sign in with the provider

    No install test has run yet

    Can fix, within what you allow

  • Cloudflare DNS

    Beta

    Keeps every verified version of your DNS records and, under your standing policy, puts a changed record back - every other record left byte-identical.

    Sign in with the provider

    No install test has run yet

    Can fix, within what you allow

  • Email

    Beta

    Alerts by email from the first minute, with delivery read back from the provider rather than assumed.

    Built in · Xovris calls the tool

    No install test has run yet

    No access to your systems

  • Slack

    Beta

    Alerts in the Slack channel you choose; a test alert shows Slack's own acceptance, and a failing channel falls back to email.

    Sign in with the provider · Xovris calls the tool

    No install test has run yet

    Can fix, within what you allow

  • Webhooks

    Beta

    Signed alert payloads to any HTTPS endpoint you own, so any tool that accepts a webhook hears about an incident.

    Webhooks · Xovris calls the tool

    No install test has run yet

    No access to your systems

  • OpenTelemetry

    Beta

    Errors and traces from any OpenTelemetry SDK that exports OTLP over HTTP as JSON, whatever language your service is written in.

    OpenTelemetry · the tool calls Xovris

    No install test has run yet

    No access to your systems

  • Sentry

    Beta

    Runs side by side with it for as long as you like, or switches over - one error is never sent to Xovris twice.

    SDK, set up in one command

    No install test has run yet

    No access to your systems

  • Datadog

    Beta

    Leaves the existing agent in place and adds Xovris through OpenTelemetry instead of a second agent.

    SDK, set up in one command

    No install test has run yet

    No access to your systems

  • New Relic

    Beta

    Leaves the existing agent in place and adds Xovris through OpenTelemetry instead of a second agent.

    SDK, set up in one command

    No install test has run yet

    No access to your systems

  • Claude Code

    Beta

    Your coding agent installs and verifies Xovris through the Xovris MCP server, and asks you to approve the sign-in.

    MCP server · the tool calls Xovris

    No install test has run yet

    No access to your systems

  • Codex

    Beta

    Your coding agent installs and verifies Xovris through the Xovris MCP server, and asks you to approve the sign-in.

    MCP server · the tool calls Xovris

    No install test has run yet

    No access to your systems

  • Gemini CLI

    Beta

    Your coding agent installs and verifies Xovris through the Xovris MCP server, and asks you to approve the sign-in.

    MCP server · the tool calls Xovris

    No install test has run yet

    No access to your systems

  • GitHub Copilot CLI

    Beta

    Your coding agent installs and verifies Xovris through the Xovris MCP server, and asks you to approve the sign-in.

    MCP server · the tool calls Xovris

    No install test has run yet

    No access to your systems

  • VS Code

    Beta

    Your coding agent installs and verifies Xovris through the Xovris MCP server, and asks you to approve the sign-in.

    MCP server · the tool calls Xovris

    No install test has run yet

    No access to your systems

  • Cursor

    Beta

    Your coding agent installs and verifies Xovris through the Xovris MCP server, and asks you to approve the sign-in.

    MCP server · the tool calls Xovris

    No install test has run yet

    No access to your systems

  • LM Studio

    Beta

    Your coding agent installs and verifies Xovris through the Xovris MCP server, and asks you to approve the sign-in.

    MCP server · the tool calls Xovris

    No install test has run yet

    No access to your systems

  • Goose

    Beta

    Your coding agent installs and verifies Xovris through the Xovris MCP server, and asks you to approve the sign-in.

    MCP server · the tool calls Xovris

    No install test has run yet

    No access to your systems

  • Windsurf

    Beta

    Your coding agent installs and verifies Xovris through the Xovris MCP server, and asks you to approve the sign-in.

    MCP server · the tool calls Xovris

    No install test has run yet

    No access to your systems

  • ChatGPT

    Beta

    Your coding agent installs and verifies Xovris through the Xovris MCP server, and asks you to approve the sign-in.

    MCP server · the tool calls Xovris

    No install test has run yet

    No access to your systems

  • Claude

    Beta

    Your coding agent installs and verifies Xovris through the Xovris MCP server, and asks you to approve the sign-in.

    MCP server · the tool calls Xovris

    No install test has run yet

    No access to your systems

  • Any MCP client

    Beta

    Your coding agent installs and verifies Xovris through the Xovris MCP server, and asks you to approve the sign-in.

    MCP server · the tool calls Xovris

    No install test has run yet

    No access to your systems

Every way in

Ready-made, install-tested, OpenTelemetry, the provider’s own API, MCP or a supervised browser – each marked ready only when a stored record says it works today.

  1. Ready-made integrations

    Sign in with the provider and approve its consent screen. Xovris sets up the rest and proves the connection works.

    Ready25 ready to connect

    See each one
  2. Services Xovris has tested

    Each connector is installed from its official release and checked before it is listed as supported.

    Ready1662 services, last tested 1 October 2026

    Search them
  3. OpenTelemetry, from any language

    Send errors, traces, logs and metrics with the standard OpenTelemetry exporter your app may already use.

    ReadyBeta

  4. The provider's own API

    From the provider's published API description, Xovris builds the connection and proves it with a harmless read before it counts.

    PlannedPlanned

  5. The provider's MCP server

    Xovris signs in to the provider's MCP server the standard way. You approve its consent screen, and your keys never pass through the AI.

    PlannedPlanned

  6. A supervised browser

    For a console with no API, Xovris works in a recorded browser you can watch, and hands sign-in, payment and terms to you.

    PlannedPlanned

  7. Not listed? Ask for it

    Tell us the service. Xovris builds the connection and tests it before anyone relies on it.

    ReadyRequests go to [email protected].

    Ask for a connection
What makes a way ready

A way in is marked ready only when the record behind it exists: a built integration whose install test passed, a tested connector, or a service that answered a harmless read. The ones still being built say so.

AI tools, in both directions

Your AI coding tools can drive Xovris, and Xovris can see what they did – each direction with its own true state.

Xovris inside your AI tools

From the first release, Claude Code, Cursor and other MCP clients call Xovris’s MCP server to install it, check it and read your incidents – you approve the sign-in.

  • Claude Code – Beta
  • Codex – Beta
  • Gemini CLI – Beta
  • GitHub Copilot CLI – Beta
  • VS Code – Beta
  • Cursor – Beta
  • LM Studio – Beta
  • Goose – Beta
  • Windsurf – Beta
  • ChatGPT – Beta
  • Claude – Beta
  • Any MCP client – Beta
Set up from a coding agent

Your AI tools' actions, seen by Xovris

Planned

Xovris reading what your agents changed, so an incident can be traced to an agent’s edit. Planned.

A service with no tile yet

When this is built, Xovris will make the connection for you: it will find the provider’s own way in, ask your consent for each step, check the result and keep it as a recipe the next person can reuse.

Planned

Planned. It will run on the same runner as every repair – the same consent, policy check, before-and-after test and rollback.

How access is asked forOpen-source credits and licences