Csvglow vs Tableaugen MCP
A side-by-side look at the Csvglow and Tableaugen MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Csvglow for data visualization work as a local process; choose Tableaugen MCP for data visualization as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Csvglow when
- You need dedicated capabilities in the Data Visualization domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Tableaugen MCP when
- You need dedicated capabilities in the Data Visualization domain.
- You prefer a local stdio subprocess transport.
- You want tools like
generate_workbook, profile_dataset, publish_to_cloud.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Visualization | Data Visualization |
| Quality signal | 49/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
Tools & capabilities
Csvglow tools
No tool names declared yet. Check the project README from the listing page.
Tableaugen MCP tools 5
generate_workbookGenerate a Tableau `.twb` / `.twbx` from a CSV path and a natural-language promptprofile_datasetInspect a CSV and return schema, data types, cardinality, and null countspublish_to_cloudPublish a generated workbook to Tableau Cloud or Tableau Serverlist_templatesReturn available dashboard templates (sales, OEE, finance, marketing, etc.)preview_workbookReturn a thumbnail image of a generated workbook for inline preview
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.
Csvglow
{
"mcpServers": {
"ratnaditya-j-csvglow": {
"command": "npx",
"args": [
"-y",
"csvglow"
]
}
}
}
Tableaugen MCP
{
"mcpServers": {
"tableaugen-mcp": {
"command": "npx",
"args": [
"-y",
"tableaugen-mcp"
]
}
}
}
Frequently asked questions
Csvglow is categorized under Data Visualization and uses a local stdio subprocess. Tableaugen MCP belongs to Data Visualization and uses a local stdio subprocess. Pick Csvglow for data visualization work and Tableaugen MCP for data visualization.
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.
Csvglow is listed as free. Auth: no auth required. Tableaugen MCP 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 ratnaditya-j-csvglow and tableaugen-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Csvglow has a quality signal of 49/100 (Fair) with 3 views, 0 installs and 14 GitHub stars. Tableaugen MCP has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.