In-depth architectural comparison of the Cli and Kibana 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
Cli
Data Visualization · Local stdio
Quality: 61/100 (Good) | Auth: OAuth 2.0
Kibana
Data Visualization · Local stdio
Quality: 51/100 (Good) | Auth: API Key required
Verdict Summary: Choose Cli if you need specialized Data Visualization tools running via a local process. Choose Kibana 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?
Choose Cli when:
You need dedicated capabilities in the Data Visualization domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Freemium).
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 MCP Server with dynamic API discovery and comprehensive Elastic Stack integration
Cli is categorized under Data Visualization and uses a local stdio subprocess. In contrast, Kibana belongs to Data Visualization using local stdio subprocess. Select Cli when you need capabilities focused on data visualization and Kibana when you require tools for data visualization.