Boostu MCP Server

MCP server for Teamleader Focus CRM. Use Teamleader in Claude and other AI assistants. Exposed over MCP by the boostu mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

boostu-teamleader-mcp is a Model Context Protocol server that exposes the Teamleader Focus API to AI assistants — including Claude Desktop, Claude Code, Cursor, and Windsurf. It provides over 100 tools spanning the full Teamleader Focus surface: CRM (contacts, companies, deals), sales documents (quotations, invoices, credit notes), product catalog, subscriptions, projects, time tracking, customer-service tickets, and more. Point your AI at it and manage your entire CRM through natural language.

Its toolset

Everything the assistant can do here goes through one of these:

• Cursor — Add to .cursor/mcp.json in your project root (or the global ~/.cursor/mcp.json):
• Windsurf — The Windsurf tool exposed by this server
• Contacts — The Contacts tool exposed by this server
• Companies — The Companies tool exposed by this server
• Deals — The Deals tool exposed by this server
• Tasks — The Tasks tool exposed by this server
• Events — The Events tool exposed by this server
• Invoices — The Invoices tool exposed by this server
• Quotations — The Quotations tool exposed by this server
• Products — The Products tool exposed by this server
• Organisation — The Organisation tool exposed by this server
• Subscriptions — The Subscriptions tool exposed by this server

Configuration

You will need 3 environment variables: TEAMLEADER_CLIENT_ID, TEAMLEADER_CLIENT_SECRET, TEAMLEADER_REFRESH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Boostu's toolset — Cursor, Windsurf, Contacts and 11 more — is a fair guide to whether it matches your workflow. It is maintained by boostuagency; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Boostu.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the boostu mcp server does with a few real requests.