bots.st/gemmein
Gemmein
Gemmein docs API reference and integration checks
2488 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 139
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://api.gemmein.com/mcp - npm
npx -y @gemmein/mcpReleased 26 Oct 2026, version 0.20.1
What it can do
| Tool | What it says it does |
|---|---|
ai_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's own words. Filter by person. Up to 50 (before = the last… |
alert_preferences | Reads which founder alerts (by kind) are on for the signed-in founder on this account. set_alert_preferences changes them. |
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 in plain words. Then its status across the board, per… |
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: true for waiting ones only. cancel_approval withdraws one… |
buy_plan | Free to build. You pay when an app goes live — or buy ahead if you're ready. Hands your human Gemmein's own payment page for the ACCOUNT's plan, before this app goes live (one plan covers every app on the account — Launch — $29 a month for the account, up to 5 apps — any may go live. 50 GB pooled… |
cancel_approval | Cancels one of this app's own approval requests that is still waiting for the founder's browser press — a mistaken or stale ask, withdrawn before anyone approves it. Refused (not_found) for a request this app's key does not own, the same way a stranger's data is refused anywhere else, never naming… |
changes | 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 Gemmein may be older than the installed release (training… |
check_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, and before go-live. It takes the app's public pk_ key only… |
close_circle | The founder's moderation: closes one circle (Close circle) — every member stops seeing its posts at once (New links stop at once; a link already opened stops working within 5 minutes.); each post stays with its author, and nobody is told. In Development it is done at once. In Live (env live) it… |
connect_payments | Connects Stripe through Gemmein's own one-purpose page — a restricted key is never typed into a chat. Answers one state: connected (which Stripe account, test or live mode), waiting (the page's link for your human: it opens Stripe's key page with every permission already ticked, Development's also… |
create_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 name or is at its cap. The new app has no connection of its own… |
declare_collection | Creates or updates one collection in Development from its declaration — exactly the JSON of gemmein/collections/<name>.json ({ rule, fields, unlockedBy, publishing, openFields, directInitiation, rankable }). Same validator as gemmein dev and sync: a bad name, rule or field is refused with the fix… |
dev_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 founder's Logs. |
dev_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 Live — removing Live's is its own request… |
dev_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 anything from Live — removing Live's is its own request… |
dev_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 back to Gemmein's own design. Never Live: Live's templates… |
dev_delete_function | Deletes one function from Development, with its secrets — the dashboard's own delete, at once, with no approval: a relay's run_function naming it fails until put_function makes it again. Never Live: a promote never removes anything from Live. On the founder's Logs. |
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. |
dev_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 from Live — removing Live's is its own request… |
dev_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 through promotion, which adds and updates views and never… |
dev_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-in: the sign-in.json brand config). Changes nothing. This… |
dev_errors | Reads Development's Errors page: 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://docs.gemmein.com/errors/<code>). The last 7 days, or the last `hours` (1–168); up… |
dev_functions | Lists Development's functions — each one's name, version, reach in plain words and which secrets are set (names only, never a value); with name, one function with its source. Changes nothing. This is what a founder may call their custom code. |
dev_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, when, whether it was allowed, and the refusal's reason… |
dev_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 only while the owner has "Customer details for AI… |
dev_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 while the owner has "Customer details for AI assistants" on —… |
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, messages, record contents) come only while the owner has… |
domain_check | Returns three views of one domain already added to this app (never any other domain): what public DNS shows now — the A, AAAA, CNAME and TXT records at the domain, its www and _gemmein, read from 3 fixed public DNS servers (Cloudflare (1.1.1.1), Google (8.8.8.8), Quad9 (9.9.9.9)), with how long… |
domain_connect_link | Returns, for one domain already added to this app, the one-click link that sets it up at the founder's own DNS provider when that provider offers Gemmein's one-click setup (Domain Connect): the founder opens it, signs in at the provider, sees every record and approves there — Gemmein never holds a… |
domain_site | Turns "Show my Gemmein site here" on (show: true) or "Stop showing my site here" (show: false) for one domain already added to this app — the same switch as the dashboard's Domains page and `npx gemmein domains show|hide`, with the same refusals (not this app's domain, not proved yours yet, a… |
explain_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 approach changes, not the request). Parsed from the… |
explain_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), schedule (a clock), data_change (a record changing)… |
explain_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 a collection's rule, or when a rule refuses something at… |
function_secret | Says whether a function's secret is set (never its value) and returns where the founder sets it — a secret is never typed into a chat. env "live": Live's own value, which never comes from Development; a Live function waits paused until each is set. Gemmein keeps it encrypted, sends it only to the… |
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 with two doors — starting from an idea with nothing built yet… |
inbox_reply | Asks the founder to approve one reply to a customer inside an existing Inbox conversation (threadId from live_inbox): the approval page in their browser shows the exact text and the customer it goes to (a browser approval; no emailed code is asked for a reply); approving it sends it, once… |
keys_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 `npx gemmein keys list` and the dashboard's API keys page… |
live_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 (approving it in the browser is what carries it out). status… |
live_emails | Reads what happened to the Live app's transactional email over the last `days` (1–90, default 30), per template (sign-in, purchase, plan-start, notify, inbox-reply, new-sign-in): sent, bounced, complained (marked as spam) and deferred (the receiving server asked to try later). Counts only — never… |
live_errors | Reads the Live app's Errors page: each refusal code with its count, first and last seen, the newest refusal's own sentence, an example Logs row id, and the page that explains the code (https://docs.gemmein.com/errors/<code>). The last 7 days, or the last `hours` (1–168); up to 50 codes. live:read… |
live_inbox | Reads the app's support Inbox: conversations, unanswered first — who wrote, the subject, when, whether the founder owes them an answer (up to 50). With threadId: that whole conversation in plain text, oldest first (the last 50 messages, each up to 8,000 characters), which messages were automatic… |
live_logs | Reads the Live app's Logs — stream auth, storage, manage or server — newest first (up to 100). Customer details (names, email addresses, messages, record contents) come only while the owner has "Customer details for AI assistants" on — a dashboard setting (Settings → AI assistants), off by… |
live_overview | Reads the Live app in one call: people who joined and were active this calendar month against last month, refund-aware revenue this month against last (per currency, minor units), subscribers by plan, errors in the last 24 hours and their codes, what waits on the founder (approvals asked in their… |
live_people | Reads the Live app's people (email, when they joined, last seen, suspended). Customer details (names, email addresses, messages, record contents) come only while the owner has "Customer details for AI assistants" on — a dashboard setting (Settings → AI assistants), off by default, never changed… |
live_records | Reads records of one Live collection, newest first (up to 50). Customer details (names, email addresses, messages, record contents) come only while the owner has "Customer details for AI assistants" on — a dashboard setting (Settings → AI assistants), off by default, never changed from a chat… |
live_revenue | Reads the Live app's business numbers: people (total, active in 30 days, suspended), subscribers by plan, refund-aware revenue per currency. live:read; audited; changes nothing. This is what a founder may call how much they have made, or sales. |
live_subscriptions | Reads the Live app's subscriptions (who, which plan, status, period end). Customer details (names, email addresses, messages, record contents) come only while the owner has "Customer details for AI assistants" on — a dashboard setting (Settings → AI assistants), off by default, never changed from… |
live_usage | Reads the Live app's Usage: each meter (API requests, storage writes, sign-in events, stored bytes, Edge function runs, emails sent — the last two pooled across every Live app on the account) against its ceiling this period, the active people the plan's band follows, AI calls, credits used and… |
live_view | Reads one Live 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 — view_action carries one out). Customer details (names, email addresses, messages, record contents) come only… |
live_webhooks | The same read as relay_runs with env live, under the name earlier versions used — call relay_runs with env live in new work. Reads the Live app's relay runs, newest first: which relay, what triggered it, status (queued, running, done, failed, dead), attempts, the last error and every action's… |
pause_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. |
people_graph | Reads one person's follows and circles, the way their page on the dashboard shows them: with person (their id, usr_…) and view — following, followers, requests (follow requests waiting for them), requested (theirs, waiting) or circles (the circles they are in, each with its creator and size) —… |
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 the app's real doors in Development. Useful before… |
provider_key | An AI provider's key, pasted by your human on Gemmein's own one-purpose page — never in a chat. Answers one state: connected (the key works, with the model it answered as), connected_with_problem (the key is saved but the account has no credit, the model isn't available to it — naming the tool… |
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. |
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 yet, or before editing, to start from what is there. File… |
put_ai_alias | Creates or repoints one model alias in Development (gemmein/ai/aliases.json's { name: { provider, model } }). |
put_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, enabled) stands, as with sync. The AI provider's key is… |
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; scripts and remote resources are stripped and named. This… |
put_function | Creates or updates one function in Development and deploys it: source is ONE bundled JavaScript module (`export default { async run(ctx, input) { … } }` — no imports; bundle TypeScript and npm packages first), reach is what it may do beyond its caller's own rights ({ read: [collections], write… |
And 79 more tools.
In its maker's words
Gemmein docs, API reference, error explainers and a live integration check for coding agents.
- Website
- gemmein.com
- Source
- github.com/gemmeinhq/gemmein-release
- Publisher
- gemmein.com
- Listed from
- the official MCP Registry as
com.gemmein/mcp - Version
- 0.20.1, updated 26 Oct 2026
- Kinds of work
- Law, tax and government, AI models and agent tools, Browser and automation
The domain it lives on
- gemmein.com
- registered 4 Jul 2026 (4 months ago), at NameCheap, Inc., its home page is a working site
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 2488 ms | |
| Answered | 1950 ms | |
| Answered | 811 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.