
Boostu Teamleader Mcp
io.github.boostuagency由 GitHub 账号 boostuagency 发布v2.1.4更新于 Nov 10, 2026
MCP server for Teamleader Focus CRM. Use Teamleader in Claude and other AI assistants.
概览
本地 MCP 服务器,让 AI 助手读取和修改 Teamleader Focus CRM 数据,包括联系人、公司、商机、报价、发票、项目和工单。
- 可以做什么
- 创建、更新联系人并关联公司,管理各销售流程中的商机
- 创建、更新、发送和接受报价;创建、记账、发送发票并登记付款;查看贷项通知单
- 浏览产品、价格表、分类和计量单位,以及商机阶段、税率、付款条件等参考数据
- 管理项目、里程碑、工时记录和实时计时器,安排或完成通话与会议
- 创建并回复支持工单,添加标签和备注,列出和上传文件,注册 Webhook
- 查询用户、团队、部门和自定义字段定义
- 适用场景
- 当 CRM、报价和开票都在 Teamleader Focus 中,并希望助手在不切换应用的情况下起草报价、记账并发送发票、记录工时或回答商机与客户相关问题时适用。
- 运行要求
- 通过 npx 或全局 npm 安装本地运行(需要 Node.js)。需要 Teamleader Focus 集成,并提供 OAuth2 授权流程取得的 TEAMLEADER_CLIENT_ID、TEAMLEADER_CLIENT_SECRET 和 TEAMLEADER_REFRESH_TOKEN。由于 Teamleader 每次调用都会轮换刷新令牌,应把 TEAMLEADER_TOKEN_STORE 设为可写文件路径。TEAMLEADER_TOOLS 可限制加载的工具组。
安装
在 SourceWeft 中
- 打开 控制台中的 Boostu Teamleader Mcp,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
🔗 BoostU Teamleader MCP
The open-source Teamleader Focus MCP server. Manage your CRM from Claude and other AI assistants, in plain language. 🤖
[CI] [npm version] [npm downloads] [node] [Model Context Protocol] [tools] [License: MIT] [Made by BoostU]
💡 What is this?
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.
Prefer not to self-host?
Use the managed, always-on edition at teamleader-mcp.boostu.be — no OAuth setup, magic-link login, and a one-click connector for Claude. Free during the preview, paid plans after.
This repository is the open-source MCP server itself: run it locally with your own Teamleader integration. The hosted edition adds multi-tenant authentication, a dashboard, usage insights, and managed token handling on top of the same server.
🔌 How it works
You ask Claude in plain language. Claude calls this MCP server, which authenticates to Teamleader Focus over OAuth2 and runs the matching API call. Your data stays in Teamleader; this server only brokers the calls.
Use the outline button at the top-right of this file to jump to any section.
✨ Highlights
- 👥 Full CRM: create and update contacts, companies, and deals across all pipelines
- 🧾 Quotations and invoicing: create quotations on deals, book invoices into accounting, send by email, and register payments
- 📦 Product catalog: browse products, categories, price lists, and units of measure
- 🔁 Subscriptions: create, update, and deactivate recurring subscriptions
- 📊 Projects and time tracking: manage projects, milestones, log time entries, and start/stop live timers
- 🎫 Customer-service tickets: open tickets, post replies, and update statuses
- 🔎 Reference-data lookups: resolve deal phases, pipelines, tax rates, payment terms, lost reasons, and more
- 🔐 OAuth2 with automatic refresh-token rotation: tokens are refreshed transparently; rotated tokens are persisted to a configurable file
- 🧩 Selectable tool groups: load only the groups you need via
TEAMLEADER_TOOLSto keep your assistant's context lean
🚀 Quick Start
Run without installing
Global install
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
Claude Code
Add to your project's .mcp.json or ~/.claude/mcp.json:
Cursor
Add to .cursor/mcp.json in your project root (or the global ~/.cursor/mcp.json):
Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
🔐 Authentication
You need three env vars: TEAMLEADER_CLIENT_ID, TEAMLEADER_CLIENT_SECRET, and TEAMLEADER_REFRESH_TOKEN. Obtain them by registering an integration in the Teamleader Marketplace / Developer portal and completing the OAuth2 authorization flow.
Teamleader rotates the refresh token on every API call. Set TEAMLEADER_TOKEN_STORE to a writable file path so the server can persist the latest token between restarts — without it the token in your config will go stale after the first restart.
For the full step-by-step walkthrough (authorize URL, code exchange, helper scripts) see docs/AUTHENTICATION.md.
⚙️ Configuration
Environment variables
Selective tool groups
Use TEAMLEADER_TOOLS to limit which tool groups are registered. This is useful when you want to keep the assistant's tool list small or restrict access to certain areas of Teamleader.
Full list of group keys:
🧰 Available Tools
Contacts
Companies
Deals
Tasks
Events
Invoices
Quotations
Products
Reference Data
Organisation
Custom Fields
Credit Notes
Subscriptions
Projects
Time Tracking
Activities (Calls & Meetings)
Tickets
Tags
Notes
Files
Webhooks
💬 Example Prompts
🐳 Docker
🛠️ Development
🏗️ Architecture
The core of the server is createServer in src/server.ts, which is transport-agnostic — it takes a TeamleaderClient and registers the enabled tool groups, returning a plain McpServer instance that the entry point (src/index.ts) wires to a StdioServerTransport. Tool logic lives in per-domain modules under src/tools/, each following a consistent try / respond / catch / respondError pattern using shared helpers in src/lib/. OAuth2 token acquisition and rotation are handled entirely in src/api/auth.ts, transparent to the rest of the codebase. A hosted, multi-tenant edition of this server is available at teamleader-mcp.boostu.be.
✅ Endpoint Verification
Most read endpoints (*.list, *.info) have been live-verified against the Teamleader Focus API. Several write and action endpoints (e.g. subscriptions.create, projects.create, files.upload) are implemented from the official documentation but have not been tested against a live account with the relevant module active. If an endpoint name is wrong, the call will fail with a clear HTTP error message rather than silently misbehaving. The full endpoint manifest and verification status are documented in docs/teamleader-endpoints.md.
🤝 Contributing
See CONTRIBUTING.md for development setup, commit conventions, and instructions on adding new tool groups.
🔒 Security
Report security vulnerabilities to [email protected] — do not open a public issue. See SECURITY.md for the disclosure policy. Never commit .env files or .teamleader-token to version control; both are listed in .gitignore.
⚖️ Disclaimer
This is an independent, community-built integration. It is not affiliated with, endorsed by, or sponsored by Teamleader NV. "Teamleader" and "Teamleader Focus" are trademarks of Teamleader NV and are used here only to describe compatibility. You are responsible for your own use of the Teamleader API under Teamleader's terms.
📄 License
MIT License — Copyright (c) 2026 BoostU Agency. See NOTICE for upstream attribution.
来源:README.md,提交 6097220
工具
0版本历史
1- v2.1.4最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
