Agent-First CRUD store MCP server — 1 daemon per table, schema.yaml driven, SQLite backend
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Choose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Documentation Overview
mini-app-mcp
Agent-First CRUD store MCP server — schema.yaml driven, SQLite backend, multi-table in a single daemon.
What it does
mini-app-mcp is a lightweight MCP server that manages one or more SQLite tables in a single running process. The shape of each table is defined entirely by a schema.yaml file; no migrations, no REST API, no GUI. CRUD is exposed exclusively as MCP tools, making it a natural backend for agents that need structured persistent storage.
Design principles
schema.yamlas sole schema authority — field names, types, and required constraints are read from YAML at startup. No field is hard-coded in application code.- Multi-table in one daemon — a single server process discovers and mounts all tables found under the configured User and Project scope directories. A dedicated legacy mode (
MINI_APP_SCHEMA+MINI_APP_DB) preserves the original single-table behaviour. - MCP-only entry point — there is no HTTP/REST/CLI CRUD interface. All reads and writes go through MCP tools.
- Structured JSON errors — every error response carries a machine-readable
codefield so agents can handle failures programmatically.
schema.yaml format
The optional title and description keys at the table level provide human- and AI-readable metadata about the table. Each field entry may also carry an optional description string. All three keys follow the OpenAPI 3.1 / JSON Schema 2020-12 naming convention and are included in info tool output and the schema://json resource.
Supported types: string, number, boolean, array, object.
Configuration
Multi-table mode (recommended)
| Environment variable | Default | Description |
|---|---|---|
MINI_APP_USER_DIR | ~/.mini-app/ | Base directory for User-scope tables. Each subdirectory is treated as a table name and must contain schema.yaml and <table>.db. |
MINI_APP_PROJECT_DIR | ./.mini-app/ | Project-scope override directory. A table present here fully replaces the User-scope definition of the same name. |
MINI_APP_BACKUP_RETENTION | 10 | Maximum number of backup copies (YAML + DB snapshot pairs) to retain per table under _backup/. Older copies beyond this limit are deleted immediately after each backup write. |
MINI_APP_SNAPSHOT_RETENTION | 10 | Maximum number of snapshot generations to retain per table under _snapshots/. Strictly separate from MINI_APP_BACKUP_RETENTION; purges only _snapshots/ files and never touches _backup/. |
Tables are discovered at startup by scanning both directories. Project-scope definitions take precedence over User-scope definitions for the same table name.
Legacy single-table mode
| Environment variable | Default | Description |
|---|---|---|
MINI_APP_SCHEMA | ./schema.yaml | Path to the schema definition file |
MINI_APP_DB | (none — must be set) | Path to the SQLite database file |
When MINI_APP_SCHEMA and MINI_APP_DB are set the server starts in legacy mode, mounting exactly one table. The table argument on all tools may be omitted in this mode.
All variables can also be placed in a .mini-app-mcp.env file in the working directory.
MCP tools
All tools accept an optional table argument that selects the target table. In multi-table mode the argument is required; omitting it returns error code TABLE_REQUIRED. Supplying an unknown table name returns error code TABLE_NOT_FOUND. In legacy single-table mode the argument may be omitted.
| Tool | Description |
|---|---|
info | Returns the parsed schema (table name, field definitions) as JSON |
create | Inserts a new row; validates the data object against the schema |
get | Retrieves a single row by id. If id is shorter than 36 characters it is treated as a UUID prefix: zero matches return NOT_FOUND; two or more matches return AMBIGUOUS_ID with a candidate list. A full 36-character UUID always uses the exact-match path. Accepts an optional fields selector to project the returned data object to a named subset of schema fields. |
list | Returns rows with optional limit / offset pagination. Accepts an optional fields selector to project the returned data objects to a named subset of schema fields. |
update | Updates an existing row by id. If id is shorter than 36 characters it is treated as a UUID prefix (see get for resolution rules). Default mode is merge (RFC 7396): absent fields are preserved from the stored row, null values delete optional fields or raise a Validation error for required ones. Pass "mode": "replace" for full replacement (pre-0.9 behaviour). |
delete | Removes a row by id. If id is shorter than 36 characters it is treated as a UUID prefix (see get for resolution rules). |
reload | Re-scan MINI_APP_USER_DIR / MINI_APP_PROJECT_DIR and atomically replace the table registry. Legacy MINI_APP_SCHEMA + MINI_APP_DB are re-applied if set. Returns { mounted, added, removed }. Limitations: no file watcher (explicit invocation only); whole-registry replace (no per-table partial reload); no schema migration for existing rows; concurrent reload calls are last-write-wins. |
schema_create | Create a new schema.yaml under the specified scope (project or user) and register the table live. Pass dry_run: true to preview without writing. Fails with SCHEMA_EXISTS if the table already exists. |
schema_update | Replace an existing table's schema.yaml with a new definition (full overwrite). Backs up the previous YAML and a SQLite snapshot to _backup/ before writing. Pass dry_run: true to preview field changes without touching disk. |
schema_delete | Remove a table's schema.yaml (moved to _backup/) and unregister it from the live registry. Does not alter or drop the SQLite table — DDL changes remain the operator's responsibility. Pass dry_run: true to preview. |
schema_batch | Execute an array of ops[] atomically under a single SQLite SAVEPOINT. Any op failure rolls back all preceding ops, leaving YAML and DB untouched. All ops must target the same table. Returns per-op results or a BATCH_ABORTED error with the index of the failing op. |
data_snapshot | Create a point-in-time SQLite snapshot of one or all mounted tables using the SQLite hot backup API. Snapshots are written to <scope_root>/_snapshots/<table>.<unix_secs>.db. Pass table and/or scope to limit the target set; omit both to snapshot all mounted tables. Pass dry_run: true to preview the operation (target tables, row counts, would-purge count) without creating any files. Retention is controlled by MINI_APP_SNAPSHOT_RETENTION (default 10), independent of MINI_APP_BACKUP_RETENTION. |
row_materialize | Write one or more rows to arbitrary absolute paths on the local filesystem. Select rows by id or by a ListFilter expression. Choose output format (raw, markdown, json, yaml), field projection (All or a named subset), and whether to write one file per row (concat=false, default) or concatenate all rows into a single file (concat=true). Returns { count, files: [{path, bytes, sha256, row_id}] } — every file entry includes a SHA-256 hex digest of the written bytes. Pass dry_run: true to compute results without writing. |
alias_create | Register a named query alias for a table. Accepts name, either filter (a ListFilter expression) or filter_template (a MiniJinja template string — mutually exclusive with filter), optional params_schema (array of parameter name strings for a templated alias), optional default_limit, and optional description. Alias names are unique per table; duplicate names return ALIAS_ALREADY_EXISTS. Aliases are scoped per table and stored in the table's own SQLite database. |
alias_list | Return all aliases registered for a table as a JSON array of { name, filter, default_limit, description, params_schema } objects. |
alias_run | Execute a stored alias by name. Accepts optional runtime limit and offset that override the stored default_limit at call time. For parameterized aliases (those created with filter_template), also accepts a params object whose key-value pairs are injected into the template. Accepts an optional fields selector to project the returned data objects to a named subset of schema fields. If params_schema is set and params is omitted, returns ALIAS_PARAMS_REQUIRED. Template render failures return ALIAS_TEMPLATE_ERROR. Returns the same shape as the list tool. Returns ALIAS_NOT_FOUND for an unknown name. |
alias_delete | Delete a named alias for a table. Returns ALIAS_NOT_FOUND if the alias does not exist. |
MCP resources
In addition to the 17 tools above, the server exposes 7 read-only Resources addressable by URI. Resources are intended for agents that want to fetch the schema definition or reference documentation without invoking a mutating tool.
Related MCP Servers
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Mini App MCP
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/mini-app-mcp)HTML Embed
<a href="https://allmcps.com/mcp/mini-app-mcp"><img src="https://allmcps.com/api/badge/mini-app-mcp?style=directory" alt="Mini App MCP on AllMCPs" /></a>Technical Specs & Signals
CategoryDatabases
27Quality signal: Emerging · 27/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership8/20
Documentation & tools11/30
Adoption & activity1/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.