Skip to main content

Connectors

The MCP connectors that ship, all disabled until configured, and what each needs to turn on.

On this page

TL;DR: Connectors are MCP servers in services/mcp/. Everything except github and systemprompt ships with enabled: false. They have been proven against stand-ins only; live sign-in needs Astound's credentials.

Server File Needs Runbook
salesforce services/mcp/salesforce.yaml Packaged External Client App, secrets salesforce_mcp_client_id / salesforce_mcp_client_secret, an org entry in services/config/salesforce-orgs.yaml docs/runbooks/connector-salesforce.md
atlassian services/mcp/atlassian.yaml No client secret (dynamic registration); jira_webhook_secret for Jira events docs/runbooks/connector-atlassian.md
google_workspace, google_drive services/mcp/google_*.yaml Google OAuth client ids and secrets, callbacks registered docs/runbooks/connector-google.md
clickhouse services/mcp/clickhouse.yaml A ClickHouse the export job writes to; admin only, read-only docs/runbooks/clickhouse-mcp.md
github services/mcp/github.yaml On; a GitHub App installation attached to the workflow service account docs/CONFIGURED-CONNECTORS.md

Turning one on

  1. Set its secrets with systemprompt admin config secret set <name> "<value>".
  2. Set enabled: true in its YAML.
  3. Grant it in services/access-control/rules.yaml and apply through /admin/sync.
  4. Restart. Users connect on Connectors.

Jira webhooks post to /api/public/workflows/events/jira.