io.github.girapphePublished by GitHub account girapphev0.6.3Updated Oct 24, 2026
Your reviewed knowledge, across AI conversations.
MemoStem lets an assistant save selected general knowledge from a chat as private drafts and reuse your approved knowledge in later conversations.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.girapphe%2Fmemostem/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"memostem": {
"type": "http",
"url": "https://www.memostem.com/api/mcp"
}
}
}Your reviewed knowledge, across AI conversations.
Let a connected AI reuse your private, confirmed knowledge or notice knowledge worth keeping as the conversation unfolds. New material becomes a private draft only after you confirm—without uploading the whole conversation or publishing anything automatically.
Use MemoStem · Connection guide · Privacy · Terms · Support · Security · Contact
This public repository is the official distribution source for MemoStem's chat-host skills, plugin packages, and hosted remote MCP connection metadata. ChatGPT, Claude, Kimi, Gemini and Grok are the primary channels; Codex and Claude Code are compatible secondary channels. The MemoStem application and server implementation remain private. Distributable manifests, skills, examples, and documentation have no mirrored authoring copy in that private repository.
Select an explanation in ChatGPT and keep it in a private guest shelf. Connect your account to move it into private pending review, then review and approve it in MemoStem. Then ask Claude or another connected host to find that knowledge. Sign in to the same MemoStem account in each host; no host gets access to another host's conversation history.
Use ordinary requests in the host where MemoStem is installed. The skill routes by your intent; opening MemoStem alone does not save anything.
An in-chat quiz does not enroll knowledge in MemoStem practice or record a practice result. A proposed improvement takes effect only after you review it in MemoStem. On a failed or uncertain save, the skill preserves the original request identity so retrying does not intentionally create another copy.
The packaged skill's main file covers what is worth keeping and how to write it, plus every consent rule. It includes focused guides for capture and selection, connection and onboarding, the guest shelf, retrieval and study, and recovery and status. They are loaded when the request needs them. The OpenAI portal ZIP ships the same guides.
The packages ship no lifecycle hooks. The Claude plugin directory accepts
command hooks only from Verified organizations, so the earlier SessionStart
reminder was removed; the memostem skill carries the same consent and
retrieval rules on every host.
In an MCP Apps-capable host with a connected account, check candidates and click Add. That click creates only the selected private pending drafts; no second chat confirmation is needed. If the host shows a text list instead, reply with the candidates to keep. Then open Candidate Inbox to read, edit, and approve them. Previewing or adding drafts does not approve knowledge or enroll it in practice. The picker UI is served by the hosted MCP server; see the MCP Apps contract and host requirements.
See card examples and review steps.
The production Streamable HTTP MCP endpoint is:
Open the MemoStem listing in ChatGPT Plugins.
The OpenAI plugin portal takes a plugin ZIP; the MCP server is connected
separately (With MCP, Universal, URL above), not imported from the ZIP.
Build the ZIP from the memostem package with npm run package:portal. It
contains the single memostem skill, assets/, and a root plugin.json with
the OpenAI interface metadata, and omits hooks/, .app.json, .claude-plugin/,
.codex-plugin/, and .mcp.json. The portal rescans the connected MCP server
daily and offers a manual Rescan. Plugins with lifecycle hooks and packages with
apps/.app.json cannot currently be submitted, which is why the ZIP is staged
from plugins/memostem without them. Sources checked 2026-10-15:
Build plugins and
Submit a plugin.
Whether the portal needs a root mcp.json or shows a Desktop-only label for a
ZIP is not yet confirmed; --with-mcp-json builds the variant that includes it.
A new version of an existing portal listing must carry that listing's plugin ID
as its manifest name: pass it with npm run package:portal -- --name=<plugin ID>.
The ID is shown only in the portal and is not committed here; the source
plugins/memostem/plugin.json keeps name: "memostem" for every other channel.
The OpenAI listing copy for that ZIP lives in
contracts/openai-portal-interface.json. The public
MemoStem connection page explains the
privacy boundary and points signed-in users to the in-product setup guide.
MemoStem uses mixed, lazy authentication. Guest capture needs no account;
claiming the shelf or using protected tools starts OAuth. New ChatGPT
connections request openid, knowledge:drafts:create,
knowledge:context:read, and knowledge:drafts:status. Existing grants are not
upgraded automatically; disconnect and reconnect, or consent again, to add
read access. openid is used only for identity; the defaults exclude
profile, email, metadata scopes, and offline_access. GitHub publication
alone does not list or activate a ChatGPT plugin.
Find MemoStem in the Claude Connectors Directory.
Add the same endpoint as a custom connector in Claude and complete MemoStem OAuth. Claude can also load the Git marketplace below for Claude Code and compatible plugin surfaces.
When a directory listing URL changes as part of a plugin release, update this
README and the application’s shared provider-link map at
packages/shared/src/ai-provider-links.ts in the private app repository, then run both repositories’
document and plugin checks. A package version change alone does not change the
directory URL; keep the public listing identity and install destinations in
sync when a provider supplies a new link.
Import this repository with Kimi Work's Plugin Builder, install from Personal, and complete OAuth. Review the converted skill and MCP settings before use. See the Kimi guide. Marketplace approval is separate.
Use Gemini Apps → Connected Apps → Custom apps with the same MCP endpoint. Current access conditions include US location, age 18+, a personal account, English and Keep Activity enabled. See the Gemini guide.
Use Grok's Connectors → New Connector → Custom and complete authentication. See the Grok guide; this is the general-chat connector.
A custom MCP connection exposes server tools and instructions; it does not install this repository's SKILL.md. Plugin loading and proactive suggestions depend on the host. Channel availability requires actual account verification.
See the MCP connection guide for provider-specific setup and server-side OpenAI API usage.
MCP clients receive guidance to make one brief save offer at a
natural stopping point when the current conversation produces independently
teachable general knowledge: a concept, mechanism, general procedure,
comparison, evidence-backed claim, knowledge question, historical event, or
language expression. The installable plugin also includes an implicitly discoverable
memostem skill with the same behavior.
The offer sends nothing and is not consent. The client may call a creation tool only after a clear affirmative reply to that specific proposal or a direct request identifying the current-conversation material. Before account connection, that selection goes to the private guest shelf; after OAuth it becomes an owner-scoped private pending draft. It must not repeat a declined topic or propose sensitive, secret, credential, or do-not-retain material. AI hosts decide whether and when to surface MCP instructions, so a connection cannot guarantee an offer in every client.
Personal or company decisions, product policies, preferences, plans, tasks, meeting outcomes, and autobiographical facts are outside this capture contract. A direct request to save named eligible material already provides consent; the assistant should verify the connection and create the requested drafts. When MemoStem is explicitly invoked without named material and the current conversation has no eligible candidate, the installed skill may apply the same candidate, consent and draft flow to recent conversation context actually provided by the host. If that context is unavailable, it reports the limitation instead of fabricating a candidate. It never transfers the source transcript.
Complete sign-in and consent in the OAuth page, then start a new Codex task so the installed snapshot loads. In that task, ask:
Check my MemoStem connection, then save the general knowledge I selected in this conversation as concise atomic memo and question-and-answer drafts.
The plugin calls check_memostem_connection first and verifies the draft
permission, then calls create_knowledge_bundle_drafts. A successful login or
tool listing alone does not prove that any draft was created. The assistant
must report the server's actual pending count and review link. Browser forms
are not a substitute for this plugin path.
For the OpenAI plugin portal, build the ZIP with npm run package:portal; the
Codex marketplace lists only memostem@memostem. The OpenAI docs describe
Desktop-only labels for local MCP servers and hooks, not for a remote
mcp.json; whether the portal labels a ZIP Desktop only is unverified until a
draft is created. Installing a package and completing OAuth are separate steps.
Run /reload-plugins, then /mcp to inspect the connection and complete OAuth
when prompted.
Without an account, save_guest_knowledge_bundles keeps only specifically
selected current-conversation general knowledge in a private shelf of at most
ten cards for 90 days. Its opaque workspace_token is a private continuation
credential: clients reuse it as a tool argument and never display or log it.
The separate short-lived review_url opens a read-only view. At capacity,
claim_guest_knowledge_workspace starts OAuth and moves the same cards into
private pending review after consent. validate_knowledge_bundle and
preview_knowledge_bundle check one selected bundle without saving it.
start_memostem displays localized onboarding or owner topic labels;
connect_memostem starts read-scope OAuth when required. Neither creates a card.
check_memostem_connection: verify authentication and report granted scopes
without reading or writing knowledge.get_topic_context: with knowledge:context:read, retrieve only the
authenticated owner's knowledge. It defaults to active confirmed items;
callers may explicitly request active, pending, archived, superseded,
or recoverable trashed lifecycle states.list_knowledge_catalog: page through the owner's stable topic and tag IDs,
canonical names, aliases, and active item counts without returning card bodies.search_knowledge: search active approved, non-superseded owner knowledge;
exact matches rank before registered aliases and keyword matches.get_knowledge_context: retrieve canonical content, taxonomy, version, and
selector-only provenance for exactly the selected item IDs across topics.create_knowledge_bundle_drafts: create structured private drafts from a
specific suggestion the user confirmed, or material they directly asked to
save from the current conversation. Each bundle must use
knowledge_scope: "general_knowledge".review_knowledge_bundle_candidates: present a bounded candidate selection
before creation; an MCP Apps Add action or an explicit text selection passes
only the chosen candidates to draft creation.create_card_drafts: compatible concept-card draft creation.get_draft_batch_status: with knowledge:drafts:status, read whether each
submitted draft is still pending or was approved, merged, updated, or ignored
by the owner. The tool cannot execute those actions.Context packs use schema version 2 and label each item with its lifecycle and verification status. Pending items remain unconfirmed candidates; non-pending items are user-confirmed but not independently fact-checked. Explicit item selection fails as one non-leaky request if any ID belongs to another owner, is outside the requested lifecycle states, has expired from trash recovery, or was permanently deleted. No context response contains raw conversation history.
An optional resolution_proposal contains a complete proposed final card,
target version, source item IDs, change summary, and reason. It is never a
partial patch or a completed merge. Draft creation cannot approve knowledge, publish to the public graph, or retain
a conversation transcript. Question-and-answer cards use answered question
bundles; they do not automatically enroll in practice. See the
working payload example
and the complete connection and capture guide.
The plugin includes only memostem, which guides getting started and account
connection, explicit saves, consent-first suggestions, owner-scoped retrieval and
study, draft status, and save recovery through the available MemoStem tools.
Developer maintenance skills belong in the private application repository and
are excluded from every public plugin package.
server.json to the official
MCP Registry when a GitHub Release is published.plugins/memostem is also an Agent Plugins 1.0
package: root plugin.json, root mcp.json, and the same skills/ tree.
The portable MCP config uses streamable-http; existing Codex/Claude adapters
keep .mcp.json with http. OAuth discovery and credential storage belong to
the client. No token or OAuth credential is packaged.
gemini-extension.json at the repository root is a remote-MCP-only Gemini CLI
extension manifest (no skill, no credentials); npm run check keeps its
version and endpoint aligned. It is not listed until the repository carries the
gemini-cli-extension topic.
Portable format validation does not establish support in any particular host.
Kimi's documented import route converts a source package; Gemini and Grok use
custom MCP connections. The Codex install name memostem@memostem and the
Claude install name are unchanged; the former memostem-chatgpt package was
removed. The portal ZIP is built from plugins/memostem only
(npm run package:portal, output dist/memostem-<version>-<shortsha>.zip,
git-ignored; requires a clean tree). Skills have a single copy under
plugins/memostem/skills; npm run check asserts the staged ZIP tree.
The dependency-free repository check validates both marketplaces, cross-platform
metadata, the complete skill trees, MCP Registry metadata, public/private
boundaries, symlinks, common secret patterns, and the versioned
contracts/mcp-compatibility.json contract.
That contract names mixed authentication, guest shelf limits, the endpoint,
OAuth scopes, required tools, MCP Apps
resource and action bindings, text fallback, and public fixtures that the private
application validates semantically against its real MCP schemas. It deliberately replaces byte-for-byte cross-repository copies.
Before releasing a public branch that changes the contract or its fixtures, a
MemoStem maintainer runs the private Public plugin compatibility workflow
with this branch name as public_plugin_ref. The workflow checks out this
repository temporarily; it does not copy plugin sources into the private Git
history.
For local Codex iteration, the plugin-creator cachebuster helper can append
+codex.<timestamp> to the Codex manifest version before reinstalling from a
local marketplace. Validation permits that Codex-only build suffix while
requiring the underlying release version to match the Claude and Registry
manifests. Start a fresh task after reinstalling so its tools and instructions
come from the new snapshot.
For support, partnership, or directory review questions, email [email protected]. Report security issues as described in SECURITY.md.
Only this repository is the public installation source. It contains manifests, instructions, static skills, and connection metadata—not the MemoStem web or mobile source, MCP implementation, authentication code, database schema, migrations, credentials, environment files, user data, or provider secrets.
Source: README.md at commit 97d1443
Start MemoStem
Start MemoStem when no topic is named. Show a localized welcome App before login, or the connected owner's topic labels and empty-state guidance. Pass the conversation language as locale when known. No drafts are created.
cursorlocaleConnect MemoStem and show topics
Connect or grant knowledge read permission through the host OAuth flow, then show a page of the authenticated owner's topic labels. Never creates knowledge.
cursorlocaleValidate one knowledge bundle
Validate exactly one user-selected, independently teachable general-knowledge bundle without an account and without saving it. Call only at the person's direct request or after clear acceptance of a specific preview proposal. The strict input rejects transcripts, conversation histories, and unsupported knowledge types; phrases that may be personal or organization-specific are returned as review_flags.
bundlesrequiredproviderrequiredprovenancerequiredrequest_idrequiredSave knowledge to a temporary guest shelf
Store one to 10 specifically selected, independently teachable general-knowledge bundles from the current conversation in a private temporary MemoStem guest shelf. Call only after a direct request or clear acceptance of a specific proposal. Reuse workspace_token to continue the same shelf, but never reveal that credential to the person. The shelf is read-only in MemoStem, expires after 90 days, and requires account connection at 10 cards.
bundlesrequiredproviderrequiredprovenancerequiredrequest_idrequiredworkspace_tokenGet a fresh guest shelf link
Issue a new short-lived, one-time mobile or desktop web link for the existing guest shelf. Use only when the person asks to open or recover that shelf. Pass the private workspace_token as a tool argument; never show or put it in a URL. This adds no card and makes the previous view link invalid.
workspace_tokenrequiredConnect and keep a guest knowledge shelf
Transfer the temporary guest shelf identified by workspace_token to the authenticated MemoStem owner as private pending drafts. Call only after the person explicitly agrees to connect or after the guest shelf reports account_required. This tool never approves or publishes cards.
workspace_tokenrequiredPreview one knowledge bundle
Return a transient preview of exactly one user-selected, independently teachable general-knowledge bundle without an account and without saving it. Call only at the person's direct request or after clear acceptance of a specific preview proposal. Use save_guest_knowledge_bundles only after the person explicitly asks to keep it; connected clients use create_knowledge_bundle_drafts.
bundlesrequiredproviderrequiredprovenancerequiredrequest_idrequiredCheck MemoStem connection
Verify the MemoStem connection and report only the currently granted knowledge permissions. Without an account it reports status guest with no permissions, and the temporary guest shelf stays available. This test does not read or write knowledge.
Takes no parameters.
Create knowledge-card drafts
Create pending, user-owned general-knowledge card drafts only after clear affirmative consent to specifically named, independently teachable knowledge in the current conversation. Every card must declare knowledge_scope as general_knowledge. Personal or company decisions, product principles or policies, pricing rationale, preferences, plans, tasks, reminders, meeting outcomes, project status, and autobiographical facts are ineligible. An assistant suggestion alone is not consent. This tool never accepts raw transcripts or historical-conversation data, and it cannot approve, publish, or modify public knowledge cards.
cardsrequiredproviderrequiredprovenancerequiredrequest_idrequiredCreate structured knowledge-bundle drafts
Create pending, user-owned concept, general procedure, comparison, mechanism, structure, claim/evidence, knowledge question, historical event, or language-expression drafts only after clear affirmative consent to specifically named, independently teachable general knowledge in the current conversation. Every bundle must declare knowledge_scope as general_knowledge; decisions and organization-specific material are not accepted. An assistant suggestion alone is not consent. It cannot approve drafts, retain transcripts, or modify public knowledge.
bundlesrequiredproviderrequiredprovenancerequiredrequest_idrequired100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
https://www.memostem.com/api/mcpcodex plugin marketplace add girapphe/memostem-plugins --ref maincodex plugin add memostem@memostemcodex plugin listcodex mcp login memostem --scopes knowledge:drafts:createclaude plugin marketplace add girapphe/memostem-pluginsclaude plugin install memostem@memostemclaude plugin list# Codexcodex plugin marketplace upgrade memostemcodex plugin add memostem@memostemcodex plugin remove memostem@memostem
# Claude Codeclaude plugin marketplace update memostemclaude plugin update memostem@memostemclaude plugin uninstall memostem@memostemclaude plugin marketplace remove memostemnpm run checkpython3 /path/to/plugin-creator/scripts/validate_plugin.py plugins/memostemclaude plugin validate .claude plugin validate plugins/memostem