Agents Index

Gemmein

Online

Gemmein docs, API reference, error explainers and a live integration check for coding agents.

Visit publisherConnectJSON

What it can do: 80 tools

  • guide read-onlyReturns the Gemmein build guide (llms.txt): the packaged contract — what code calls, matching the installed SDK. Useful before building an app on Gemmein, moving an existing app onto it, or deciding whether an app fits.
  • changes read-onlyReturns what changed in each Gemmein release newer than `since` (a Gemmein version, e.g. "0.22.1"), or the last three when `since` is left out: each change as was → now, with the error codes it added or removed. Useful w
  • reference read-onlyReturns the @gemmein/sdk API reference (REFERENCE.md): every method, exact signature, return shape, and the stable error-code table. Useful while writing code against the SDK. With `topic` (a module or method: "g.collect
  • search_docs read-onlySearches the Gemmein docs for one term or phrase ('keyed create', 'ifVersion', 'addressed', 'expand') without reading a whole document. Returns the docs site's matching sections first, best first — each a direct markdown
  • explain_rule read-onlyExplains one of the eight collection safety rules (private, shared, admin_write, public_read, community, addressed, direct, app_only): its exact access contract, what it is right for, and the mistakes that leak data. Use
  • explain_error read-onlyExplains a GemmeinError code (err.code: conflict, forbidden, unknown_collection, invalid_shape, html_not_allowed, …): what the code means and the exact next step — including whether the refusal is final (a forbidden repe
  • validate_collection_name read-onlyChecks a collection name against the naming law: lowercase letters, numbers, underscores; starts with a letter; 2-63 characters. Useful while planning collections, before any g.collection(name) call is written: a bad nam
  • reaffirm_template read-onlyReturns reaffirm.mjs, the ready-to-edit harness that re-proves the app's boundaries against live Gemmein on every deploy (also shipped inside the @gemmein/sdk package): copied next to the app with its CONFIG block set, i
  • explain_relay read-onlyValidates a relay definition — the contents of gemmein/relays/<name>.json — offline, before `gemmein sync` carries it to the cloud. A relay is the secure boundary for three jobs. React, nothing charged: a receiver (a pro
  • check_integrationRuns the reaffirm boundary checks live against the caller's own app on this Gemmein; returns structured pass/fail (structuredContent: checks, notes, failedCount, passed). Useful once the app is wired to Gemmein, when con
  • app_status read-onlyReturns the app this connection is approved for: its name, its Development public key (pk_ — public by design, the key the app's code uses; no secret key is ever returned here), whether it is live, and what going live st
  • tools_map read-onlyReturns a map of this connector's tools, in eight groups (start, build, test_dev, site, ask_live, read_live, customers, keys_and_billing): each group's purpose in one line, then each tool with a one-line "use it when…".
  • pull read-onlyReturns what the app's Development holds as the gemmein/ file set (path → contents): its name, every collection's declaration, payments.json, relays, AI tools and aliases, email templates. Useful in a project that has no
  • keys_list read-onlyLists every server key this app has — name, environment (development or, once live, live too), who made it, its access (collections and powers, never a Development/Live-wide "all" granted lightly) and when it was last us
  • waiting_review read-onlyReads one post a test member wrote to a moderated collection ("publishing": "owner approves") before it's approved or sent back — its fields and its version (deciding it — approve or send back — is `npx gemmein approve`/
  • syncDoes what `npx gemmein sync` does, for an AI app with no terminal: takes the gemmein/ files' contents (path → text) and Gemmein applies them to Development through the same doors and validators — collections, payments, r
  • declare_collectionCreates or updates one collection in Development from its declaration — exactly the JSON of gemmein/collections/<name>.json ({ rule, fields, unlockedBy, publishing, openFields, lockedFields, directInitiation, rankable })
  • put_recordCreates one record in a Development collection — the same back-office write the dashboard's own Add row makes. Owned/addressed/direct collections take ownerUserId/audienceUserId (a Development person's id). Once the app
  • update_recordUpdates one Development record by id — the same door the dashboard's own edit sheet uses. data patches by default (a field left out is untouched); replace: true writes the whole document (a field left out is removed). On
  • dev_delete_recordDeletes one Development record by id — the same door the dashboard's own delete button uses. Once the app is live, request_delete_record asks the founder instead.
  • publish_recordPublishes or unpublishes one Development record by id, on a collection with its own draft/published chip — the same door the dashboard's own chip uses. Once the app is live, request_publish_record asks the founder instea
  • set_paymentsSets Development's plans and products from gemmein/payments.json's contents ({ plans, products, consent, mappings }). The file wins: a row edited in the dashboard is overwritten, and the answer lists every change first.
  • put_relayCreates or updates one relay in Development from gemmein/relays/<name>.json's contents ({ name, trigger, actions }); explain_relay validates the same definition offline. A signing or receiver secret Gemmein makes for it
  • put_ai_toolCreates or updates one AI tool in Development from gemmein/ai/tools/<name>.json's contents (label, provider, model or alias, credits, kind, instructions, inputs, bounds…). On an existing tool the dashboard's commerce (la
  • put_ai_aliasCreates or repoints one model alias in Development (gemmein/ai/aliases.json's { name: { provider, model } }).
  • put_email_templateSaves one email template in Development: name is sign-in (content = sign-in.json's JSON: logoUrl, brandColour, backgroundColour, appName, greeting), purchase, plan-start, notify or inbox-reply (content = the HTML). The s
  • put_viewCreates or updates one view in Development from gemmein/views/<name>.json's contents ({ collection, filter?, sort?, columns?, totals?, layout, actions? }): one collection, a filter in the owner's own timezone, sort, the
  • rename_appNames the app (it titles the customers' sign-in emails). Before go-live it is Development's and changes at once; once live, the founder approves it in the browser (request_rename_app).
  • test_member_addMakes a test member <name>@<tag>.gemmein.test in Development — their sign-in codes and every email the app sends them land in test_mail, never a real inbox. Test members sign in through the app's real screens and show th
  • test_mail read-onlyReads the test kit's mailbox: sign-in codes and every email the app sent test members (subject, text, headers, SPF/DKIM/DMARC as Gemmein signs it). to = a member's name; latest = only the newest. An email's text comes ba
  • prove_appProves on the server what a chat can't: Gemmein signs in as two of the app's test members (the first two test_member_add made, or the two named; never a real person, and no key passes through the chat) and runs the stand
  • test_run_ai_toolSends one AI tool on provider external (a pipeline — your own server runs it) a test run: every declared input gets a placeholder value, and Gemmein signs and posts the hand-off to the tool's own URL, the same way a real
  • test_payPays for a plan or product as a test member through the app's real checkout in Stripe's sandbox (test mode), to prove what the app does after a payment. outcome names what to prove: pays (a paid purchase), declined (Stri
  • test_outcome read-onlyReturns what Stripe's webhook did for a test member: their payments since a moment (ISO time, from test_pay), what each unlocked, their credits.
  • test_refundRefunds a test member's sandbox payment in Stripe's test mode, to prove what the app does after a refund — the same sandbox `pay` (from test_pay) and the same kit's guards: a test-mode key only, a test member's own payme
  • test_member_creditsGives a test member credits in Development, at once with no approval — the same credits the dashboard gives, on their credit history with the note. Test members only (made with test_member_add); anyone else is refused, a
  • test_member_suspendSuspends a test member in Development, at once with no approval — the dashboard's own suspend: they are signed out everywhere and can't sign in; their account, records and payments stay. For proving what the app shows a
  • test_member_unsuspendLifts a test member's suspension in Development, at once with no approval — the dashboard's own unsuspend: they can sign in again. Test members only (made with test_member_add); anyone else is refused, and it never reach
  • test_member_cancel_subscriptionCancels a test member's subscription in Development, at once with no approval, exactly as Live's would be: a sandbox (Stripe test mode) subscription is set to cancel at the end of the period it paid for — Stripe charges
  • request_go_liveAsks the founder to take the app live: its Development becomes the public Live app their customers use, on the Gemmein plan named (or the one the account already pays for). Going live is the founder's approval, then thei

…and 40 more.

Connect it

Claude Code
claude mcp add --transport http gemmein https://api.gemmein.com/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://api.gemmein.com/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "gemmein": {
      "url": "https://api.gemmein.com/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "gemmein": {
      "type": "http",
      "url": "https://api.gemmein.com/mcp"
    }
  }
}

Questions

What does Gemmein do?

Gemmein docs, API reference, error explainers and a live integration check for coding agents. It exposes 80 tools to AI assistants.

What tools does Gemmein provide?

80 tools, including guide, changes, reference, search_docs, explain_rule, explain_error, validate_collection_name, reaffirm_template, explain_relay, check_integration, app_status, tools_map….

How do I connect Gemmein to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://api.gemmein.com/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Gemmein require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Gemmein online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Gemmein?

gemmein.com. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Communication