MemoStem

io.github.girapphe由 GitHub 账号 girapphe 发布v0.6.3更新于 Oct 24, 2026

Your reviewed knowledge, across AI conversations.

已验证Streamable HTTP可网页运行效率与工作流知识与记忆

概览

AI 生成的概览

MemoStem 让助手把对话中选定的通用知识保存为私人草稿,并在之后的对话中复用你已审核的知识。

可以做什么
  • 启动引导、连接账号并查看已授予的权限
  • 在不保存的情况下预览或校验单个选定的知识包
  • 把选定知识存入私人访客书架并生成一次性查看链接
  • 登录后将访客书架转入账号下的待审草稿
  • 根据已确认的内容创建待审卡片或结构化知识草稿
  • 检索、搜索并分页浏览账号下已批准的知识及草稿状态
适用场景
适合希望把某个 AI 对话中讲清楚的知识留存下来、并在另一个对话中复用的场景,也适合让助手依据你自己审核过的笔记而非通用训练数据来回答。适合愿意逐条确认保存内容、而不愿上传整段对话的人。
运行要求
需要远程 Streamable HTTP 端点,无需本地安装包。访客保存无需账号,但转入账号或使用受保护工具需要 MemoStem OAuth 登录。读取与状态工具需要 knowledge:context:read 和 knowledge:drafts:status 权限;新连接会申请 openid、knowledge:drafts:create、knowledge:context:read 和 knowledge:drafts:status。部分宿主还有额外条件,例如 Gemini 要求美国地区且年满 18 岁。
安装前请注意
草稿在你于 MemoStem 中批准前都是私人的待审状态,创建工具无法发布或批准。workspace_token 是私有的续接凭据,不得显示或记录。保存的内容会发送到 MemoStem 的托管服务,但不会发送完整对话记录。个人、公司、机密或凭据类内容不在采集范围内。已有的 OAuth 授权不会自动升级,读取权限可能需要重新连接。

安装

在 SourceWeft 中

  1. 打开 控制台中的 MemoStem,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.girapphe%2Fmemostem/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "memostem": {
      "type": "http",
      "url": "https://www.memostem.com/api/mcp"
    }
  }
}

README

[MemoStem Recall Sprout logo]

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.

IntentEnglish한국어
SaveSave this explanation of EUV lithography as one atomic memo draft.방금 설명한 EUV 노광 원리를 메모 초안 하나로 저장해 줘.
RetrieveFind my approved MemoStem knowledge about EUV.MemoStem에서 내가 승인한 EUV 지식을 찾아줘.
SelectShow candidates from the concepts we just discussed.방금 이야기한 개념 중 저장할 후보를 보여줘.

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.

What you wantTry sayingWhat should happen
Choose what to keep“방금 설명한 개념 중 저장할 후보를 보여줘.”Preview candidates, then save only your selection.
Save a named idea“삼투압 원리를 메모 초안 하나로 저장해 줘.”Save the selected idea once; no repeated consent question.
Reuse reviewed knowledge“내가 승인한 EUV 지식으로 이번 질문에 답해 줘.”Search your active confirmed knowledge and identify the sources used.
Practice in this chat“내가 승인한 EUV 지식으로 한 문제씩 퀴즈를 내 줘.”Retrieve the selected knowledge, ask one question at a time, and keep the exercise in chat.
Propose an improvement“기존 삼투압 메모에 이 설명을 보완하는 초안을 만들어 줘.”Prepare a complete pending proposal for your review.
Check a previous save“방금 만든 초안이 아직 검토 대기인지 확인해 줘.”Check the known batch when status permission is available.

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:

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

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

Secondary channels: install the Git plugin

Codex

bash
codex plugin marketplace add girapphe/memostem-plugins --ref maincodex plugin add memostem@memostemcodex plugin listcodex mcp login memostem --scopes knowledge:drafts:create

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.

ChatGPT marketplace update

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.

Claude Code

bash
claude plugin marketplace add girapphe/memostem-pluginsclaude plugin install memostem@memostemclaude plugin list

Run /reload-plugins, then /mcp to inspect the connection and complete OAuth when prompted.

Update or remove

bash
# 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 memostem

What the MCP exposes

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.

Included skills

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.

Directory publication

  • The remote server metadata is published from server.json to the official MCP Registry when a GitHub Release is published.
  • Paste-ready OpenAI, Anthropic and Kimi listing copy, prompts, review cases, and activation gates live in docs/directory-submissions.md.
  • Five-channel evidence, account prerequisites and follow-up Issues are in the readiness record.
  • Provider review and approval are external states. A public GitHub repository or a successful MCP Registry workflow does not prove an OpenAI or Anthropic directory listing is live.

Portable package

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.

Validate locally

bash
npm run checkpython3 /path/to/plugin-creator/scripts/validate_plugin.py plugins/memostemclaude plugin validate .claude plugin validate plugins/memostem

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.

Contact

For support, partnership, or directory review questions, email [email protected]. Report security issues as described in SECURITY.md.

Publication boundary

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.

来源:README.md,提交 97d1443

工具

10

start_memostem

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.

输入参数cursorlocale

connect_memostem

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

输入参数cursorlocale

validate_knowledge_bundle

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

输入参数bundles必填provider必填provenance必填request_id必填

save_guest_knowledge_bundles

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

输入参数bundles必填provider必填provenance必填request_id必填workspace_token

claim_guest_knowledge_workspace

Connect 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_token必填

preview_knowledge_bundle

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

输入参数bundles必填provider必填provenance必填request_id必填

check_memostem_connection

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

无需输入参数。

create_card_drafts

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.

输入参数cards必填provider必填provenance必填request_id必填

create_knowledge_bundle_drafts

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

输入参数bundles必填provider必填provenance必填request_id必填

版本历史

4
  1. v0.6.3最新Oct 16, 2026
  2. v0.6.2Sep 23, 2026
  3. v0.6.1Sep 22, 2026
  4. v0.5.3Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分