
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.
概覽
Teamleader Focus CRM 的 MCP 伺服器,讓 AI 助理以自然語言查詢與操作聯絡人、商機、報價、發票、專案與工單。
- 可以做什麼
- 查詢、建立與更新聯絡人、公司、商機、任務與行事曆活動,並管理標籤與備註。建立報價單、寄送報價、接受報價,以及建立草稿發票、入帳、寄送、登記付款與下載。瀏覽產品目錄、價格表、計量單位、稅率、付款條件等參考資料。管理訂閱、專案與里程碑、工時紀錄與即時計時器。處理客服工單、通話與會議活動、檔案下載上傳,以及註冊 Webhook。
- 適用情境
- 當你使用 Teamleader Focus 管理 CRM、報價、發票、專案與工時,並希望用自然語言讓 AI 助理代為查詢或操作時適用。適合願意自行建立整合並管理 OAuth 憑證的開發者或自架團隊。
- 執行需求
- 需在本機以 Node.js 執行 npm 套件(可用 npx)。需在 Teamleader 開發者入口建立整合並完成 OAuth2 授權,提供 TEAMLEADER_CLIENT_ID、TEAMLEADER_CLIENT_SECRET 與 TEAMLEADER_REFRESH_TOKEN 三個環境變數。建議設定 TEAMLEADER_TOKEN_STORE 指定可寫入的檔案路徑,否則重新啟動後權杖會失效。需網路連線至 Teamleader API。
安裝
在 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,提交 44ba8f5
工具
0版本歷史
1- v2.1.4最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
