Mini App MCP

Name: Mini App MCP
Author: ynishi

作者：ynishi版本 0.20.0i★ –i在你的电脑上运行

注册名称io.github.ynishi/mini-app-mcp

安装

概览

作者提供的说明（英文原文）

Agent-First CRUD store MCP server — 1 daemon per table, schema.yaml driven, SQLite backend

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 数据库与数据集

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

Docker已安装 Docker

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "mini-app": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/ynishi/mini-app-mcp:0.20.0"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add mini-app -- docker run -i --rm ghcr.io/ynishi/mini-app-mcp:0.20.0

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "mini-app": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/ynishi/mini-app-mcp:0.20.0"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "mini-app": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/ynishi/mini-app-mcp:0.20.0"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 ynishi 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“数据库与数据集”中的其他服务器比较i

星标数多于此分类中其他 1141 个服务器的 0%
发布到注册中心的时间比此分类中其他 1141 个服务器的 70% 更新
基础检查结果等于或优于此分类中其他 1141 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Mini App MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.20.0）于17天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。

有什么可以替代它？

同一分类中有：Supabase, MongoDB MCP Server, Elasticsearch MCP Server

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Supabase

作者：supabase

MCP server for interacting with the Supabase platform

电脑或云端★ 2,993Apache-2.0昨天更新

安装

MongoDB MCP Server

作者：mongodb-js

MongoDB Model Context Protocol Server

在你的电脑上运行★ 1,157Apache-2.03天前更新

安装

Elasticsearch MCP Server

作者：cr7258

MCP server for interacting with Elasticsearch

在你的电脑上运行★ 315Apache-2.014个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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 code field so agents can handle failures programmatically.

schema.yaml format

table: issues

title: "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 --mcp

"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_TOKEN is optional. The transport's built-in Host header validation (loopback-only) guards against DNS rebinding.
Non-loopback bind: MINI_APP_HTTP_TOKEN must be set — startup is refused otherwise. Every request must then carry Authorization: Bearer .
Transport encryption (TLS) and any richer authorization are intentionally out of scope; terminate TLS at a rev

只显示了开头部分；其余内容请在仓库中阅读