Safety check for AI agent and pipeline writes to Databricks tables, before they reach production.
Connect Runs on your machine
claude mcp add bricksentry -e BRICKSENTRY_CONFIG=<BRICKSENTRY_CONFIG> -e DATABRICKS_HOST=<DATABRICKS_HOST> -e DATABRICKS_TOKEN=<DATABRICKS_TOKEN> -- uvx bricksentry-mcp==0.1.20
{
"mcpServers": {
"bricksentry": {
"command": "uvx",
"args": [
"bricksentry-mcp==0.1.20"
],
"env": {
"BRICKSENTRY_CONFIG": "<BRICKSENTRY_CONFIG>",
"DATABRICKS_HOST": "<DATABRICKS_HOST>",
"DATABRICKS_TOKEN": "<DATABRICKS_TOKEN>"
}
}
}
}
{
"mcpServers": {
"bricksentry": {
"command": "uvx",
"args": [
"bricksentry-mcp==0.1.20"
],
"env": {
"BRICKSENTRY_CONFIG": "<BRICKSENTRY_CONFIG>",
"DATABRICKS_HOST": "<DATABRICKS_HOST>",
"DATABRICKS_TOKEN": "<DATABRICKS_TOKEN>"
}
}
}
}
{
"servers": {
"bricksentry": {
"type": "stdio",
"command": "uvx",
"args": [
"bricksentry-mcp==0.1.20"
],
"env": {
"BRICKSENTRY_CONFIG": "<BRICKSENTRY_CONFIG>",
"DATABRICKS_HOST": "<DATABRICKS_HOST>",
"DATABRICKS_TOKEN": "<DATABRICKS_TOKEN>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
BRICKSENTRY_CONFIGOptional | Path to your bricksentry.yml (backend, tables and policy). |
DATABRICKS_HOSTOptional | Databricks workspace URL, when using the Databricks backend. |
DATABRICKS_TOKENOptional, secret | Databricks access token, when using the Databricks backend. |
Details
| Package | [email protected] (PYPI, stdio) |
| First published | 13 Nov 2026 |
| Last updated | 13 Nov 2026 |
| Registry name | io.github.bricksentry/bricksentry |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
