Node.js/TypeScript MCP server for Atlassian Confluence. Provides tools enabling AI systems (LLMs) to list/get spaces & pages (content
Nothing to run from here
Gemmein is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
14
downloads a day
local
runs on your machine
2k
downloads in 30d
What it does
Gemmein docs, API reference, error explainers and a live integration check for coding agents.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user gemmein-mcp '--' npx -y @gemmein/mcp
# 2 — ask your agent for something these tools do
# guide, changes, reference and 7 more
Gemmein costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
PublisherVerified · since 2026
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Gemmein as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user gemmein-mcp '--' npx -y @gemmein/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Call this FIRST — before any install, account, or code — when your human asks to build an app on Gemmein, to move an existing app onto it, or whether their app can use it at all. The guide (llms.txt) opens with two doors — starting from an idea with nothing built yet, or already holding an app —…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | optional: what you need ("refund a payment") — returns only the docs sections that answer it, as direct .md links |
Call this when what you remember about Gemmein may be older than the installed release — from training data, or a guide read weeks ago — and before telling your human how something works. Returns what changed in each Gemmein release newer than since (a Gemmein version, e.g. "0.22.1"), or the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | no | the Gemmein version you knew, e.g. 0.22.1 — returns every release after it; leave out for the last three |
Reach for this while WRITING code against @gemmein/sdk: every method, exact signature, return shape, and the stable error-code table (REFERENCE.md). Pass topic (a module or method: "g.collection", "checkout") to get only the matching sections — the packaged text plus each section's direct link,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | optional: a module or method — returns only its sections instead of the whole reference |
Use when one question comes up mid-build ('keyed create', 'ifVersion', 'addressed', 'expand') and reading a full document would waste context. Answers first with the docs site's sections that match, best first — each a direct markdown link with its anchor…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | term or phrase to find |
Call while DESIGNING a collection — which rule fits this data? — or when a rule refuses something at runtime. One of the seven rules (private, shared, admin_write, public_read, community, addressed, direct) returns its exact access contract, what it is right for, and the mistakes that leak data.…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rule | string | no | the rule to explain; omit for the all-rules cheat-sheet |
Call the moment a GemmeinError reaches you (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; fix the approach, not the request). Parsed from…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | no | the err.code to explain; omit to list all |
Run at PLANNING time on every collection name you intend to use, before any g.collection(name) call is written. The naming law: lowercase letters, numbers, underscores; starts with a letter; 2-63 characters. A bad name throws from g.collection(name) before any network call — at module load that…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
Fetch this when you wire up the app's CI, or when you hand the finished app to your human: 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). Copy it next to the app, set the CONFIG block,…
No parameter schema on file.
Call while WRITING or FIXING gemmein/relays/<name>.json — before gemmein sync carries it to the cloud. A relay is one trigger (receiver: a provider's webhook; schedule: a clock; data_change: a record changing) and up to ten actions in Gemmein's own verbs (write_record, grant_access,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| definition | object | yes | the relay definition — the contents of gemmein/relays/<name>.json ({ name, trigger, actions }) |
Call after wiring the app to Gemmein and before telling your human it is done — and again before go-live. Runs the reaffirm boundary checks live against the caller's own app; returns structured pass/fail (structuredContent: checks, notes, failedCount, passed). Tier A (public pk_ key only): the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| publicKey | string | yes | the app's public pk_ key |
| privateCollection | string | yes | a collection with the private rule |
| publicCollection | string | no | optional: a community/public_read collection to confirm anonymous readability |
| secretKey | string | no | optional: the sk_dev secret key — enables Tier B isolation proof (sk_live is refused) |
| apiUrl | string | no | optional: API base URL override (local/dev API); omit for production Gemmein |
| testUsers | array | no | optional: the two Tier-B test emails (default reaffirm-a/b@test.dev). Each is signed out of its earlier sessions, so name real development people only if signing them out is fine |
| timeoutMs | number | no | overall time budget, default 30000 |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Gemmein or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.16.0 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digestd502c7c900b0ea8c4c56c51ef7066190fd0bf199a65551391e5c9d445bc1a833
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (10 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| guide | no tags | |
| changes | no tags | |
| reference | no tags | |
| search_docs | no tags | |
| explain_rule | no tags | |
| explain_error | no tags | |
| validate_collection_name | no tags | |
| reaffirm_template | untrusted-input | untrusted-input: keyword "fetch" |
| explain_relay | no tags | |
| check_integration | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestd502c7c900b0ea8c
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.16.0. Pin a release below and the command asks for exactly that one.
0.16.0
14 Oct 2026
latestNo release note was published with this version.
0.14.0
7 Oct 2026
No release note was published with this version.
0.13.0
4 Oct 2026
No release note was published with this version.
0.12.0
3 Oct 2026
No release note was published with this version.
0.10.1
28 Sep 2026
No release note was published with this version.
0.10.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Gemmein can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.