Local-first, policy-gated MySQL/MariaDB and SQLite access for AI agents: native Rust MCP server, CLI and GUI
sequel-mcp demonstrates solid foundational quality with 23 well-named tools covering database operations, policy management, and audit trails. All tools have descriptions (10-200 chars, within baseline range) and explicit input schemas with typed parameters. However, output schemas are not documented in the visible code, parameter descriptions lack depth (many are 1-2 sentences without format/constraint details), and error handling guidance is minimal. Security-sensitive tools (execute, restore_backup) lack confirmation/dry-run patterns despite destructive risk. Tool composition is sound, each tool has one responsibility, but some parameter relationships (e.g., policy object structure) are underdocumented.
Add a MySQL/MariaDB connection
Add a SQLite connection
Clean up audit log based on retention policy
Describe a table schema
Run a non-read SQL statement (INSERT/UPDATE/DELETE/DDL/admin). Subject to the two-layer policy: table-rule elevation still requires user confirmation.
Explain a SQL statement
Get policy for a database
Get policy for a table
Output schemas not documented. Tools return results but LLMs cannot see expected field structure, forcing them to infer response shape and risking downstream tool chaining failures.
Policy parameter descriptions lack detail. 'Partial policy object' does not explain what fields are valid, constraints, or examples. LLMs cannot construct valid policy payloads without trial-and-error.
Destructive tools (execute, restore_backup, cleanup_audit) lack dry-run or confirmation patterns. Agents can accidentally delete data or restore wrong backups without safeguards.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | <=2025-11-25 | v2 |
Import connections and history from Sequel Ace
List available backups
List all configured connections
Run a single read-only SQL statement (SELECT/SHOW/DESCRIBE/EXPLAIN, plus read-only SQLite PRAGMA). SQLite opens a read-only file handle.
Remove a connection
Restore from a backup
Search audit log
Search command history
Search Sequel Ace query history
Select a database for the connection
Set policy for a connection
Set policy for a database
Set the default connection
Set retention policy for audit and backups
Set policy for a table
Parameter format constraints not documented. SSH parameters (ssh_host_key_policy, ssh_docker_bridge_tool) accept enums but descriptions do not list valid values. LLMs must guess or fail.
Error handling guidance absent. Tools return errors but do not guide LLMs on recovery (retry, lookup, ask user). Agents cannot self-correct on failures.