A side-by-side look at the Costory FinOps MCP and Supabase 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 Costory FinOps MCP for databases work over a hosted endpoint; choose Supabase MCP Server for databases as a local process. You can also run both side by side in one mcpServers block.
SUPABASE_API_KEY.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 41/100 · Fair | 45/100 · Fair |
| 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 | None listed | SUPABASE_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 52 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Costory FinOps MCP | View Supabase MCP Server |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"costory-finops-mcp": {
"url": "https://app-api.costory.io/mcp"
}
}
}
{
"mcpServers": {
"joshuarileydev-supabase-mcp-server": {
"command": "npx",
"args": [
"y"
],
"env": {
"SUPABASE_API_KEY": "YOUR_SUPABASE_API_KEY_HERE"
}
}
}
}