@gemmein/mcp

@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 AI-built web apps: passwordless auth, structured storage with plain-English safety rules, and built-in Stripe subscription handling. This server is read-only: it never creates, edits, or deletes anything on the platform.

Setup

Claude Code:

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

Cursor / any MCP client (mcpServers config):

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

Tools

• guide — call first: it opens with the 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 seven collection safety rules, record shapes, links, uploads, contention patterns, payments).
• reference — the exact SDK API reference: every method, signature, return shape, error code.
• search_docs — targeted search over both documents.
• explain_rule — any safety rule's contract, what it's right for, and the mistakes to avoid (or a cheat-sheet of all seven).
• explain_error — what a GemmeinError code means and exactly what to do.
• 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 companion SDK

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

MIT © Gemmein Limited