Weave vs MCP Bigquery Server
A side-by-side look at the Weave and MCP Bigquery Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
W
WeaveDatabasesConnected tables, relations, workflows and markdown documents in one SQLite file, over MCP.41FairAuth: not declaredVerdict: choose Weave for databases work; choose MCP Bigquery Server for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Bigquery Server when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | W Weave | |
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 41/100 · Fair | 56/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 13 | 148 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Weave | View MCP Bigquery Server |
Tools & capabilities
Weave tools
No tool names declared yet. Check the project README from the listing page.
MCP Bigquery 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.
Weave
No confirmed install command for Weave yet — follow the setup steps linked from its listing page rather than a guessed package name.
MCP Bigquery Server
{
"mcpServers": {
"ergut-mcp-bigquery-server": {
"command": "npx",
"args": [
"-y",
"@ergut/mcp-bigquery-server"
]
}
}
}
Frequently asked questions
Weave is categorized under Databases and uses an install path we have not confirmed yet. MCP Bigquery Server belongs to Databases and uses a local stdio subprocess. Pick Weave for databases work and MCP Bigquery Server 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. Weave has no confirmed install command yet — follow its own setup instructions.
Weave has no declared pricing — check the project's own site. MCP Bigquery Server 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 weave and ergut-mcp-bigquery-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Weave has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 13 GitHub stars. MCP Bigquery Server has 56/100 (Good) with 2 views, 0 installs and 148 GitHub stars.