@gemmein/mcp

中文文档
0.21.1发布于 2026/11/15MITES Module近 30 天下载 2388

Gemmein MCP server — gives coding agents the Gemmein guide, API reference, rule/error explainers, what changed in each release, and a live integration check (reaffirm) as tools. Nine tools are read-only; check_integration writes test people and a probe re

原始使用文档
文档目录3 节
  1. Setup
  2. Tools
  3. The companion SDK

@gemmein/mcp

The Gemmein MCP server — gives your coding agent the whole Gemmein contract as tools, straight in the editor.

Gemmein is the backend for web and mobile apps: hosting, sign-in, protected data, payments, AI tools and a dashboard to run your customers. Ten tools work without an account. Nine are read-only, and all but guide work offline: guide makes one read-only GET to https://docs.gemmein.com/llms-dashboard.txt for the dashboard section. check_integration runs live checks against your app; with a development secret key it also writes in the development environment: it creates two test people and a probe record, deletes the record, and signs the test people out of earlier sessions. Without a secret key it writes nothing while the app's boundaries hold — but if a private collection is open to strangers, the anonymous test write succeeds and its record stays, in whatever environment the key names (live included), and the check fails, naming the collection.

Eleven more tools act on a linked Gemmein app — create_app, delete_app, the Views family (put_view, dev_view, live_view, dev_delete_view, view_action, view_add, view_edit, view_reorder) and dev_email_templates. Link the project once with npx gemmein login (a browser approval, 7 days); without a link these refuse, naming that command — no key is ever asked for in the chat.

Setup

Claude Code:

claude mcp add gemmein -- npx -y @gemmein/mcp

Cursor / any MCP client (mcpServers config):

{ "gemmein": { "command": "npx", "args": ["-y", "@gemmein/mcp"] } }

No terminal? The same tools are hosted at https://api.gemmein.com/mcp (MCP over Streamable HTTP, OAuth sign-in) — add it as a custom connector in ChatGPT, Claude, Lovable, Replit, Bolt or v0. The ten tools need no account. After your human approves the connection once, the hosted server also builds the app in Development (pull and sync the gemmein/ files, test members, test mail, sandbox test payments) and asks your human to approve each Live change in their browser; reading Live is a separate approval, and every read is on their Logs. Secret keys are shown once in the browser, never in the chat. On the hosted server, check_integration checks the API it runs on only.

Tools

  • guide — call first: it opens with two doors — an idea with nothing built yet, or an app that already exists — and both reach the same fit assessment (FITS / FITS EXCEPT / DOESN'T FIT — the verdict an agent delivers before any install), then the full builder's guide (auth flow, the eight collection safety rules, record shapes, links, uploads, contention patterns, payments, credits, AI tools, relays, mobile). The guide is the packaged contract — what code calls, matching the installed SDK. The dashboard section (connecting Stripe, the dashboard's rooms, health checks) is read live from docs.gemmein.com, because it changes with the dashboard; offline, the guide ends with a link to it instead. It ends with every docs page's markdown link; pass topic ("refund a payment") to get only the sections that answer it, each a direct link such as https://docs.gemmein.com/payments/refunds.md#refunds.
  • reference — the exact SDK API reference: every method, signature, return shape, error code. Pass topic ("checkout") for only the matching sections, with each section's direct link.
  • search_docs — the docs site's sections that answer a question, best first, each a direct markdown link with its anchor, then the matching passages of both packaged documents. Offline: the section index ships with the server.
  • changes — what changed in each Gemmein release after the version you knew (since), or the last three: every change as was → now, with the error codes it added or removed. Bundled, offline — call it when what you remember may be older than the installed release.
  • explain_rule — any safety rule's contract, what it's right for, and the mistakes to avoid (or a cheat-sheet of all eight).
  • explain_error — what a GemmeinError code means and exactly what to do, with the code's own page (https://docs.gemmein.com/errors/).
  • explain_relay — how a relay is written: its trigger, the thirteen action verbs (write_record, grant_access, revoke_access, grant_credits, email_person, call_url, run_function, start_run, spend_credits, fulfil_product, refund_product, grant_plan, revoke_plan), templates, and the refusals the engine answers.
  • validate_collection_name — catch a bad collection name at planning time (a bad name throws synchronously and can blank an app silently).
  • reaffirm_template — the ready-to-edit CI harness that proves an app's boundaries on every deploy.
  • check_integration — run those boundary checks live against your own app right now: anonymous access refused where it must be, cross-user isolation proven with throwaway dev test sessions, structured pass/fail back. Never pass a live secret key — sk_live is refused by design.

The following eleven need a linked project (npx gemmein login):

  • create_app — ask to make another app on the same account, in Development only. Your human approves it in their browser with the emailed code.
  • delete_app — ask to permanently delete this app: every record, customer, file, site, domain, relay, AI tool and key goes, and every active customer subscription is cancelled in Stripe at once. Your human approves it in their browser, types the app's name and enters the emailed code — this can't be undone, and no caller of this tool can skip either check.
  • put_view — create or update one Development view: a recipe over one collection (filter, sort, columns, totals, layout, action buttons).
  • dev_view / live_view — read one view's rows, exactly as its layout shows them, with totals and each row's open actions. live_view needs the live:read grant.
  • dev_delete_view — delete a view's recipe from Development; the collection and its records are untouched, and Live keeps its own copy for good.
  • view_action — move one record one step along a view's own action buttons. In Development it happens at once; with env: "live" your human approves it in their browser (no emailed code).
  • view_add / view_edit / view_reorder — add, edit or reorder a record through a view's own form, Development only.
  • dev_email_templates — list Development's saved email templates (name, version, which {{vars}} each takes), or, with name, one template's own full saved source for editing on the fly.

The companion SDK

Your app talks to Gemmein through @gemmein/sdk. This server teaches your agent to use it correctly.

MIT © Gemmein Limited

版本与发布记录

@gemmein/mcp 共发布 29 个版本,首次发布于 2026/07/20;过去 12 个月发布了 29 个版本。

版本发布日期距今
0.21.1latest2026/11/151 天前
0.21.02026/11/106 天前
0.20.12026/10/2720 天前
0.20.02026/10/2522 天前
0.18.02026/10/2225 天前
0.17.02026/10/1829 天前

关于 @gemmein/mcp 的常见问题

@gemmein/mcp 是什么?

Gemmein MCP server — gives coding agents the Gemmein guide, API reference, rule/error explainers, what changed in each release, and a live integration check (reaffirm) as tools. Nine tools are read-only; check_integration writes test people and a probe re

如何安装 @gemmein/mcp?

在项目目录运行 npm install @gemmein/mcp,或使用 pnpm add / yarn add / bun add。它还提供命令行工具 gemmein-mcp,可以用 npx gemmein-mcp 直接运行。

@gemmein/mcp 支持 TypeScript 吗?

该包的 package.json 没有声明类型入口。需要类型提示时,可以在 npm 上查找社区维护的 @types/gemmein__mcp 是否存在。

@gemmein/mcp 支持 ESM 还是 CommonJS?

以 ES Module 形式发布,推荐使用 import 引入。在 CommonJS 项目中,Node.js 20.19+ / 22.12+ 可以直接 require() 不含顶层 await 的 ES Module,更早的版本需要改用动态 import()。

@gemmein/mcp 需要什么版本的 Node.js?

package.json 的 engines 字段要求 Node.js >=20。版本不符时 npm 默认只给出警告,开启 engine-strict 后会拒绝安装。

@gemmein/mcp 可以商用吗?

@gemmein/mcp 使用 MIT 许可。宽松许可:允许商业使用、修改和再分发,通常只需在分发时保留原版权与许可声明。以上为概括,不构成法律意见,请以许可原文为准。

@gemmein/mcp 的下载量有多少?

根据 npm 官方下载统计,@gemmein/mcp 在 2026/10/16 – 2026/11/14 这 30 天内被下载 2,388 次,日均约 80 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@gemmein/mcp 还在维护吗?

最新版本 0.21.1 发布于 2026/11/15(1 天前);至今共发布 29 个版本,其中过去 12 个月发布了 29 个;首次发布于 2026/07/20。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。