describe_exasol_built_in_function
Loads details for the specified builtin function, reading the resource json. Returns all fields. Some functions, for example TO_CHAR, can have information in more than one row.
LABSCO SUMMARY
It ships read-only: understanding the database is on by default, running SQL against it is a decision you have to make.
Turn on enable_read_query for queries and enable_write_query for DML and DDL; write queries then go through an elicitation step that puts the SQL in front of the user to review before it runs. One more setting worth touching on day one: every metadata type has both a list and a find tool, so use enable_list_tools or enable_find_tools to drop the family you will not use rather than carrying both.
What it is
The vendor's server for Exasol. It opens with metadata and dialect knowledge only — query execution, table summarization and profiling are each behind a configuration flag that is off by default.
What you get
- The database's shape: schemas, tables and views, custom functions and user-defined functions — each with a list tool for the full inventory and a find tool for keyword search over names and comments
- Descriptions of individual objects: columns and constraints for a table or view, input and output parameters for a function or UDF
- The Exasol dialect itself: SQL types, reserved and non-reserved keywords by letter, system tables and statistics tables with their descriptions, and built-in functions by category down to per-function detail
- SQL preprocessors: list what is registered and activate one for the session
- Query execution behind a switch — execute_exasol_query for reads once enable_read_query is on, and DML and DDL once enable_write_query is on
- Two more optional tools: summarize_exasol_table computes column statistics and sample rows, profile_exasol_query runs a query with Exasol profiling and returns the execution-plan breakdown
- Domain knowledge served as resources rather than tools — skill:// documents covering the SQL dialect, UDFs and script languages, system tables, table design, IMPORT and EXPORT, and virtual schemas
Requirements
Python >= 3.11 and uv. Three environment variables carry the connection: EXA_DSN, EXA_USER and EXA_PASSWORD. Run it with uvx exasol-mcp-server@latest, or install it once with uv tool install exasol-mcp-server@latest. Everything else goes through EXA_MCP_SETTINGS, either as inline JSON or a path to a JSON file — that is where enable_read_query and enable_write_query are turned on, default_row_limit is set, and the visible schemas and tables are filtered. For remote use, exasol-mcp-server-http --host --port serves it over HTTP.
Setup effort
One command plus credentials — uv tool install exasol-mcp-server@latest, then supply credentials
USE CASES
01
Finding the right table in a database you have never seen
Keyword-search the schemas and then the tables, and describe the one that looks right.
02
Taking a complete inventory of a small schema
List the schemas, then everything inside the one you want, without keyword guessing.
03
Calling a UDF correctly the first time
Find the script by keyword, then read its input and output parameters.
04
Writing Exasol SQL rather than generic SQL
Browse the built-in function categories, then read the full detail for the function you need.
05
Checking a name against the reserved words before you use it
List keywords by letter, filtered to the reserved ones.
06
Reading the database's own performance statistics
List the statistics tables, then describe the one holding what you are after.
22 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
describe_exasol_custom_function
describe_exasol_statistics_table
describe_exasol_system_table
describe_exasol_table_or_view
describe_exasol_user_defined_function
find_exasol_custom_functions
find_exasol_schemas
find_exasol_tables_and_views
find_exasol_user_defined_functions
list_exasol_built_in_function_categories
Returns a list of builtin function categories.
list_exasol_built_in_functions
Selects the list of builtin functions of the specified type (category), reading the resource json. Returns only the function names.
list_exasol_custom_functions
list_exasol_keywords
list_exasol_preprocessors
list_exasol_schemas
list_exasol_sql_types
list_exasol_statistics_tables
list_exasol_system_tables
list_exasol_tables_and_views
list_exasol_user_defined_functions
set_exasol_preprocessor
Activates the specified SQL preprocessor script at the session level. This setting may be silently reset if the server reconnects to the database. Verify with list_exasol_preprocessors before running queries that depend on it.
BEFORE YOU INSTALL
What to know first
Tools you get
22 tools when we connected; the project documents 34. The rest are off by default — turn on the ones you need.
Extra tools, each turned on by a setting:
enable_read_bucketfs4 toolsenable_write_bucketfs4 toolsenable_read_query1 toolenable_write_query1 toolenable_summarize_table1 toolenable_query_profiling1 tool
Requires
- uvx on PATH
- EXA_DSN in your environment
- EXA_USER in your environment
- EXA_PASSWORD in your environment
Where it runs
Both documented setups run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
uv tool install exasol-mcp-server@latestMCP Clients
Claude Desktop — uv tool install
CLAUDE DESKTOP — UV TOOL INSTALL · JSON
{
"mcpServers": {
"exasol_db": {
"command": "exasol-mcp-server",
"env": {
"EXA_DSN": "<YOUR_EXA_DSN>",
"EXA_USER": "<YOUR_EXA_USER>",
"EXA_PASSWORD": "<YOUR_EXA_PASSWORD>"
}
}
}
}Claude Desktop — uvx
CLAUDE DESKTOP — UVX · JSON
{
"mcpServers": {
"exasol_db": {
"command": "uvx",
"args": [
"exasol-mcp-server@latest"
],
"env": {
"EXA_DSN": "<YOUR_EXA_DSN>",
"EXA_USER": "<YOUR_EXA_USER>",
"EXA_PASSWORD": "<YOUR_EXA_PASSWORD>"
}
}
}
}
