Supabase
by supabase
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
Computer or cloud★ 2,993Apache-2.0Updated yesterday
Install
Mini App MCP
Overview
Description from the maker (original English)
Agent-First CRUD store MCP server — 1 daemon per table, schema.yaml driven, SQLite backend
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Databases & datasets
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- DockerDocker installed
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"mini-app": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/ynishi/mini-app-mcp:0.20.0"
]
}
}
}Run this in your terminal
claude mcp add mini-app -- docker run -i --rm ghcr.io/ynishi/mini-app-mcp:0.20.0Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mini-app": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/ynishi/mini-app-mcp:0.20.0"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"mini-app": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/ynishi/mini-app-mcp:0.20.0"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account ynishi, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Databases & datasetsi
- More stars than 0% of the other 1141 servers in this category
- Published to the registry more recently than 70% of the other 1141 servers in this category
- Basic checks equal to or better than 100% of the other 1141 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Mini App MCP safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.20.0) reached the registry 17 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
What can I use instead?
In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MongoDB MCP Server
by mongodb-js
MongoDB Model Context Protocol Server
Runs on your computer★ 1,157Apache-2.0Updated 3 days ago
Install
Elasticsearch MCP Server
by cr7258
MCP server for interacting with Elasticsearch
Runs on your computer★ 315Apache-2.0Updated 14 months ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.yaml` as 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
table: issuestitle: "Issue tracker" description: "Tracks bugs and feature requests for a project." fields:
- name: title type: string required: true description: "Short one-line summary of the issue."
- name: state type: string required: false
- name: tags type: array required: false
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 .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 /_snapshots/ . .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. |
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 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.
| URI | MIME | Content |
|---|---|---|
schema://yaml | application/yaml | Raw schema.yaml file content (read from disk on each request) |
schema://json | application/json | Parsed SchemaConfig as JSON (same shape the info tool returns) |
schema://json-schema | application/schema+json | JSON Schema (draft-07) derived from the schema's fields. Use this to validate data arguments before calling create / update |
docs://quickstart | text/markdown | Agent quickstart (mode detection + first-call recipe + pointers to the other docs:// resources), compiled into the binary. Distinct from this human-facing README — read this resource from inside the MCP session |
docs://tools | text/markdown | Cheat sheet of all 17 MCP tools and their input shapes |
docs://errors | text/markdown | Reference table of error codes returned by the server |
docs://filters | text/markdown | Guide for constructing filter objects (Eq/In/Like/Or/And) used by list and alias_create |
The info tool and schema://json resource return equivalent content but serve different purposes: info is a callable tool (good for one-off introspection in a conversation), while resources are URI-addressable and can be subscribed to or cached by the client.
Usage
Start the server via --mcp (stdio transport) or --mcp-http (streamable HTTP transport). These are the only entry points; there is no REST/CLI-CRUD surface.
Multi-table mode
Place each table's schema.yaml and .db under ~/.mini-app/ / (User scope) or ./.mini-app/ / (Project scope), then start without any extra environment variables:
mini-app-mcp --mcpRegister it once in .mcp.json to serve all mounted tables:
{"mcpServers": { "mini-app": { "command": "mini-app-mcp", "args": ["--mcp"] } } }
Multi-device mode (streamable HTTP)
Run one central daemon that owns the SQLite files, and connect from any number of devices as remote MCP clients. Because every device talks to the same single process, the single-writer storage model is preserved — no cross-device sync or conflict handling exists or is needed.
# Central host — loopback (same-machine clients, e.g. behind an SSH tunnel)mini-app-mcp --mcp-http # default bind 127.0.0.1:8484
Central host — LAN exposure requires a token (generate one once):
openssl rand -hex 32
MINI_APP_HTTP_TOKEN= mini-app-mcp --mcp-http --bind 0.0.0.0:8484
Client registration in .mcp.json (any device on the network):
{"mcpServers": { "mini-app": { "type": "http", "url": "http://central-host:8484/mcp", "headers": { "Authorization": "Bearer " } } } }
Security model:
- Loopback bind (default):
MINI_APP_HTTP_TOKENis optional. The transport's built-inHostheader validation (loopback-only) guards against DNS rebinding. - Non-loopback bind:
MINI_APP_HTTP_TOKENmust be set — startup is refused otherwise. Every request must then carryAuthorization: Bearer. - Transport encryption (TLS) and any richer authorization are intentionally out of scope; terminate TLS at a rev
Only the beginning is shown; read the rest in the repo