Stedia

Connectors

Connect a platform integration, publish a custom connector in Studio, or add a remote MCP server.

Open Connectors. The agent can only act where you have a connection.

  • GitHub
  • Linear
  • Gmail
  • Outlook
  • Google Drive
  • Shopify

Three tabs:

TabWhoWhat
CatalogEveryonePlatform connectors and published custom connectors
StudioAdminsImport OpenAPI and publish a custom connector
MCPAdminsAdd a remote MCP server as an org connector

The summary line counts connected connectors and active connections. Filter by status, category, or search.

Connect

Open the connector

Open a connector. Click Connect or Manage.

Choose who uses it

Choose Who uses this connection: Personal, or Organization (share with the org; may require admin).

Sign in

Choose How to sign in. Click Continue to the provider for OAuth, or Connect after you paste credentials.

If the browser blocks the OAuth window, allow popups and try again.

The detail panel lists version, an org enable toggle (admins), actions, and connections. Actions that write show Approval required. Those need a teammate to approve in chat or on a scheduled run unless you pre-authorize them on a job or turn on Auto-approve in a thread.

What you can connect

Platform connectors:

Custom:

Off for organization

A connector hidden from members stays that way until an admin enables it. On a self-hosted install, a missing catalog entry usually means the operator did not set that provider's env vars.

On this page