
Fattureincloud Mcp
io.github.aringad由 GitHub 帳號 aringad 發布v1.2.0更新於 Oct 24, 2026
Italian e-invoicing with Fatture in Cloud. Create, send to SDI, manage clients.
概覽
非官方 MCP 伺服器,將助理連接到 Fatture in Cloud,可建立、管理並送出義大利電子發票、客戶與費用。
- 可以做什麼
- 列出、讀取並檢視發票、貸項通知單、形式發票與收到的供應商單據,包含 PDF 連結與電子發票狀態。建立與更新客戶,建立草稿發票、貸項通知單、形式發票與被動費用單據。將形式發票轉為發票,部分更新或複製草稿,刪除草稿單據。將發票與貸項通知單送至義大利 SDI 電子發票系統,並以電子郵件寄送副本。讀取成本/收入中心、年度收入與利潤儀表板,並檢查發票編號連續性。
- 適用情境
- 適合已使用 Fatture in Cloud 的義大利企業或會計人員,希望以自然語言草擬、審閱與提交電子發票,管理客戶與費用,或依成本中心與收入中心分析開票情況。
- 執行需求
- 以本機 Python 套件(pip install fattureincloud-mcp)或 Claude Desktop 套件包執行。需在 FIC_ACCESS_TOKEN 提供 Fatture in Cloud 手動 API 權杖,在 FIC_COMPANY_ID 提供數字公司 ID;寄送禮貌副本郵件另需 FIC_SENDER_EMAIL。需要連線至 Fatture in Cloud API 的網路存取。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Fattureincloud Mcp,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
fattureincloud-mcp
[PyPI] [License] [MCPB] [Listed in italia-mcp-servers]
by Mediaform s.c.r.l. — Genova, Italy
MCP server that connects Claude (Desktop, Code, or any MCP client) to FattureInCloud, the leading Italian SaaS for electronic invoicing. Manage invoices, credit notes, proformas, clients, suppliers, cost/revenue centers, and supplier expenses through natural language. Italy mandates B2B/B2C e-invoicing through the Sistema di Interscambio (SDI) — this server brings AI-assisted billing to that compliance-driven workflow.
⚠️ Unofficial integration. Not affiliated with, endorsed by, or sponsored by TeamSystem S.p.A., owner of the FattureInCloud trademark. The trademark is used here for descriptive purposes only.
Features (23 tools)
Marking payments as "paid" is intentionally not exposed: the FattureInCloud API requires a payment account that cannot be reliably retrieved through the SDK. Use the FattureInCloud web panel for that operation.
Installation
Option 1 — Claude Desktop (MCPB bundle, recommended)
- Download the latest
fattureincloud.mcpbfrom the GitHub Releases page. - Drag the
.mcpbfile onto Claude Desktop, or use Settings → Extensions → Install from file. - When prompted, fill in your FattureInCloud API token, company ID, and (optional) sender email.
That's it — no Python setup, no virtualenv.
Option 2 — Manual install via PyPI
For Claude Code users or any MCP client that reads claude_desktop_config.json-style configuration:
Then add to your MCP client configuration (for Claude Desktop, ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows):
Restart your MCP client after editing the config.
Configuration
How to get the FattureInCloud credentials: log into FattureInCloud, go to Settings → API and Integrations, create a Manual Token with the permissions you need. The COMPANY_ID is in the URL after /c/ once you select a company.
Usage examples
Example 1 — Create an invoice for a known client
"Find client 'Acme Srl' and create a draft invoice for €1,500 + VAT for consulting services in November 2026, payable in 30 days, on revenue center 'Project Alpha'."
Claude will:
- Call
list_clients(cached) and pick the matching client - Call
list_cost_centers(cached) to validateProject Alphaexists - Call
create_invoicewithclient_id, items, dates, payment terms, andrevenue_center="Project Alpha" - Return the draft number and ask whether to send it to SDI
Example 2 — Cost-center analysis
"How much did I bill on the 'Project Alpha' revenue center in 2025? Break down by month."
Claude will:
- Call
list_cost_centersto confirm the label - Call
list_invoicesfor year 2025 (the result includesrevenue_centerper invoice when set) - Filter by
revenue_center == "Project Alpha"and aggregate by month
Example 3 — Recurring invoices replay
"Duplicate every invoice issued to 'Recurring Customer Co' in October 2025, set the new dates in November, keep 30-day payment terms."
Claude will:
- Call
list_invoiceswithquery="Recurring Customer Co"andmonth=10,year=2025 - For each result, call
duplicate_invoicewithnew_dateset in November - Return the list of new draft invoices and ask before sending
Caching
To minimize redundant calls to the FattureInCloud API, this server caches client lookups and the cost-centers list locally as JSON files (default location ~/.fattureincloud-mcp/cache/, scoped per company_id, 24-hour TTL). The cache is transparent: tool signatures don't change.
Cost / Revenue Centers
FattureInCloud uses one shared registry for cost centers (on supplier documents) and revenue centers (on issued documents). With this server you can:
list_cost_centers— read the registryrevenue_center="<label>"— assign oncreate_invoice,create_credit_note,create_proforma,convert_proforma_to_invoice,update_document,duplicate_invoicecost_center="<label>"— assign oncreate_received_document
The label must already exist; centers are managed from FattureInCloud's web UI (Settings → Cost Centers). Passing an unknown label returns the list of valid labels in the error message.
Privacy & Data Handling
- API calls go directly from your machine to FattureInCloud's servers (
api-v2.fattureincloud.it). No data is routed through Mediaform or any third-party server. - The local cache is plaintext JSON in your home directory. You control it.
- Credentials live only in your
.env(gitignored), shell, or MCP clientuser_config. They are never logged or transmitted to anyone other than FattureInCloud. - Full Privacy Policy: https://media-form.it/privacy-policy.html
- See also
docs/PRIVACY.mdfor a mirrored copy of the policy.
Known issues
- Invoice duplication may fail for some clients. A specific client configuration triggers a failure path that hasn't been reproduced yet. Workaround: duplicate manually from the FattureInCloud web panel. Tracked in
docs/KNOWN_ISSUES.md— please report a reproducible case via GitHub issues.
Contributing
Issues and pull requests welcome at https://github.com/aringad/fattureincloud-mcp.
For any code change:
- Fork and branch from
main(feat/...,fix/...,docs/...). - Run
pytest tests/— all 39 tests must stay green. - New code targeting cost-center / cache / new tools should ship with tests (target ≥80% coverage on new modules).
- Conventional commits style (
feat:,fix:,docs:,chore:,test:). - Open a PR. The maintainer reviews changes against the FattureInCloud API contract.
Security
For vulnerability disclosure see SECURITY.md. Preferred channel: GitHub Security Advisories.
License
MIT — see LICENSE.
Trademark
"FattureInCloud" is a trademark of TeamSystem S.p.A. This is an independent, community-built integration. It is not affiliated with, endorsed by, or sponsored by TeamSystem S.p.A. The trademark is used solely for descriptive purposes (to indicate the third-party service this software interoperates with).
Author / Support
- Maintainer: Mediaform s.c.r.l. — Genova, Italy
- Issues: https://github.com/aringad/fattureincloud-mcp/issues
- Email: [email protected]
來源:README.md,提交 847d6fe
工具
0版本歷史
1- v1.2.0最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分