Fattureincloud MCP vs Tradingview MCP
A side-by-side look at the Fattureincloud MCP and Tradingview MCP 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 Tradingview 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?
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 Tradingview MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 44/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Freemium |
| Required env vars | FIC_ACCESS_TOKENFIC_COMPANY_ID | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 25 | 5,132 |
| Directory activity | 4 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Fattureincloud MCP | View Tradingview MCP |
Tools & capabilities
Fattureincloud MCP tools
No tool names declared yet. Check the project README from the listing page.
Tradingview 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.
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"
}
}
}
}
Tradingview MCP
{
"mcpServers": {
"tradingview-mcp": {
"command": "uvx",
"args": [
"tradingview-mcp-server"
]
}
}
}
Frequently asked questions
Fattureincloud MCP is categorized under Finance & Fintech and uses a local stdio subprocess. Tradingview MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick Fattureincloud MCP for finance & fintech work and Tradingview MCP 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. Tradingview MCP is listed as freemium — a free tier with paid plans. Auth: no auth required. 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 tradingview-mcp 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. Tradingview MCP has 51/100 (Good) with 6 views, 0 installs and 5,132 GitHub stars.