com.gemmein/mcp

up checked 2026-11-11T10:39:29.163Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided title

Gemmein

Publisher-provided description

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

Summary by lookupd

Lets an agent read Gemmein docs and API reference, manage collections, records, relays and payments in Development, and run integration…

Install

Claude Code, remote (streamable-http)

claude mcp add --transport http mcp https://api.gemmein.com/mcp

Claude Code, npm package (stdio)

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

Codex, remote (streamable-http)

codex mcp add mcp --url https://api.gemmein.com/mcp

Codex, npm package (stdio)

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

Cursor, remote (streamable-http) → .cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://api.gemmein.com/mcp"
    }
  }
}

Cursor, npm package (stdio) → .cursor/mcp.json

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

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (showing 30 of 146)

Publisher-provided text

• 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, movin
• 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 w
• reference Returns the @gemmein/sdk API reference (REFERENCE.md): every method, exact signature, return shape, and the stable error-code table. Useful while writing code a
• search_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
• 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
• 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 ste
• validate_collection_name Checks a collection name against the naming law: lowercase letters, numbers, underscores; starts with a letter; 2-63 characters. Useful while planning collectio
• reaffirm_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 p
• 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 bounda
• 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
• 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 eve
• tools_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
• 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 a
• 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 Developm
• waiting_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 (de
• sync 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 thro
• declare_collection Creates or updates one collection in Development from its declaration — exactly the JSON of gemmein/collections/<name>.json ({ rule, fields, unlockedBy, publish
• put_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 ownerUser
• update_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
• 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 instea
• 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
• 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 dashboa
• put_relay Creates or updates one relay in Development from gemmein/relays/<name>.json's contents ({ name, trigger, actions }); explain_relay validates the same definition
• 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
• 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, p
• put_view Creates or updates one view in Development from gemmein/views/<name>.json's contents ({ collection, filter?, sort?, columns?, totals?, layout, actions? }): one
• rename_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 brows
• 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. Tes
• test_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 membe

Details

• Version: 0.21.0
• Transports: streamable-http, stdio
• Uptime (7 days): 100%
• Median latency: 263 ms
• First indexed: 2026-11-01T08:54:10.202Z
• Last seen in registry: 2026-11-10T03:17:09.551Z
• Repository: https://github.com/gemmeinhq/gemmein-release
• Website: https://gemmein.com

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/com.gemmein/mcp.svg)](https://lookupd.com/servers/com.gemmein/mcp)

• 62033 servers
• Last crawl: 2026-11-11T15:38:39.561Z
• API base: https://api.lookupd.com
• MCP URL: https://api.lookupd.com/mcp