Vitrus analytics vs Redash MCP
A side-by-side look at the Vitrus analytics and Redash MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
V
Vitrus analyticsDatabases · Remote HTTP/SSERead-only web analytics — AI traffic, revenue, goals, funnels — with the SQL behind every number.41FairAuth: not declaredVerdict: choose Vitrus analytics for databases work over a hosted endpoint; choose Redash MCP for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
VChoose Vitrus analytics when
- You need dedicated capabilities in the Databases domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
VITRUS_PASSWORD.
Choose Redash MCP when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
REDASH_URL, REDASH_API_KEY, REDASH_SAFETY_MODE, REDASH_SAFETY_DISABLE_PII, REDASH_SAFETY_DISABLE_COST, REDASH_AUTO_LIMIT, REDASH_MCP_CACHE_TTL, REDASH_MCP_CACHE_MAX_MB.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | V Vitrus analytics | |
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 41/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | VITRUS_PASSWORD |
Tools & capabilities
Vitrus analytics tools
No tool names declared yet. Check the project README from the listing page.
Redash 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.
Vitrus analytics
{
"mcpServers": {
"vitrus-analytics": {
"url": "https://app.vitrus.dev/mcp"
}
}
}
Redash MCP
{
"mcpServers": {
"seob717-redash-mcp": {
"command": "npx",
"args": [
"-y",
"redash-mcp"
],
"env": {
"REDASH_URL": "YOUR_REDASH_URL_HERE",
"REDASH_API_KEY": "YOUR_REDASH_API_KEY_HERE",
"REDASH_SAFETY_MODE": "YOUR_REDASH_SAFETY_MODE_HERE",
"REDASH_SAFETY_DISABLE_PII": "YOUR_REDASH_SAFETY_DISABLE_PII_HERE",
"REDASH_SAFETY_DISABLE_COST": "YOUR_REDASH_SAFETY_DISABLE_COST_HERE",
"REDASH_AUTO_LIMIT": "YOUR_REDASH_AUTO_LIMIT_HERE",
"REDASH_MCP_CACHE_TTL": "YOUR_REDASH_MCP_CACHE_TTL_HERE",
"REDASH_MCP_CACHE_MAX_MB": "YOUR_REDASH_MCP_CACHE_MAX_MB_HERE"
}
}
}
}
Frequently asked questions
Vitrus analytics is categorized under Databases and uses a remote HTTP/SSE transport. Redash MCP belongs to Databases and uses a local stdio subprocess. Pick Vitrus analytics for databases work and Redash MCP for databases.
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.
Vitrus analytics has no declared pricing — check the project's own site. Redash MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key 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 vitrus-analytics and seob717-redash-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Vitrus analytics has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 4 GitHub stars. Redash MCP has 53/100 (Good) with 2 views, 0 installs and 1 GitHub stars.