Adding a connector

Extending Glide with a new vendor connector is a five-step partner-PR flow. The full source of truth is CONTRIBUTING.md; this page summarizes the connector-specific path.

Trust tiers

Tier	When
`community`	Any first PR. Off by default; requires `GLIDE_ALLOW_COMMUNITY_CONNECTORS=true` + a red admin banner. Open contribution; no signed agreement required.
`verified`	Reviewed against the Verified-tier checklist + signed Trusted Partner Agreement. Ships enabled with per-tenant opt-in. Tier promotion is a separate PR.
`core`	Glide-maintained reference implementations. Tier promotion requires CODEOWNERS approval.

Five-step flow

Open a `New connector` issue first

Use the new-connector issue template so we can flag any compliance / regulatory concerns before you write code. Include vendor name, slug, capabilities, regions, regulatory posture, and rationale.

Read the `_base/` interfaces

Capability contracts live at packages/connectors/_base/src/capabilities/. Pick the subset your vendor implements:

orchestration — fiat ↔ crypto conversion.
kyc — identity verification.
card — card issuance.
screening — sanctions / AML lookup.
chain-receipt — on-chain confirmation reads.
balance — multi-chain balance reads.
auth — token verification.
banking — direct bank-rail (ACH / wire / SWIFT).
qr-gateway — QR-code merchant payments.
And 5 more (oauth-authorization-server, attestation, merkle-anchor, timelock-module, recovery).

Scaffold the package

packages/connectors/<slug>/
├── package.json
├── tsconfig.json
├── eslint.config.mjs
├── icon.svg
├── README.md
├── COMPLIANCE.md
├── DISCLAIMER.md (required if vendor ToS is unclear on adapter redistribution)
├── src/
│   ├── manifest.ts        // ConnectorManifest (Zod-validated)
│   ├── credentials.ts     // Zod schema for env keys
│   ├── legacy.ts          // adapter implementation
│   └── __tests__/
│       └── contract.test.ts

Or use the CLI:

glide partner submit ./my-connector --type=connector

Write the contract test

Extend ContractTestSuite from @repo/connectors-base:

import { ContractTestSuite } from '@repo/connectors-base';
import { manifest } from '../manifest';
import { MyVendorAdapter } from '../legacy';

class MyVendorSuite extends ContractTestSuite {
  readonly manifest = manifest;
  readonly runtime = {
    orchestration: new MyVendorAdapter(),
  };
}

The test asserts manifest validity + capability presence + egress-host invariant (every host the connector touches must appear in manifest.egressHosts).

Submit the PR

All eight CI gates must pass:

DCO sign-off check.
Signed-commits check (Verified tier and above).
Manifest schema validation.
Contract-test runner.
License-compat scan (M5.5+).
Supply-chain scans (Snyk + Socket — M5.5+).
Egress-host lint via ts-morph (M5.5+).
Compliance review (counsel sign-off for verified-tier promotions).

See License compatibility for the matrix.

Review SLA

Community-tier: 5 business days.
Verified-tier promotion: 10 business days (includes Trusted Partner Agreement review).

Reading list

Connector catalog — every connector currently in the repo.
License compatibility — accept / warn / block matrix.
Threat model — T7 (malicious connector PR).

Connectors Agent skills

Get started

Concepts

Packages

Connectors

Agent skills

Headless MCP

Security

Standards

Legal

Adding a connector

Trust tiers

Five-step flow

Review SLA

Reading list

​Trust tiers

​Five-step flow

​Review SLA

​Reading list

Trust tiers

Five-step flow

Review SLA

Reading list