MCP Flowcore Platform vs ThoughtSpot MCP Server
A side-by-side look at the MCP Flowcore Platform and ThoughtSpot MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Flowcore Platform for data platforms work as a local process; choose ThoughtSpot MCP Server for data platforms as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Flowcore Platform when
- You need dedicated capabilities in the Data Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
USERNAME, PAT.
Choose ThoughtSpot MCP Server when
- You need dedicated capabilities in the Data Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Platforms | Data Platforms |
| Quality signal | 52/100 · Good | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | OAuth 2.0 |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | USERNAMEPAT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 9 | 34 |
| Directory activity | 6 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MCP Flowcore Platform | View ThoughtSpot MCP Server |
Tools & capabilities
MCP Flowcore Platform tools
No tool names declared yet. Check the project README from the listing page.
ThoughtSpot MCP Server 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.
MCP Flowcore Platform
{
"mcpServers": {
"flowcore-mcp-flowcore-platform": {
"command": "npx",
"args": [
"-y",
"@flowcore/platform-mcp-server"
],
"env": {
"USERNAME": "YOUR_USERNAME_HERE",
"PAT": "YOUR_PAT_HERE"
}
}
}
}
ThoughtSpot MCP Server
{
"mcpServers": {
"mcp-server-8": {
"command": "npx",
"args": [
"-y",
"@thoughtspot/mcp-server"
]
}
}
}
Frequently asked questions
MCP Flowcore Platform is categorized under Data Platforms and uses a local stdio subprocess. ThoughtSpot MCP Server belongs to Data Platforms and uses a local stdio subprocess. Pick MCP Flowcore Platform for data platforms work and ThoughtSpot MCP Server for data platforms.
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.
MCP Flowcore Platform is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. ThoughtSpot MCP Server has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 flowcore-mcp-flowcore-platform and mcp-server-8 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Flowcore Platform has a quality signal of 52/100 (Good) with 6 views, 0 installs and 9 GitHub stars. ThoughtSpot MCP Server has 48/100 (Fair) with 2 views, 0 installs and 34 GitHub stars.