Control Plane vs Elasticsearch
A side-by-side look at the Control Plane and Elasticsearch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Control Plane for security work over a hosted endpoint; choose Elasticsearch for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Control Plane when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
Choose Elasticsearch when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ES_URL, ES_API_KEY, ES_USERNAME, ES_PASSWORD, ES_CA_CERT, NODE_TLS_REJECT_UNAUTHORIZED, MCP_TRANSPORT, MCP_HTTP_PORT. - You want tools like
list_indices, get_mappings, es_search.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 37/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | ES_URLES_API_KEYES_USERNAMEES_PASSWORDES_CA_CERTNODE_TLS_REJECT_UNAUTHORIZEDMCP_TRANSPORTMCP_HTTP_PORT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 8 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 8 |
| Full listing | View Control Plane | View Elasticsearch |
Tools & capabilities
Control Plane tools
No tool names declared yet. Check the project README from the listing page.
Elasticsearch tools 8
list_indicesList indices with pattern filter, health filter, sorting and token-aware summaryget_mappingsGet field mappings with flat/tree/raw modes, field filtering and multi-index comparees_searchFull Query DSL search with auto-highlight, plus harness field validation / auto-fixlookup_fieldsFind the right field names: ECS vocabulary intersected with the index's real fieldsexecute_es_apiExecute any ES REST endpoint directly (GET/POST/PUT/DELETE/HEAD)get_shardsShard info with health analysis, problem detection and recommendationslist_data_streamsList and analyze Data Streams with ILM info and backing index detailsesql_queryExecute ES\
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.
Control Plane
{
"mcpServers": {
"control-plane": {
"url": "https://mcp.thinkneo.ai/mcp"
}
}
}
Elasticsearch
{
"mcpServers": {
"elasticsearch": {
"command": "npx",
"args": [
"-y",
"@tocharianou/elasticsearch-mcp"
],
"env": {
"ES_URL": "YOUR_ES_URL_HERE",
"ES_API_KEY": "YOUR_ES_API_KEY_HERE",
"ES_USERNAME": "YOUR_ES_USERNAME_HERE",
"ES_PASSWORD": "YOUR_ES_PASSWORD_HERE",
"ES_CA_CERT": "YOUR_ES_CA_CERT_HERE",
"NODE_TLS_REJECT_UNAUTHORIZED": "YOUR_NODE_TLS_REJECT_UNAUTHORIZED_HERE",
"MCP_TRANSPORT": "YOUR_MCP_TRANSPORT_HERE",
"MCP_HTTP_PORT": "YOUR_MCP_HTTP_PORT_HERE"
}
}
}
}
Frequently asked questions
Control Plane is categorized under Security and uses a remote HTTP/SSE transport. Elasticsearch belongs to Security and uses a local stdio subprocess. Pick Control Plane for security work and Elasticsearch for security.
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.
Control Plane has no declared pricing — check the project's own site. Elasticsearch 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 control-plane and elasticsearch as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Control Plane has a quality signal of 37/100 (Fair) with 1 views, 0 installs and 3 GitHub stars. Elasticsearch has 57/100 (Good) with 3 views, 0 installs and 8 GitHub stars.