Skip to main content

​
Integrations

Path: Headmaster’s Library → Integrations (PIN-protected) Integrations are external services the agent can reach during a conversation. Unlike MCP servers (which are tool-level connections), integrations are service-level connections — the agent uses them to read or write data from a specific service. Examples: A file storage bucket (S3, Google Drive), a calendar (Google Calendar, Outlook), an issue tracker (Jira, Linear), a database (Postgres, BigQuery).

​
Adding an integration

1

Open Integrations

Go to Settings → Headmaster’s Library → Integrations and click Add integration.
2

Pick the type

Select from: Storage, Calendar, Issue Tracker, Database, Custom.
3

Fill in credentials

Enter the API key, OAuth token, or connection string — depends on the type.
4

Test and save

Click Test connection, then Save. The integration is immediately available to the agent and appears in the integrations list with a status indicator.

​
Credentials

Credentials are stored locally, encrypted at rest. They are not synced to the cloud. If you move to a new machine, you have to add the integrations again.

​
Removing an integration

Click Remove on an integration card. The agent loses access to that service in its next turn. Existing conversation transcripts that referenced the integration are not edited.

​
Troubleshooting

If the agent reports it can’t reach an integration, open the integration’s card. It shows:
  • The last error from the service.
  • A Test connection button.
  • The timestamp of the last successful connection.
The most common cause is an expired or rotated credential. Update the credential and test again.

Connections (MCP)

Tool-level connections via the Model Context Protocol.

Settings Overview

Map of all settings areas and what’s in each.