Skip to content

Search docs

Find pages, headings, and concepts. Press ⌘K or Ctrl+K to toggle.

Build your own

How custom connectors are registered.

Connectors are plain TypeScript modules in packages/web/lib/connectors/registry/. Each definition declares a slug, an auth type, and a list of operations whose execute functions call the upstream service.

For most users, the 541 built-in slugs cover the integrations they need. Adding a new connector is currently a code change to the platform.

If you need a service we don't have

  1. Open /[orgSlug]/connectors and confirm it isn't already registered under a different name.
  2. File a request — the connectors MCP and the connectors team track demand and prioritize new slugs.

Programmatic access

The HTTP API exposes connectors at /api/v1/connectors. See API access for authentication and rate limits.

Operating notes

  • Connector packages are published as @hasna/connect-<name>. They are invoked through the platform runtime, not as direct CLIs.
  • Tool calls go through the standard agent tool path, so usage shows up in audit logs and (for paid models) in usage metering.