AI-native database utility. Talk to your DB in plain language. No SQL. MySQL & PostgreSQL.
MCPpedia last refreshed this data
com.dataclawe/dataclawe-mcp is an MCP server that AI-native database utility. Talk to your DB in plain language. No SQL. MySQL & PostgreSQL. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 57/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"com-dataclawe-dataclawe-mcp": {
"url": "<see-readme-for-url>"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
AI-native database utility. Talk to your DB in plain language. No SQL. MySQL & PostgreSQL.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in data
Token-efficient database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, SQLite
Manage Supabase projects — databases, auth, storage, and edge functions
A cross-platform desktop application for managing AI Agents and MCP Servers. 一款用于管理AI智能体与MCP服务器的跨平台桌面应用程序。
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
MCP Security Weekly
Get CVE alerts and security updates for com.dataclawe/dataclawe-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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."
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": "kimura@example.com",
"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"
]
}
| Action | Description | Read-only |
|---|---|---|
SELECT | Fetch one or more records | ✅ |
COUNT | Count matching records | ✅ |
EXISTS | Check if a record exists | ✅ |
SCHEMA | Get column definitions for a table | ✅ |
TABLES | List all available tables | ✅ |
STATS | Get record count, last updated, and storage size | ✅ |
TIMELINE | Get chronological change history of a record | ✅ |
INSERT | Create a new record | ❌ |
UPDATE | Update existing records | ❌ |
DELETE | Logical delete (status flag) | ❌ |
TABLE_CREATE | Create a new table (empty declaration) | ❌ |
TABLE_COPY | Copy a table | ❌ |
TABLE_RENAME | Rename a table | ❌ |
TABLE_DROP | Logical delete a table | ❌ |
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
... [View full README on GitHub](https://github.com/DataClawe/dcl-spec#readme)