Gemmein
Gemmein docs, API reference, error explainers and a live integration check for coding agents
Reviews
No review yet. Used Gemmein? Be the first to help others choose.What it does
Gemmein is an MCP server, a connector that lets an AI assistant use it as a tool. It can be used hosted (nothing to install) or installed locally.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)Hosted endpoint
https://api.gemmein.com/mcpstreamable-http
In Claude Code: claude mcp add --transport http gemmein https://api.gemmein.com/mcp
Install package
- NPM
@gemmein/mcpv0.21.1 · runs locally (stdio)
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"gemmein": {
"url": "https://api.gemmein.com/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 1d agoONLINE Gemmein answered an MCP connection on 15 Nov 2026 and introduced itself as gemmein 0.21.1 (MCP protocol 2025-06-18).
146 tools offered to AI assistants
guide· Returns 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. The guide opens withchanges· Returns 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 when knowledge of Gemreference· Returns 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.collection", "checkout") itsearch_docs· Searches 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 link with its anchoexplain_rule· Explains 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. Useful when choosing aexplain_error· Explains 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 repeats on retry; the apvalidate_collection_name· Checks 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 name throws from g.collreaffirm_template· Returns 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, it runs in CI. Usefulexplain_relay· Validates 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 provider's webhook), sccheck_integration· Runs 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 confirming it is done,app_status· Returns 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 still waits on, each itools_map· Returns 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…". With goal — take pay
Show 88 more
pull· Returns 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 gemmein/ folder yetkeys_list· Lists 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 used. The same list `nwaiting_review· Reads 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`/`send-back`'s own josync· Does 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, relays, AI tools anddeclare_collection· Creates 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 }). Same validator asput_record· Creates 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 is live, request_creupdate_record· Updates 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). Once the app is live,dev_delete_record· Deletes 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_record· Publishes 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 instead.set_payments· Sets 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. Needs Stripe connectput_relay· Creates 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 is not returned hereput_ai_tool· Creates 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 (label, credits, lock,put_ai_alias· Creates or repoints one model alias in Development (gemmein/ai/aliases.json's { name: { provider, model } }).put_email_template· Saves 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 same checks as sync;put_view· Creates 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 columns and totals irename_app· Names 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_add· Makes 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 the app works before htest_mail· Reads 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 back inside <customer_prove_app· Proves 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 standard proofs through ttest_run_ai_tool· Sends 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 run would. Answerstest_pay· Pays 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 (Stripe declines it; nothtest_outcome· Returns 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_refund· Refunds 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 payment only. payment istest_member_credits· Gives 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, and it never reachestest_member_suspend· Suspends 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 suspended person. Tetest_member_unsuspend· Lifts 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 reaches Live. On the fountest_member_cancel_subscription· Cancels 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 nothing more, and Strequest_go_live· Asks 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 their payment for the plrequest_promote· Asks the founder to promote Development's changes to the live app: collections (a new field arrives blank on existing records unless answered), plans and products (made in their Stripe account), relays and AI tools — Live's copy of each isrequest_rename_app· Asks the founder to rename the live app — the name titles every sign-in email its customers get. Before go-live, rename_app changes it at once. This is a change to how the business runs: your human approves it in their browser with the codecreate_app· Asks the founder to make another app on this same account, in Development only — a separate sandbox with its own collections, keys and settings, sharing nothing with this app's data. Refused once the account already has an app of that namerequest_add_domain· Asks the founder to add one of their own domains to the live app. email: true also sends the app's email from mail.<domain> (on a domain already added for the web, that adds email to it). site: true shows the app's Gemmein Live site at it —request_delete_domain· Asks the founder to remove one of the app's domains: the app stops answering at it and stops sending email from it. This is a change to how the business runs: your human approves it in their browser with the code Gemmein emails (and, when trequest_accept_terms· Asks the founder to accept Gemmein's terms for this app (going live needs them accepted). They read and accept the terms on the approval page. This is a change to one customer, so it is your human's approval alone: they approve it in theirrequest_revoke_server_key· Revokes one of the app's secret server keys by its name: a server that uses it is refused from then on. In Development this happens at once — no approval, no page. In Live it asks the founder to approve it in their browser first. For a Liverequest_replace_every_key· Asks the founder to replace every key Gemmein issued for this app — Development and Live, in one action: every secret server key, every relay's Gemmein-minted signing secret, every external AI tool's signing secret, and the site preview lindelete_app· Asks the founder to permanently delete this project's linked app — this can't be undone. Every record, customer, file, site, domain, relay, AI tool and key goes; every active customer subscription is cancelled in Stripe at once (no refund brequest_unpublish_site· Asks the founder to take the public Live site offline: its address and the app's own domains show a plain "This site is offline" page. Every version and file is kept and the Development preview is untouched; site_promote, or site_rebuild wirequest_delete_collection· Asks the founder to delete Live's own copy of one collection. A Live collection that holds records is refused before asking — it is deleted on the dashboard. Development's copy is deleted at once with dev_delete_collection. This is a changerequest_delete_relay· Asks the founder to delete Live's own copy of one relay: Live's events no longer start it. Development's copy is deleted at once with dev_delete_relay. This is a change to how the business runs: your human approves it in their browser withrequest_delete_ai_tool· Asks the founder to delete Live's own copy of one AI tool: Live's calls to it are refused from then on. Development's copy is deleted at once with dev_delete_ai_tool. This is a change to how the business runs: your human approves it in theirequest_grant_credits· Asks the founder to give one Live customer credits: their balance goes up by amount, and note is the line their credit history shows. test_member_credits does the same for a test member in Development, at once. This is a change to one custorequest_suspend_person· Asks the founder to suspend one Live customer: they are signed out everywhere and can't sign in; their account, records and payments stay, and the founder can lift it on the customer's page. test_member_suspend does the same for a test membrequest_unsuspend_person· Asks the founder to lift one Live customer's suspension: they can sign in again, nothing else changes. test_member_unsuspend does the same for a test member in Development, at once. This is a change to one customer, so it is your human's aprequest_delete_person· Asks the founder to delete one Live customer and their data — this can't be undone: their account, records, files and sign-in are erased, and a paid subscription they hold in Stripe is set to cancel at the end of the period they paid for. Trequest_cancel_subscription· Asks the founder to cancel one Live customer's subscription: a paid one is set to cancel in Stripe at the end of the period it paid for (Stripe charges nothing more); a comped plan ends at once. test_member_cancel_subscription does the samerequest_create_record· Asks the founder to create a record in one of Live's collections. Before go-live, put_record creates it at once. This is a change to one customer, so it is your human's approval alone: they approve it in their browser, and no emailed code irequest_update_record· Asks the founder to update one of Live's own records. Before go-live, update_record changes it at once. This is a change to one customer, so it is your human's approval alone: they approve it in their browser, and no emailed code is asked.request_delete_record· Asks the founder to delete one of Live's own records — this can't be undone. Before go-live, dev_delete_record deletes it at once. This is a change to one customer, so it is your human's approval alone: they approve it in their browser, andrequest_publish_record· Asks the founder to publish or unpublish one of Live's own records. Before go-live, publish_record changes it at once. This is a change to one customer, so it is your human's approval alone: they approve it in their browser, and no emailedrequest_app_lives· Asks the founder to set whether the LIVE app lives on the web, as a mobile app, or both. Before go-live, set_app_lives changes it at once. This is a change to how the business runs: your human approves it in their browser with the code Gemmrequest_email_switches· Asks the founder to turn the LIVE app's outgoing emails and/or its new-sign-in notice on or off. Before go-live, set_email_switches changes it at once. This is a change to how the business runs: your human approves it in their browser withrequest_email_sender_look· Asks the founder to set the local-part word each kind of email sends from on the LIVE app's own verified domain: account, support and/or news. Before go-live, set_sender_words changes it at once. This is a change to how the business runs: yrequest_google_signin_switch· Asks the founder to turn the LIVE app's "Continue with Google" on or off for customers. Before go-live, set_google_signin changes it at once. This is a change to one customer, so it is your human's approval alone: they approve it in their brefund_steps· Refunds are never made from a chat: Gemmein's Live Stripe key can't refund, by design. This reads one Live payment (its pi_… from live_revenue or the payment's Logs row) and answers your human's exact steps in Stripe — how much, to which culive_action_status· Reads where a Live request stands (one a request_* tool, inbox_reply, site_promote, site_rebuild or replay_relay with env live, a moderation tool with env live, domain_site on a Live app or request_server_key asked) — it changes nothing (aprequest_server_key· Asks for a secret server key (Development or Live) with exactly the access named — access like "notes:read,orders:read-write" or "all" — and "inbox:read" / "inbox:reply" for an agent that runs support from the app's server. A Development kedev_logs· Reads Development's Logs — stream auth (sign-ins), storage (record writes and refusals), manage (changes made through the dashboard, the CLI or this connection) or server (server-key refusals) — newest first (up to 100): each row's event, wdev_records· Reads records of one Development collection, newest first (up to 50) — the app's own test data as it stands while you build, for checking what a write saved. Customer details (names, email addresses, messages, record contents) come only whidev_people· Reads Development's people (email, when they joined, last seen, suspended, and whether each is a test member — added with test_member_add, or made by a check run). Customer details (names, email addresses, messages, record contents) come ondev_errors· Reads Development's Errors, the Logs page's own section: each refusal code with its count, first and last seen, the newest refusal's own sentence, an example Logs row id (dev_logs reads the row), and the page that explains the code (https:/dev_view· Reads one Development view's rows, exactly as its layout shows them (filtered, sorted, its declared columns) with its totals, and each row's own action buttons (the moves open to it right now). Customer details (names, email addresses, messdev_delete_collection· Deletes one collection from Development, with its records — the dashboard's own delete, at once, with no approval (Development is what this connection builds). Never Live: a collection Live has stays in Live, and a promote never removes anydev_delete_relay· Deletes one relay from Development, with its run history — the dashboard's own delete, at once, with no approval: Development's events no longer start it. Never Live: a relay Live has stays in Live, and a promote never removes anything fromdev_delete_ai_tool· Deletes one AI tool from Development — the dashboard's own delete, at once, with no approval: Development's calls to it are refused from then on. Never Live: an AI tool Live has stays in Live, and a promote never removes anything from Livedev_email_templates· Lists Development's email templates (sign-in, purchase, plan-start, notify, notify-account, notify-event, email-person, inbox-reply) — each one's version and which {{vars}} it takes; with name, one template with its full saved source (sign-dev_email_template_preview· Renders one of Development's email templates (sign-in, purchase, plan-start, notify, notify-account, notify-event, email-person, inbox-reply) with sample data — the saved version, or, with html, that design instead (to check it before savindev_email_template_test· Sends ONE test of a Development email template (sign-in, purchase, plan-start, notify, notify-account, notify-event, email-person, inbox-reply) with sample data to the founder's OWN address only — never anyone else's, and never asked for hedev_delete_email_template· Deletes one of Development's email templates (sign-in, purchase, plan-start, notify, notify-account, notify-event, email-person, inbox-reply) — the dashboard's own delete, at once, with no approval: Development's emails of that kind go backdev_delete_view· Deletes one view's recipe from Development — the dashboard's own delete, at once, with no approval; the collection and its records are untouched, only the view's recipe goes. Never Live, even by request: a view's recipe reaches Live only thdev_delete_ai_alias· Deletes one model alias from Development — the dashboard's own delete, at once, with no approval. Refused (alias_in_use) while any AI tool still runs on it — point them elsewhere first (put_ai_tool). put_ai_alias makes it again. On the founview_add· Creates one record in Development through a view's own "add" form — the SAME record-create door the dashboard's Data room uses, curated to the view's declared add.fields: data may name only those fields. A file or image field takes the refeview_edit· Updates one record in Development through a view's own "edit" form — the SAME record-update door the dashboard's Data room uses, curated to the view's declared edit.fields, compare-and-swapped on ifVersion (the version dev_view's own row caview_reorder· Moves one record on a view's own "reorder": true field — the collection's own rankable number field, written through the SAME record-update door a plain edit uses. move: "up" or "down" swaps rank with its one neighbour in the view's own ordrelay_runs· Reads a relay's runs in Development (env development, the default) or Live (env live — needs the live:read grant), newest first: each run's id, relay, what triggered it, status (queued, running, done, failed, dead), attempts, the last errorreplay_relay· Runs one finished relay run (done, failed or dead — its id from relay_runs) again, every action of the relay as it is now; an action that already succeeded finds its own earlier work (a payment's grants are given once, an email isn't sent tpause_relay· Pauses one relay in Development — its trigger fires no more events until resumed; events already queued or running finish. The same pause the dashboard's own switch makes. resume_relay lifts it. On the founder's Logs.resume_relay· Resumes one paused relay in Development — its trigger fires again. The same resume the dashboard's own switch makes. On the founder's Logs.sends_read· Reads up to 50 of the emails the app has sent one person (by their id, from dev_people/live_people) — kind, subject, when, and whether it was answered (a support reply only). Never the email's own body. A subject is the founder's own templaai_calls_read· Reads this environment's AI tool calls, newest first — the tool, who called it (a person's id, never for a relay or a key), the cost, the status, and (where the tool records it) the prompt and answer, wrapped as a customer's or the founder'set_ai_settings· Sets Development's settings for one AI provider: rawCalls (true = the provider's own exact error text reaches the chat, for debugging — off by default), models (the allow-list a tool may pin or alias to; omit to leave it, [] to clear it toset_email_switches· Turns the app's outgoing emails (sends — on by default) and/or the new sign-in device notice (newSignIn — on by default) on or off. Send either or both; the other is left as it is. Before go-live it acts at once; once live, the founder apprset_sender_words· Sets the local-part word (before the @) each kind of email sends from on the app's own verified domain: account, support and/or news. These are also the Inbox's own labels — a reply arrives at <word>@<domain>, so changing one changes whereset_app_lives· Sets whether the app lives on the web, as a mobile app, or both — read before go-live to shape which proofs it asks for (a web app's secret scan proves nothing about a phone bundle, so changing this clears any stored scan; go-live asks agaiset_google_signin· Turns "Continue with Google" on or off for the app's customers, in Development only — always, whether or not the app is live. It never touches Live's own switch, which keeps running whatever it was set to: ask for that with request_google_salert_preferences· Reads which founder alerts (by kind) are on for the signed-in founder on this account. set_alert_preferences changes them.set_alert_preferences· Turns up to 20 founder alert kinds on or off for the signed-in founder on this account — send [{kind, enabled}, …]. Some critical kinds are locked on and refuse to turn off (the door names which). On the founder's Logs.approvals_list· Lists this app's own machine and AI-connection approval requests — who asked, what for, its state (waiting, approved, denied, cancelled, revoked, expired), when. Only this app's own; another app on the same account never shows here. open: t
The first 100 are shown.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Install package | @gemmein/mcp | DECLARED | SRC-001 Official MCP Registry | 13h ago |
| Version | 0.21.1 | DECLARED | SRC-001 Official MCP Registry | 13h ago |
| Hosted endpoint | https://api.gemmein.com/mcp | DECLARED | SRC-001 Official MCP Registry | 13h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 13h ago |
| Package registries | npm | DECLARED | SRC-001 Official MCP Registry | 13h ago |
| Local install (package) | yes | DECLARED | SRC-001 Official MCP Registry | 13h ago |
| Website | https://gemmein.com | DECLARED | SRC-001 Official MCP Registry | 13h ago |
| Repository | https://github.com/gemmeinhq/gemmein-release | DECLARED | SRC-001 Official MCP Registry | 13h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 13h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 13h ago |
Change history
- VERSION15 Nov 20260.21.0 → 0.21.1
- VERSION10 Nov 20260.20.1 → 0.21.0
- VERSION26 Oct 20260.20.0 → 0.20.1
- VERSION25 Oct 20260.18.0 → 0.20.0
- VERSION21 Oct 20260.17.0 → 0.18.0
- CHANGED18 Oct 2026remote access: no → yes
- VERSION18 Oct 20260.16.3 → 0.17.0
- VERSION16 Oct 20260.16.2 → 0.16.3
- VERSION16 Oct 20260.16.1 → 0.16.2
- VERSION15 Oct 20260.16.0 → 0.16.1
- VERSION14 Oct 20260.15.0 → 0.16.0
- VERSION10 Oct 20260.14.0 → 0.15.0
- VERSION08 Oct 20260.13.0 → 0.14.0
- VERSION04 Oct 20260.12.0 → 0.13.0
- VERSION04 Oct 20260.11.0 → 0.12.0
- VERSION03 Oct 20260.10.1 → 0.11.0
- VERSION28 Sept 20260.10.0 → 0.10.1
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Gemmein still online?
Free alerts · no account▲ 0Do you run Gemmein? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Gemmein
How do I connect Gemmein?
Use the hosted endpoint https://api.gemmein.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Gemmein offer?
When Electra Index connected on 15 Nov 2026, it listed 146 tools: guide, changes, reference, search_docs, explain_rule, explain_error, validate_collection_name, reaffirm_template and more. The full list is in "Live check" above.
Is Gemmein online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.