Connector catalogue

Every connector that ships in the Zeno dashboard today, generated from the runtime catalogue.

These are the connectors a fresh Zeno install offers under the dashboard's /connectors route. The list is generated from agent/connectors-catalog.json at docs build time, so it is always in lockstep with what an operator actually sees in their dashboard.

A connector is an MCP server the worker spawns on demand — see Connectors for the concept.

GitHub App

github-app

Multi-installation GitHub access via a GitHub App. One connector per installation.

Upstream docs ↗

GitHub Personal

github

GitHub access via a personal access token. Issues, PRs, repos, code search.

Upstream docs ↗

Klaviyo

klaviyo

Email/SMS marketing — campaigns, lists, segments, profiles, events.

Upstream docs ↗

Linear

linear

Issues, projects, cycles, docs, and team metadata.

Upstream docs ↗

MySQL

mysql

Read-only access to a MySQL database via the MySQL MCP server (@benborla29/mcp-server-mysql). Writes are gated behind upstream ALLOW_INSERT_OPERATION / ALLOW_UPDATE_OPERATION / ALLOW_DELETE_OPERATION env vars which this catalog never sets. One installation per database connection.

Upstream docs ↗

Postgres

postgres

Read-only access to a Postgres database via the Postgres MCP server (crystaldba/postgres-mcp). One installation per database URL.

Upstream docs ↗

Swarmia

swarmia

Engineering metrics — DORA, throughput, code review.

Upstream docs ↗

Sentry

sentry

Errors, releases, issues across your projects.

Upstream docs ↗