Elasticsearch MCP Server vs QueryWeaver
A side-by-side look at the Elasticsearch MCP Server and QueryWeaver MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Elasticsearch MCP Server for databases work as a local process; choose QueryWeaver 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 Elasticsearch MCP 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.
- You want tools like
list_indices, get_index, create_index.
Choose QueryWeaver when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 65/100 · Great | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 313 | 1,086 |
| Directory activity | 3 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 20 | Not listed |
| Full listing | View Elasticsearch MCP Server | View QueryWeaver |
Tools & capabilities
Elasticsearch MCP Server tools 20
list_indicesList all indices.get_indexReturns information (mappings, settings, aliases) about one or more indices.create_indexCreate a new index.delete_indexDelete an index.search_documentsSearch for documents.index_documentCreates or updates a document in the index.get_documentGet a document by ID.delete_documentDelete a document by ID.delete_by_queryDeletes documents matching the provided query.get_cluster_healthReturns basic information about the health of the cluster.get_cluster_statsReturns high-level overview of cluster statistics.list_aliasesList all aliases.- +8 more on the listing page
QueryWeaver 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.
Elasticsearch MCP Server
{
"mcpServers": {
"cr7258-elasticsearch-mcp-server": {
"command": "uvx",
"args": [
"elasticsearch-mcp-server"
]
}
}
}
QueryWeaver
{
"mcpServers": {
"queryweaver": {
"command": "uvx",
"args": [
"queryweaver"
]
}
}
}
Frequently asked questions
Elasticsearch MCP Server is categorized under Databases and uses a local stdio subprocess. QueryWeaver belongs to Databases and uses a local stdio subprocess. Pick Elasticsearch MCP Server for databases work and QueryWeaver 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.
Elasticsearch MCP Server is listed as free. Auth: api key required. QueryWeaver 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 cr7258-elasticsearch-mcp-server and queryweaver as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Elasticsearch MCP Server has a quality signal of 65/100 (Great) with 3 views, 0 installs and 313 GitHub stars. QueryWeaver has 48/100 (Fair) with 3 views, 0 installs and 1,086 GitHub stars.