DCL — DataClawe Command Language
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."
Power your agent
पब्लिशर का अपना URL। PlugMCP एंडपॉइंट नहीं।
Host a copy with our keys and logs.
https://mcp.dataclawe.com/sseऊपर दिया Claude बटन नाम और URL भरकर Claude खोलता है। पुष्टि आपको वहीं करनी होती है।
claude mcp add --transport http com.dataclawe-dataclawe-mcp https://mcp.dataclawe.com/sseRun in a terminal.
{ "mcpServers": { "com.dataclawe-dataclawe-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.dataclawe.com/sse" ] } }}claude_desktop_config.json
रिमोट URL या आपकी मशीन पर कमांड? दोनों इंस्टॉल में क्या अंतर है
PlugMCP पर चलाएँ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
लॉन्चपब्लिशर से
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."
AI-native database utility. Talk to your DB in plain language. No SQL. MySQL & PostgreSQL.
DCL (DataClawe Command Language) is an open standard for communicating with databases using simple JSON.
It is designed for:
DCL translates into native SQL internally. Your existing database does not change. Your existing application does not change.
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.
{
"dcl": "1.0",
"action": "SELECT",
"table": "users",
"columns": ["id", "name", "email"],
"where": [
"status = 'active'",
"age >= 20"
],
"order": "created_at DESC",
"limit": 10,
"offset": 0
}
{
"dcl": "1.0",
"action": "INSERT",
"table": "users",
"data": {
"name": "kimura",
"email": "[email protected]",
"status": "active"
}
}
{
"dcl": "1.0",
"action": "UPDATE",
"table": "users",
"data": {
"status": "inactive"
},
"where": [
"id = 123"
]
}
{
"dcl": "1.0",
"action": "DELETE",
"table": "users",
"where": [
"id = 123"
]
}
WHERE is an array of condition strings. Multiple conditions are AND by default.
"where": [
"status = 'active'",
"age >= 20",
"age <= 60",
"status != 'deleted'"
]
"where": {
"OR": [
"status = 'active'",
"status = 'pending'"
]
}
"where": {
"AND": [
"age >= 20",
{
"OR": [
"status = 'active'",
"status = 'pending'"
]
}
]
}
"where": [
"name LIKE 'kimura%'"
]
"where": [
"status IN ('active', 'pending')"
]
"where": [
"age BETWEEN 20 AND 60"
]
"where": [
"deleted_at IS NULL"
]
"where": [
"deleted_at IS NOT NULL"
]
{
"dcl": "1.0",
"action": "SELECT",
"table": "orders",
"columns": [
"SUM(amount) AS total",
"AVG(amount) AS average",
"COUNT(*) AS count"
],
"where": [
"status = 'paid'"
],
"group": "customer_id"
}
{
"dcl": "1.0",
"action": "COUNT",
"table": "users",
"where": [
"status = 'active'"
]
}
{
"dcl": "1.0",
"action": "EXISTS",
"table": "users",
"where": [
"email = '[email protected]'"
]
}
{
"dcl": "1.0",
"action": "SCHEMA",
"table": "users"
}
{
"dcl": "1.0",
"action": "TABLES"
}
Declares a new empty table. Internally creates a single status=8 schema declaration row.
{
"dcl": "1.0",
"action": "TABLE_CREATE",
"table": "users"
}
With optional schema definition:
{
"dcl": "1.0",
"action": "TABLE_CREATE",
"table": "users",
"schema": {
"name": "text",
"age": "integer",
"email": "text"
}
}
Without schema: Created with
schema: null. Column types are auto-registered astexton first INSERT.
DataClawe maintains one status=8 declaration row per table.
Example status=8 row content:
{
"schema": {
"name": "text",
"age": "text",
"email": "text"
}
}
Auto Schema Evolution:
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.
Returns record count, last updated timestamp, and storage size. Useful for AI agents to assess table state before operating.
{
"dcl": "1.0",
"action": "STATS",
"table": "users"
}
Example response:
{
"dcl": "1.0",
"status": "OK",
"data": {
"table": "users",
"record_count": 1024,
"last_updated": "2026-03-28T10:00:00Z",
"size_kb": 512
}
}
Returns the change history (created, updated, logical delete) of a record in chronological order. Useful for AI agents tracking data evolution.
{
"dcl": "1.0",
"action": "TIMELINE",
"table": "users",
"where": [
"id = 123"
]
}
Copies a table under a new name. Used for backups, migrations, and testing.
{
"dcl": "1.0",
"action": "TABLE_COPY",
"table": "users",
"target_table": "users_backup_20260328"
}
Renames a table.
{
"dcl": "1.0",
"action": "TABLE_RENAME",
"table": "users_old",
"new_name": "users_archived"
}
Logically deletes a table. Data is not physically removed immediately.
{
"dcl": "1.0",
"action": "TABLE_DROP",
"table": "users_temp"
}
Note: TABLE_DROP is a logical delete — not equivalent to SQL
DROP TABLE. Data is not immediately destroyed.
{
"dcl": "1.0",
"status": "OK",
"count": 42,
"data": [
{ "id": 1, "name": "kimura", "email": "[email protected]" }
],
"meta": {
"table": "users",
"elapsed_ms": 12
}
}
{
"dcl": "1.0",
"status": "ERROR",
"code": "TABLE_NOT_FOUND",
"message": "Table 'users' does not exist"
}
DCL works over two protocols. The DCL command itself is identical in both cases.
{
"dcl": "1.0",
"action": "SELECT",
"table": "orders",
"where": [
"status = 'pending'",
"created_at >= '2026-01-01'"
],
"order": "created_at DESC",
"limit": 100
}
This DCL JSON is the same regardless of whether you call via REST API or MCP. Only the outer protocol layer differs.
DCL normalizes differences between MySQL and PostgreSQL. You write one DCL command. DataClawe handles the rest.
DCL is designed in two layers. You choose the layer you need.
For AI agents, frontend engineers, and anyone doing straightforward data operations.
If Standard covers your needs, you never have to go further.
For backend engineers who need more expressive power.
Same JSON structure. Same DataClawe engine. More capability when you need it.
JOIN
{
"dcl": "1.0",
"action": "SELECT",
"table": "users",
"columns": ["users.id", "users.name", "orders.amount"],
"join": [
{
"table": "orders",
"on": "users.id = orders.user_id",
"type": "LEFT"
}
],
"where": [
"users.status = 'active'"
],
"order": "orders.amount DESC",
"limit": 20
}
Subquery
{
"dcl": "1.0",
"action": "SELECT",
"table": "users",
"where": [
"id IN (SELECT user_id FROM orders WHERE status = 'paid')"
]
}
Multiple JOINs
{
"dcl": "1.0",
"action": "SELECT",
"table": "orders",
"columns": [
"orders.id",
"users.name AS customer",
"products.name AS product",
"orders.amount"
],
"join": [
{
"table": "users",
"on": "orders.user_id = users.id",
"type": "INNER"
},
{
"table": "products",
"on": "orders.product_id = products.id",
"type": "LEFT"
}
],
"where": [
"orders.status = 'paid'",
"orders.created_at >= '2026-01-01'"
],
"order": "orders.created_at DESC"
}
JOIN types supported in Advanced
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.
The following are out of scope in both Standard and Advanced, to keep DCL safe and predictable for AI agents:
ALTER TABLEDROP TABLE equivalent)Note:
TABLE_DROPin DCL is a logical delete — distinct from SQLDROP TABLE. It does not immediately destroy data.
DCL is a data operation language, not a schema management language.
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.
DCL is an open specification. Feedback, proposals, and pull requests are welcome.
v1.0 — DCL Standard
dcl.schema.json)v1.1 — DCL Advanced
SDKs
DataClawe uses a tiered pricing model that scales from individual developers to enterprise.
Initial registration fee: $20 (one-time, all plans)
Usage rates (Business plan — overage)
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.
For Enterprise pricing, contact us at dataclawe.com/enterprise.
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.
DCL specification is released under Creative Commons Attribution 4.0 International (CC BY 4.0).
You are free to implement, extend, and build upon this specification. Attribution to DataClawe is appreciated.
DCL v1.1 — 2026 — DataClawe Project
AI-native database utility. Talk to your DB in plain language. No SQL. MySQL & PostgreSQL.
{ "mcpServers": { "com.dataclawe-dataclawe-mcp": { "url": "https://mcp.dataclawe.com/sse", "headers": {} } }}टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए http कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
DataClawe — Database As A Utility तक HTTP से पहुँचा जाता है।
पिछली जाँच 2026-11-08 को हुई। AI-native database utility. Talk to your DB in plain language. No SQL. MySQL & PostgreSQL.