Skip to content
Zep

Connecting your tools

Zep is useful once it’s connected to the services you actually work in. The first-run onboarding flow walks you through this, but you can always redo these steps from Settings in the UI.

Slack

Zep talks to Slack via the Anthropic MCP proxy. No bot tokens, no custom app.

  1. Open Settings → Integrations → Slack.
  2. Click Connect Slack. A browser tab opens to Slack’s OAuth page.
  3. Approve. You’ll be redirected back to Zep.

Zep can now pull thread context when analyzing DAG failures or merge requests.

GitLab

  1. Open Settings → Integrations → GitLab.
  2. Enter your GitLab host (e.g. gitlab.com or your self-hosted URL).
  3. Click Connect. You’ll be taken through OAuth.

Airflow

Airflow is read-only and uses a service account.

  1. Open Settings → Integrations → Airflow.
  2. Enter the base URL (e.g. https://airflow.example.com).
  3. Paste a username + app password for a read-only account.

Zep validates the connection on save. If it fails, check the URL and credentials; see Troubleshooting.

Claude CLI

Zep uses your installed Claude CLI for analysis. If you’ve already run claude auth, you’re done. Otherwise:

Terminal window
claude auth

Zep picks up the credentials from your home directory automatically.