Lumabill vs Fattureincloud MCP
A side-by-side look at the Lumabill and Fattureincloud MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Lumabill for finance & fintech work; choose Fattureincloud MCP for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
LChoose Lumabill when
- You need dedicated capabilities in the Finance & Fintech domain.
Choose Fattureincloud MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
FIC_ACCESS_TOKEN, FIC_COMPANY_ID.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | L Lumabill | |
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 37/100 · Fair | 44/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | FIC_ACCESS_TOKENFIC_COMPANY_ID |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 25 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Lumabill | View Fattureincloud MCP |
Tools & capabilities
Lumabill tools
No tool names declared yet. Check the project README from the listing page.
Fattureincloud MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Lumabill
No confirmed install command for Lumabill yet — follow the setup steps linked from its listing page rather than a guessed package name.
Fattureincloud MCP
{
"mcpServers": {
"fattureincloud-mcp": {
"command": "uvx",
"args": [
"fattureincloud-mcp"
],
"env": {
"FIC_ACCESS_TOKEN": "YOUR_FIC_ACCESS_TOKEN_HERE",
"FIC_COMPANY_ID": "YOUR_FIC_COMPANY_ID_HERE"
}
}
}
}