Supported Tools

Latchkey supports 25+ popular services with two levels of authentication:

• Browser authentication: Automated login via latchkey auth browser

• Manual authentication: Requires latchkey auth set or latchkey auth set-nocurl

Run latchkey services list to see all supported services on your system.

Current services

AWS

Manual only: latchkey auth set-nocurl aws <access-key-id> <secret-access-key>

Notes: Requires AWS access key and secret key. Latchkey handles request signing automatically.

Calendly

Manual only: latchkey auth set calendly -H "Authorization: Bearer <token>"

Coolify

Manual only: latchkey auth set coolify -H "Authorization: Bearer <token>"

Discord

• Browser: latchkey auth browser discord

• Manual: latchkey auth set discord -H "Authorization: Bot <token>"

Notes: Browser login extracts credentials from the user session, not a bot token.

Dropbox

• Browser: latchkey auth browser dropbox

• Manual: latchkey auth set dropbox -H "Authorization: Bearer <token>"

Figma

Manual only: latchkey auth set figma -H "Authorization: Bearer <token>"

GitHub

• Browser: latchkey auth browser github

• Manual: latchkey auth set github -H "Authorization: Bearer <token>"

Notes: Browser login creates a personal access token with broad permissions.

GitLab

Manual only: latchkey auth set gitlab -H "PRIVATE-TOKEN: <token>"

Google Analytics

• Browser: latchkey auth browser google-analytics

• Manual: latchkey auth set google-analytics -H "Authorization: Bearer <token>"

Notes: You may need to run latchkey auth browser-prepare google-analytics to create an OAuth client first.

Google Calendar

• Browser: latchkey auth browser google-calendar

• Manual: latchkey auth set google-calendar -H "Authorization: Bearer <token>"

Notes: You may need to run latchkey auth browser-prepare google-calendar to create an OAuth client first.

Google Directions

Manual only: latchkey auth set-nocurl google-directions <api-key>

Notes: The API key is added to requests automatically.

Google Docs

• Browser: latchkey auth browser google-docs

• Manual: latchkey auth set google-docs -H "Authorization: Bearer <token>"

Notes: You may need to run latchkey auth browser-prepare google-docs to create an OAuth client first.

Google Drive

• Browser: latchkey auth browser google-drive

• Manual: latchkey auth set google-drive -H "Authorization: Bearer <token>"

Notes: You may need to run latchkey auth browser-prepare google-drive to create an OAuth client first.

Google Gmail

• Browser: latchkey auth browser google-gmail

• Manual: latchkey auth set google-gmail -H "Authorization: Bearer <token>"

Notes: You may need to run latchkey auth browser-prepare google-gmail to create an OAuth client first.

Google People

• Browser: latchkey auth browser google-people

• Manual: latchkey auth set google-people -H "Authorization: Bearer <token>"

Notes: You may need to run latchkey auth browser-prepare google-people to create an OAuth client first.

Google Sheets

• Browser: latchkey auth browser google-sheets

• Manual: latchkey auth set google-sheets -H "Authorization: Bearer <token>"

Notes: You may need to run latchkey auth browser-prepare google-sheets to create an OAuth client first.

Linear

• Browser: latchkey auth browser linear

• Manual: latchkey auth set linear -H "Authorization: <token>"

Mailchimp

Manual only: latchkey auth set mailchimp -H "Authorization: Bearer <token>"

Notion

• Browser: latchkey auth browser notion

• Manual: latchkey auth set notion -H "Authorization: Bearer <token>"

Notes: Browser login requires the locale to be set to English. Access is limited to pages that existed when the login happened for the first time.

Sentry

Manual only: latchkey auth set sentry -H "Authorization: Bearer <token>"

Slack

• Browser: latchkey auth browser slack

• Manual: latchkey auth set slack -H "Authorization: Bearer xoxb-your-token"

Notes: Browser login extracts credentials from the user session, not a bot token.

Stripe

Manual only: latchkey auth set stripe -H "Authorization: Bearer <token>"

Telegram

Manual only: latchkey auth set-nocurl telegram <bot-token>

Notes: Requires a bot token. Latchkey injects the token into the URL path automatically.

Umami

Manual only: latchkey auth set umami -H "x-umami-api-key: <api-key>"

Yelp

Manual only: latchkey auth set yelp -H "Authorization: Bearer <token>"

Zoom

Manual only: latchkey auth set zoom -H "Authorization: Bearer <token>"

Checking service details

For up-to-date information about any service, run:

latchkey services info <service_name>

This shows

• API documentation links

• Current credential status (missing, invalid, or valid)

• Authentication requirements

• Service-specific notes and limitations

Request a new service

Don't see a service you need? You can do the following:

Add a service definition at runtime

In simple cases, you can use the latchkey services register command to add support for a new service at runtime. See the CLI reference for more details.

Open a GitHub issue

Visit https://github.com/imbue-ai/latchkey/issues and describe:

• Service name and API documentation URL

• How you plan to use it with agents

• Whether the service offers public API access

Contribute support yourself

Latchkey is open source. If you're comfortable with TypeScript and Playwright, you can add support for new services by following the development guide.

Basic service support (manual authentication only) typically requires:

• Service name and base API URLs

• Authentication header format

• A few lines of configuration

Browser-based authentication requires additional implementation depending on how the service handles login flows.

---

Access Latchkey here: https://github.com/imbue-ai/latchkey