TeamSystem
TeamSystem — Italy's largest business-software group — over the TeamSystem Digital / Enterprise APIs: customers, invoices, items and documents. OAuth 2.0. Partner credentials required.
7 天免费 · 无需信用卡 · EU 托管
问 TeamSystem 任何事
通过 AnythingMCP 对 TeamSystem 试一个真实提示 — Claude 调用工具并返回答案。在你的消息上按 Enter 即可在 Cloud 安装。
在 Cloud 上安装 TeamSystemClaude 是 AI，可能会出错。请核对回答。
2 分钟设置
- 1在 cloud.anythingmcp.com 开始免费试用。
- 2在连接器商店点击 TeamSystem。提示时粘贴凭据。
- 3生成 MCP API 密钥，将 AI 客户端指向生成的 MCP URL。
配置 TeamSystem
直接来自连接器定义：在哪里获取凭据、需要哪些权限，以及该适配器调用的是哪个 API。 由连接器作者以英文提供。
Partner credentials required. TeamSystem's APIs are published through its developer portal but issued per integration partner and per product line (TeamSystem Enterprise, TS Digital, Alyante, …). You will not find a self-service key in the product UI, and there is no public sandbox — which is why this adapter ships unverified.
Setup
- Register at developer.teamsystem.com and have your TeamSystem partner enable the APIs for your customer's tenant.
- Create an application and note the client id and client secret.
- Note the tenant id that scopes your customer's data. Set
TEAMSYSTEM_CLIENT_ID,TEAMSYSTEM_CLIENT_SECRETandTEAMSYSTEM_TENANT_ID.
Client credentials, scoped per product. The token endpoint is https://auth.teamsystem.com/oauth2/token and the scopes on your application decide which of the paths below answer. A 403 here is almost always a missing scope rather than a bad secret.
X-Tenant-Id on every call. TeamSystem multiplexes many customers behind one API host; the tenant header is what picks one. A wrong tenant returns an empty result, not an error.
Italian tax vocabulary applies. Documents carry partitaIva and codiceFiscale, and invoices going through the Sistema di Interscambio carry an e-invoice status. A rejected (scartata) invoice has not legally been issued.
Unverified. The paths and field names below follow the vendor's published documentation and have not been exercised against a live tenant. Treat a 404 as a docs-versus-reality gap and check the developer portal before concluding that the credential is wrong. A correction from anyone running this against a real system is genuinely welcome.