MemoStem

MemoStem across AI conversations

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.

Save here, reuse in another AI conversation

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.

Why MemoStem

• Get a timely suggestion. In supported plugin clients, the assistant can name a reusable result and ask whether to keep it, so you do not need to remember a MemoStem or card command.
• Confirm, don't scrape. Nothing is transferred when the AI notices an idea. Only the specific suggestion you confirm is sent, never a transcript or hidden history. If you invoke MemoStem without naming material and the current chat has no eligible candidate, the same flow may use recent conversation context the host explicitly provides; it cannot browse unavailable conversation history.
• Start without an account. Keep up to ten selected cards in a private guest shelf for 90 days. The shelf is read-only in MemoStem; connecting moves its cards to your private pending Candidate Inbox for review.
• Keep knowledge teachable. Create an atomic memo for one concept or a question-and-answer draft for one retrieval question.
• Reuse only your knowledge. A read-authorized connection can retrieve the signed-in owner's confirmed knowledge and, only when explicitly requested, inspect its lifecycle state.

Everyday workflows

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.

No lifecycle hooks

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.

Ask for useful cards

• Concept: “Save how rain forms as one concise concept card, with a definition and an example.”
• Retrieval question: “Make one question-and-answer card about why cooling air forms water droplets, using what we just discussed.”
• Selection first: “Show me candidates for the weather concepts we discussed so I can choose which to keep.”

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.

Connect from an AI app

The production Streamable HTTP MCP endpoint is:

https://www.memostem.com/api/mcp

ChatGPT

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= . 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.

Claude

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.

Kimi

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.

Gemini

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.

Grok

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.

Consent-first proactive capture

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 d