scherlok
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCHERLOK_CONNECTION | Yes | Database connection string for Scherlok MCP server |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tablesA | List the tables visible to the configured warehouse connection. Returns the table names (capped) and a total count. Use this to discover
what can be profiled before calling |
| investigateA | Profile tables and store them as the baseline for future anomaly checks. Pass |
| watchA | Profile tables and detect anomalies against the stored baseline. Returns the anomalies found (type, severity, message per table), capped.
Pass |
| statusA | Report the current monitoring state. Returns the connection target (password redacted), how many tables the connection can see, and how many anomalies were recorded in the last 30 days. A quick health glance without profiling anything. |
| historyA | Return anomalies recorded in the last Reads from the local profile store — does not re-profile the warehouse. |
| checkA | Run a watch over all tables and return a CI-style pass/fail gate.
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rbmuller/scherlok'
If you have feedback or need assistance with the MCP directory API, please join our Discord server