Teamleader Focus

Getting a token

1. Register an integration in the Teamleader Marketplace developer area (developer.teamleader.eu). You receive a client id and client secret.
2. Run the authorization-code flow once for the account and keep the refresh token — Teamleader's access tokens last one hour.
3. Set TEAMLEADER_CLIENT_ID, TEAMLEADER_CLIENT_SECRET and TEAMLEADER_REFRESH_TOKEN. AnythingMCP refreshes the access token on its own.

Every endpoint is a POST, including the reads. Teamleader's API is action-shaped — companies.list, deals.info, invoices.list — and all of them are POSTs whose JSON body carries the filter. That is why these tools look like writes in an HTTP trace even when they only read; the tool names here say what each one actually does.

Filters are a nested object. {"filter": {"term": "Acme"}, "page": {"size": 20, "number": 1}, "sort": [{"field": "name", "order": "asc"}]}. The available filter keys differ per action and are listed in Teamleader's reference.

Refresh tokens rotate. Teamleader issues a new refresh token on every refresh and invalidates the old one. AnythingMCP persists the rotated token back into the connector, so the stored value stays current — but if you also use the same refresh token from another script, one of the two will start failing.

Ids are UUIDs, and deals.info needs the deal's id, not its reference number.

Cloud reachability: api.focus.teamleader.eu is public with a valid certificate.