Fattureincloud MCP vs MCP Adyen
A side-by-side look at the Fattureincloud MCP and MCP Adyen MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Fattureincloud MCP for finance & fintech work as a local process; choose MCP Adyen 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?
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.
Choose MCP Adyen when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 44/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | FIC_ACCESS_TOKENFIC_COMPANY_ID | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 25 | 274 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Fattureincloud MCP | View MCP Adyen |
Tools & capabilities
Fattureincloud MCP tools
No tool names declared yet. Check the project README from the listing page.
MCP Adyen 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.
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"
}
}
}
}
MCP Adyen
{
"mcpServers": {
"mcp-adyen": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-itau@alpha"
]
}
}
}
Frequently asked questions
Fattureincloud MCP is categorized under Finance & Fintech and uses a local stdio subprocess. MCP Adyen belongs to Finance & Fintech and uses a local stdio subprocess. Pick Fattureincloud MCP for finance & fintech work and MCP Adyen for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Fattureincloud MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. MCP Adyen has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add fattureincloud-mcp and mcp-adyen as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Fattureincloud MCP has a quality signal of 44/100 (Fair) with 4 views, 0 installs and 25 GitHub stars. MCP Adyen has 49/100 (Fair) with 1 views, 0 installs and 274 GitHub stars.