In-depth architectural comparison of the Kibana and Cli MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Kibana
Data Visualization · Local stdio
Quality: 51/100 (Good) | Auth: API Key required
Cli
Data Visualization · Local stdio
Quality: 53/100 (Good) | Auth: API Key required
Verdict Summary: Choose Kibana if you need specialized Data Visualization tools running via a local process. Choose Cli if your workspace requires Data Visualization integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
K
Choose Kibana when:
You need dedicated capabilities in the Data Visualization domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: KIBANA_URL, KIBANA_API_KEY, KIBANA_USERNAME, KIBANA_PASSWORD, KIBANA_COOKIES.
Primary tools included: Dynamic discovery from the Kibana OpenAPI specification, Saved object CRUD, search, pagination, bulk operations, and references, API key, Basic Auth, and cookie-based authentication.
Kibana MCP Server with dynamic API discovery and comprehensive Elastic Stack integration
Push To Display MCP server send structured content to selected boards on iOS and android devices with app Push To Display, route updates to specific panels, and render in real time with display-focused multi-panel layouts.
Kibana is categorized under Data Visualization and uses a local stdio subprocess. In contrast, Cli belongs to Data Visualization using local stdio subprocess. Select Kibana when you need capabilities focused on data visualization and Cli when you require tools for data visualization.