Commercient Data Lake / Use with AI & MCP

Claude Code, Claude, and any MCP agent — on your business data

The Data Lake speaks MCP (Model Context Protocol) natively, so AI agents connect the same way they connect to any modern tool — with one URL and one revocable key. Two planes are exposed: a data plane for querying and writing the entities you allow, and a governed admin control plane for operating the platform itself.

Connect Claude Code

One command adds your Data Lake as an MCP server in Claude Code:

# your key is "tenant:dlk_..." - mint one with `dlake keys create` or in the console
claude mcp add datalake https://datalake-ms-dab.commercient.com/mcp \
  --transport http --header "X-API-Key: yourtenant:dlk_..."

# optional: the admin control plane as a second server (Admin-role key required)
claude mcp add datalake-admin https://datalake-ms-dab.commercient.com/admin \
  --transport http --header "X-API-Key: yourtenant:dlk_..."

From that moment Claude Code can list your entities, query and update records, run aggregates, export tables, and — through the admin plane — build schema, manage API keys, drive the setup wizard, and operate the CRMPro and TxDownloaderPro sync legs. Ask in plain language; the tools self-describe.

Connect Claude (Desktop or claude.ai)

Add a custom connector with the same URL and key. If you prefer the tenant in the URL, use the per-tenant form:

Plane	Generic URL (tenant from the key)	Per-tenant URL
Data	`https://datalake-ms-dab.commercient.com/mcp`	`.../auth/{tenant}/mcp`
Admin	`https://datalake-ms-dab.commercient.com/admin`	`.../auth/{tenant}/admin`

What an agent can do

Query & write data

Read, filter, aggregate, and update the entities your key allows — live ERP, CRM, and database records, with row-level security applied in the database on every call.

Manage the platform

The admin plane exposes the full operating surface as tools: schema and views, API keys, imports and connectors, webhooks, the registration wizard, and the CRMPro / TxDownloaderPro sync configuration.

Learn the platform by itself

Built-in agent skills teach an agent the correct command ordering and the gotchas. An agent can fetch them live over MCP — list_skills, then get_skill — so its knowledge is always current.

Governance built in

Every agent connection is an API key you minted: scope it to specific entities and fields, revoke it at any time (effective immediately), and audit everything it did. Admin-plane tools additionally require the key's user to hold the Admin role — an agent with a regular key can query data but cannot reconfigure the platform.

Getting help

Ask the agent to call get_help_docs or get_api_guide over MCP for the full platform guides, or list_skills / get_skill for the task-oriented skills. From the CLI the same content is dlake guide help, dlake guide api and dlake skills show <name> — and the console has a Help section with the complete product guide.