Is this MCP server read-only?
Yes, this project builds a read-only MCP server. For full read, write, update, delete, and action capabilities, CData offers a separate free CData MCP Server for Elasticsearch (beta).
@CDataSoftware
Basic information
This project builds a read-only MCP server. For full read, write, update, delete, and action capabilities and a simplified setup, check out our free [CData MCP Server for Elasticsearch (beta)](https://www.cdata.com/download/download.aspx?sku=EEZK-V&type=beta).
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"{classname_dash}": {
"command": "PATH\\TO\\java.exe",
"args": [
"-jar",
"PATH\\TO\\CDataMCP-jar-with-dependencies.jar",
"PATH\\TO\\elasticsearch.prp"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Elasticsearch MCP Server by CData is a read-only Model Context Protocol (MCP) server that allows LLMs such as Claude Desktop to query live Elasticsearch data using natural language. It wraps the CData JDBC Driver for Elasticsearch, which exposes Elasticsearch as relational SQL models, and makes that data available through a simple MCP interface — no SQL required.
Clone the repository, build the JAR with Maven (mvn clean install), download and license the CData JDBC Driver for Elasticsearch, configure a connection string using the driver's utility, and create a .prp file with JDBC properties. Then add the server entry to your Claude Desktop config file (claude_desktop_config.json) pointing to Java and the JAR, and restart Claude Desktop. The server runs via stdio.
get_tables, get_columns, and run_query.prp) fileYes, this project builds a read-only MCP server. For full read, write, update, delete, and action capabilities, CData offers a separate free CData MCP Server for Elasticsearch (beta).
You need Java (to run the JAR file), the CData JDBC Driver for Elasticsearch (installed and licensed), and a client that supports MCP over `stdio` (like Claude Desktop).
It uses a JDBC connection string configured in a `.prp` file. The driver models Elasticsearch data as relational tables and exposes them via MCP tools.
The server uses `stdio` transport, so it can only be used with clients that run on the same machine as the server.
Data remains in the live Elasticsearch instance; the server retrieves it on demand. No data is stored by the MCP server itself.
A Model Context Protocol server to connect to MongoDB databases and MongoDB Atlas Clusters.

Oracle MCP server with no run-sql tool: It generates tools for each of the PL/SQL procedures, tables and approved SQL you choose. The server doesn't expose a SQL prompt, and can't reveal how it's connected to Oracle.
A Model Context Protocol (MCP) server that enables secure interaction with MySQL databases

Local database MCP server: your agent sees a migration's impact before it runs, for PostgreSQL, MySQL, SQL Server and SQLite, with no database credentials.

Connect Karma.Domains to ChatGPT, Claude, Cursor, VS Code, or another MCP client — and find a domain in plain language. The same auctions, expired, backorder, and buy-now data you use in the app, plus saved filters, note
Comments