Exasol
@exasol
Exasol MCP server. Provides knowledge about the Exasol database to an LLM through the Model Context Protocol. With Exasol’s MCP Server, you’re not just giving LLMs access to your data. You’re giving them context, structure, and governance, without sacrificing performance or cont
Overview
What is Exasol?
An MCP server that provides LLM access to the Exasol database. It includes tools for reading database metadata and executing data-reading SQL queries.
How to use Exasol?
—
Key features of Exasol
- Collects database metadata by enumerating schemas, tables, views, functions, and UDF scripts.
- Provides filtering mechanisms when enumerating database objects.
- Describes tables (columns and constraints) and functions/scripts (input and output parameters).
- Enables keyword search of database objects.
- Executes provided SQL queries.
Use cases of Exasol
- LLM-powered exploration of an Exasol database schema.
- Automatic generation and execution of data-reading queries from natural language.
- Intelligent searching and retrieving metadata about database objects.
FAQ from Exasol
What does the Exasol MCP server do?
It gives an LLM access to an Exasol database via MCP tools for metadata retrieval and executing queries.
What database objects can it enumerate?
Schemas, tables, views, functions, and UDF scripts.
Does it support writing or modifying data?
No. The server is limited to reading metadata and executing data-reading SQL queries.
How is filtering implemented for object enumeration?
The server provides a filtering mechanism to use alongside object enumeration.
What can it describe for tables vs functions?
For tables it returns the list of columns and constraints; for functions and scripts it returns input and output parameters.
