By AgamiAI
Add a trust layer between AI and your database so every query is defensible. Curate a semantic model with confidence-scored joins, metrics, and filters, approve or reject AI-proposed changes via a review dashboard, and reconcile dashboard numbers against the model using NL→SQL with mismatch drill-downs. Every answer ships a SQL receipt showing what ran and which model version it used.
EARLY ACCESS (in testing) — usable today, but newer than the local single-player path; feedback welcome via a GitHub issue. Prepares a ready-to-run, self-hosted agami deploy bundle ON THE USER'S MACHINE so a team can stand up a shareable MCP server their Claude connects to. Conversationally gathers the hard-floor inputs (hostname, admin identity), auto-detects the local model, writes docker-compose.yml + Caddyfile + a filled agami.env (referencing the PUBLISHED image ghcr.io/agamiai/agami-core — no clone, no build), and stages the model artifacts. Generates the signing secret via deploy_preflight; the admin password is typed by the user into the file (never in chat). Then runs `docker compose up` if Docker is local, otherwise prints the exact VM steps + the shareable MCP URL. Username/password auth only on this paved path.
The single dashboard for the active profile's semantic model — browse, curate, AND sign off the trust layer in one surface. Browse every subject area, table, field, metric, entity, and join with live search; edit descriptions/metrics/entities/joins; exclude tables/columns you don't want queried; add new metrics; edit ORGANIZATION.md. Its **Review tab** is the trust-layer sign-off queue: approve / reject the AI-proposed metrics (Rule 1 — a query using an unsigned metric still answers but carries a warning until it's approved), entities, and inferred joins (Rule 2 — lazy, usable while unreviewed). Every action is queued, submitted back to Claude as one feedback block, applied via the curation engine, and gated by the validator before it touches the YAML. (This skill absorbed the former `/agami-review`.)
Reconciles known (label, expected_value) numbers from an existing dashboard against agami's answers. Input can be a SCREENSHOT of a Metabase / Power BI / Tableau / Looker dashboard (Claude's vision extracts the pairs), a CSV, or numbers pasted inline — the user doesn't need to know which; they can just ask. For each pair, the skill generates a matching NL question, runs it through the active profile's semantic model, diffs actual vs expected, and surfaces matches in green and mismatches in red with drill-down receipts. The strongest onboarding demo for a skeptical data engineer — either we agree with their numbers (trust earned via evidence) or we surface a real definitional disagreement (trust earned via transparency).
Saves a user correction so future queries learn from it. Always appends a (question, corrected_sql) pair to the subject area's example library under <artifacts_dir>/<profile>/prompt_examples/<area>/. Additionally, classifies the correction and — when applicable — applies a surgical edit to the semantic model itself (relationship fix, column metadata, or new metric) via the curation engine. Every model edit is validated before write; the validator is the binding gate, and a failed validation reverts. Shows the user a model diff for approval before any model mutation.
Wires the local agami MCP server (python -m mcp_harness) into the Claude Desktop app in one step, so you can ask your database questions from Claude Desktop — not just inside Claude Code. Auto-detects the right Python interpreter (the one with your DB driver), installs the agami-core package into it so the registration survives plugin updates, and safely merges the entry into claude_desktop_config.json (backup + atomic write, preserving every other key). The local server is the mirror of the hosted Agami connector — same tools, local backend — so this is also how a developer feels the exact experience their business end-users would get.
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
The trust layer between AI and your data. Local. Private. Yours.
agami-core is the trust layer between an AI agent and your database — a governed, self-improving semantic model that enforces correct joins, signed-off metric definitions, and a full audit receipt on every answer. Same question, same answer, every time. It builds itself from your live schema, messy or clean. The rules live in the model, not the prompt.
Real enterprise schemas have thousands of tables, mostly undocumented, with columns named col_47 and three definitions of "revenue". That's the problem this solves.
In the Claude Code CLI:
/plugin marketplace add AgamiAI/agami-core
/plugin install agami-core@agami
/agami-connect sample # zero setup: no database, no credentials
who are the top 5 customers by total spend?
In VS Code or Cursor, the two
/plugin …commands above don't work from the chat input — type/pluginto open the Manage Plugins dialog and add the marketplace + install the plugin there instead (see Install). The/agami-connectline and everything after it work the same everywhere.
That last line returns a governed answer with a receipt (the exact SQL, the joins used, the model version) — and the governance runs before the query, so the kind of silent join mistake an ungoverned agent would hand back as a confident wrong number never reaches you. Two ways to go from here:
/agami-connect to introspect it into a governed semantic model, then just ask questions.Each path is walked through in full below (Quickstart · Install).
agami ships with Acme Store, a small local SQLite dataset (commerce + subscriptions) and a ready-made, signed-off semantic model. You get a governed answer — with a full receipt — in under a minute, and nothing leaves your machine.
# 1. Install the plugin (see Install below for the per-host steps).
# 2. Try the sample — no connection needed:
/agami-connect sample # or just say "I don't have a database" / "try the sample"
# 3. Ask a question — see governance ENFORCED:
who are the top 5 customers by total spend?
# 4. Now watch the model get BUILT — see governance MADE:
/agami-connect reintrospect
Step 3 is where the governance fires. The sample question is deliberately one an ungoverned agent gets confidently wrong — a multi-table join where a naive agent silently returns a bad number. agami's pre-flight catches it and returns the correct answer with a join receipt — the trust layer, enforced on your very first query.
npx claudepluginhub agamiai/agami-core --plugin agami-coreSkills and tools powered by the Honeydew MCP that help coding agents query data and build semantic models
MotherDuck skills for connecting, exploring live schemas, writing DuckDB SQL, using the REST API, and building dashboards, Dives, pipelines, and analytics apps.
Semantic SQL compiler — compile .view.yml schema definitions into dialect-specific SQL. Unix-philosophy CLI designed as a tool-use interface for LLMs.
Analytics engineering for Claude Code and any agent: data warehouse exploration, dbt transformation and semantic modeling, and schema-drift maintenance on dbt.
Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries.
Write SQL, explore datasets, and generate insights faster. Build visualizations and dashboards, and turn raw data into clear stories for stakeholders.