A JSON-based database command standard for AI agents, frontend engineers, and anyone who finds SQL too complex.
"If you understand MySQL and MSX-BASIC, you already understand DCL."
What is DCL?
DCL (DataClawe Command Language) is an open standard for communicating with databases using simple JSON.
AI-native database utility. Talk to your DB in plain language. No SQL. MySQL & PostgreSQL.
2026-11-08
星數
—
工具
—
可用率
—
It is designed for:
AI agents (Claude, GPT, Cursor, and others) to safely read and write structured data
Frontend engineers who need database access without writing SQL
MCP (Model Context Protocol) tool integration
Any application connecting to MySQL or PostgreSQL — legacy or new
DCL translates into native SQL internally. Your existing database does not change. Your existing application does not change.
Design Philosophy
DCL follows three rules:
1. If you can read it, you understand it.
No cryptic operators. No framework-specific syntax. No : chaining.
2. MySQL words. JSON structure.
Actions like SELECT, INSERT, UPDATE, DELETE are exactly what you expect. WHERE conditions are written the way MySQL engineers already write them.
3. MSX-BASIC level simplicity.
If a condition like age >= 20 needs an explanation, the design has failed.
4. Simple by default. Powerful when needed.
Standard covers most real-world needs. Advanced covers the rest. You never pay the complexity cost until you need it.
Writing to a non-existent table via INSERT auto-creates the status=8 row.
New columns are automatically appended to the status=8 schema on each INSERT (type defaults to text).
First INSERT: {"name": "kimura", "age": 25}
→ Auto-create status=8: {"name":"text", "age":"text"}
→ INSERT the record
Second INSERT: {"name": "suzuki", "phone": "090-xxxx"}
→ "phone" is new → auto-append to status=8 schema
→ schema: {"name":"text", "age":"text", "phone":"text"}
When connecting to legacy MySQL/PostgreSQL, actual column types (VARCHAR(255), INT, etc.) are recorded in the status=8 row.
STATS — Table statistics
Returns record count, last updated timestamp, and storage size. Useful for AI agents to assess table state before operating.
SQL solved everything in one spec.
That is why SQL is still hard after 30 years.
DCL Standard is for everyone.
DCL Advanced is for when you need more.
You always start simple. You go deeper only when you must.
The same engine handles both. The same JSON structure. No new syntax to learn when you move from Standard to Advanced — just new keys.
What remains intentionally unsupported
The following are out of scope in both Standard and Advanced, to keep DCL safe and predictable for AI agents:
Stored procedures
Schema creation or ALTER TABLE
Raw SQL passthrough
Physical schema destruction (immediate DROP TABLE equivalent)
Note:TABLE_DROP in DCL is a logical delete — distinct from SQL DROP TABLE. It does not immediately destroy data.
DCL is a data operation language, not a schema management language.
Versioning
The "dcl": "1.0" field is required in every request and response.
Future versions will remain backward compatible. A DCL 1.0 request will always work against a DCL 2.0 server.
Contributing
DCL is an open specification. Feedback, proposals, and pull requests are welcome.
Open an issue to propose a new action or operator
Open a pull request to improve documentation or examples
All contributions must follow the design philosophy: readable, MySQL-familiar, BASIC-level simplicity
Roadmap
v1.0 — DCL Standard
Spec finalization
JSON Schema for validation (dcl.schema.json)
Reference implementation in Go (DataClawe Engine)
MCP server reference implementation
MySQL wire protocol support
Multi-tenant isolation specification
v1.1 — DCL Advanced
JOIN specification (INNER / LEFT / RIGHT)
Subquery support
Nested aggregation
SDKs
JavaScript / TypeScript
PHP
Python
Go
Pricing
DataClawe uses a tiered pricing model that scales from individual developers to enterprise.
Initial registration fee: $20 (one-time, all plans)
Plan
Monthly
Records
Sessions
SLA
Free
$0
2,000
100/day
No
Personal
$20
up to 20,000
up to 20,000/month
No
Business
$20+
Unlimited
Unlimited
No
Enterprise
Contact us
Unlimited
Unlimited
Yes
Usage rates (Business plan — overage)
Item
Unit price
Record storage
$0.001 / record / month
Session
$0.001 / session
Record size limit: 100KB per record.
This covers IoT sensor data, CRM contacts, medical text records, WordPress posts, and financial transactions.
Images and video files are out of scope — store them in CDN/object storage and keep the URL in DataClawe.
DCL is developed as part of the DataClawe project.
DataClawe is a database translation engine that connects legacy MySQL and PostgreSQL systems to AI agents, LLM pipelines, and cloud-native services — without rewriting the original system.
DCL is the command language that makes this connection possible for everyone, not just database engineers.
Legacy systems should not be destroyed. They should be translated.