Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add exasol/mcp-server --skill exasol-mcp-servergit clone --depth 1 https://github.com/exasol/mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/exasol/mcp-server/exasol-mcp-server)<a href="https://agentmods.dev/skills/exasol/mcp-server/exasol-mcp-server"><img src="https://agentmods.dev/badge/skills/exasol/mcp-server/exasol-mcp-server.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00036 | $0.00778 |
| Opus 5 | $0.00018 | $0.00389 |
| Sonnet 5 | $0.00007 | $0.00156 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
exasol-mcp-server scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exasol MCP Server
Optional Tools
Several tools — including execute_exasol_query, profile_exasol_query, execute_exasol_write_query, summarize_exasol_table, and all BucketFS tools — are disabled by default and may not appear in the tool list. If a workflow below requires a tool that is not available, do not retry or attempt workarounds: inform the user that the tool is disabled and needs to be enabled by the server administrator.
Common Workflows
Schema Exploration
Start broad, then narrow down:
1. list_exasol_schemas
→ pick a schema
2. list_exasol_tables_and_views(schema_name=...)
→ pick a table
3. describe_exasol_tables_and_views(schema_name=..., table_names=[...])
→ see columns, types, constraints (pass every table/view needed in one call)
4. summarize_exasol_table(schema_name=..., table_name=...)
→ understand data distribution (if enabled)
If you already know roughly what you are looking for, use the find_* variants to keyword-search across all schemas at once.
Writing and Debugging a Query
1. execute_exasol_query(query="SELECT ...")
→ verify the query works and returns expected data
2. profile_exasol_query(query="SELECT ...")
→ check the execution plan if the query is slow
→ look at the EXECUTION_MODE column: COMPILE, EXECUTE, WAIT
→ high COMPILE time → query rewrite or simplification may help
→ high EXECUTE time → check JOIN strategies and data distribution
Discovering and Using UDFs
1. list_exasol_user_defined_functions(schema_name=...)
→ see all UDF scripts in a schema
2. describe_exasol_user_defined_functions(schema_name=..., func_names=[...])
→ read source code and parameter declarations (pass every UDF needed in one call)
3. execute_exasol_query(query="SELECT schema.script_name(col) FROM table")
→ invoke the script on data
BucketFS Workflow
1. list_bucketfs_directories(path="/")
→ see top-level buckets
2. list_bucketfs_files(path="/my_bucket/models/")
→ list model files
3. read_bucketfs_text_file(path="/my_bucket/config.json")
→ read a configuration file
4. write_text_to_bucketfs_file(path="/my_bucket/output.txt", content="...")
→ save results or configuration
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 106 lines · 36 tokens per session scan A 7e4939d3bd20
exasol-mcp-server is a skill published in the GitHub repository exasol/mcp-server (18 stars, last pushed 6d ago), licensed MIT. It adds 36 tokens to every session and 778 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
pg-bloat-analysis
Detects and remediates table and index bloat in PostgreSQL using pgstattuple analysis. Identifies fragmentation, dead tuples, and wasted space with prioritized maintenance actions including VACUUM, REINDEX, and pgrepack recommendations.
pg-index-optimization
Performs comprehensive PostgreSQL index optimization including unused index cleanup, duplicate detection, missing index recommendations, and hypothetical index testing with HypoPG. Provides actionable CREATE/DROP INDEX statements with estimated impact.
pg-slow-query-diagnosis
Diagnoses slow PostgreSQL queries by analyzing pgstatstatements, execution plans, index opportunities, and table statistics. Guides the agent through a systematic investigation workflow using pgtuner-mcp tools to produce actionable optimization recommendations.
n8n-error-handling
Wire n8n error handling so failures are loud, structured, and recoverable. Use when building any webhook/API workflow, a scheduled or unattended workflow, or any path where a silent failure would drop user-visible work — and whenever the user mentions error handling, onError, continueErrorOutput, error…
n8n-validation-expert
Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, the validation loop process, or auto-fix capabilities.…
solr-query
To build and debug Solr queries: eDisMax, block join, JSON facets, kNN, explain.