Memside

io.github.memside由 GitHub 帳號 memside 發布v1.0.5更新於 Oct 24, 2026

AI continuity and Library Templates: memories, profiles, rules, tasks, and checkpoints.

已驗證Streamable HTTP可網頁執行效率與工作流知識與記憶

概覽

AI 產生的概覽

Memside 是託管的記憶與延續性中樞,讓助理在不同 AI 工具之間儲存、檢索並接續專案脈絡。

可以做什麼
  • 搜尋、取得並建立經核准的記憶、使用者設定檔與操作規則
  • 產生精簡的啟動或接續脈絡包,從檢查點繼續專案
  • 更新檢查點,在對話與 IDE 工作階段之間保留持久脈絡
  • 瀏覽唯讀的公開 Library 範本,並管理受權限控制的創作者草稿與發布流程
適用情境
適合在 ChatGPT、Claude、Grok、IDE 或編碼代理之間切換工作時使用,讓已儲存的偏好、決策與專案狀態隨之轉移,不必反覆貼上長提示。也適合需要跨相容 AI 用戶端重複使用規則與範本的情境。
執行需求
需要遠端 MCP 端點(Streamable HTTP),不需本機安裝套件。必須驗證:透過 Memside 的 OAuth 登入,或以 Authorization 標頭攜帶 Bearer API 金鑰。需要 Memside 帳號。
安裝前請注意
連線會攜帶 Memside API 金鑰或 OAuth 工作階段,請勿把真實金鑰寫進共用設定檔,應使用使用者層級設定或密鑰儲存。助理可建立與更新記憶和檢查點,這些脈絡會跨工具長期保留。私有資料依登入使用者隔離,secret 記憶不會進入面向 AI 的流程,但仍應留意儲存了哪些內容。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Memside,將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.memside%2Fmemside/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

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

README

Memside

Memside is an AI continuity and memory hub for work across ChatGPT, Claude, Grok, IDEs, coding agents, and other AI tools that support OAuth, MCP, or API-key connections. It provides a private place for reusable context, decisions, Operating Rules, project notes, checkpoints, and Library Templates that can move between compatible AI tools.

Memside keeps AI context available beyond one chat window. A connected AI tool can retrieve relevant memories, continue a project from a checkpoint, follow saved working preferences, create approved durable context, and work with permission-controlled Library Templates. This repository is the public home for Memside integration documentation, examples, SDKs, and support information. It is not a mirror of the private production application source.

Product site: https://www.memside.com

Documentation: https://docs.memside.com

Continuity With Less Repeated Prompting

Memside is built to give AI assistants the right context at the right time: current task state, saved preferences, project notes, checkpoints, and reusable rules. In internal testing and early pilot usage, this helped AI tools stay on track without requiring users to rebuild the same detailed prompt in every new chat or IDE session.

High-level test results:

Context approachContinuity score
No Context~45%
Long Context Dump~84-85%
Memside Context~96-99%
Very Detailed Manual Prompt~97-99%

Token savings: in separate context-reuse tests, Memside reduced repeated full-context transfer by 83-91% on representative light, medium, and heavy project datasets.

A very detailed manual prompt means a long prompt where the user includes every important detail by hand: project state, preferences, decisions, references, and next steps. With Memside, the workflow is simpler: ask the AI to save the checkpoint, references, and useful context, then move to a new chat and ask it to continue from that checkpoint using Memside.

Results are based on internal tests and early pilot usage patterns. Performance varies by model, provider, prompt style, and workflow. See Continuity and context results for details.

Connect Memside

Memside supports hosted MCP access for AI tools that can connect to remote MCP servers. MCP gives compatible AI clients a standard way to use Memside as a continuity layer instead of locking memory into one assistant.

text
https://api.memside.com/mcp/

For AI tools that support OAuth for MCP, setup continues through Memside sign-in. AI tools that support API-key authentication can use a Memside API key as a bearer token.

Start here:

Developer Quickstart

Select the path that matches the client or integration.

GoalUseStart here
Connect ChatGPT, Grok, Claude, or another hosted clientOAuth MCPClient guides
Connect IDEs and coding agents such as VS Code, Copilot, Cursor, Claude Code, Codex, Antigravity, opencode, or a local MCP clientBearer-header MCPVS Code guide
Call Memside from scripts or automationAPI keyAPI keys

For a direct API check, create a Memside API key and run:

bash
curl https://api.memside.com/context/startup \  -H "Authorization: Bearer mem_sk_example_key"

For a runnable JavaScript example:

bash
cd examples/javascriptnpm run startup

Set MEMSIDE_API_KEY before running examples. See Developer quickstart for the full setup.

JavaScript SDK

Memside publishes a lightweight JavaScript SDK for public API-key workflows:

bash
npm install memside

Basic usage:

js
import { MemsideClient } from "memside";
const memside = new MemsideClient({  apiKey: process.env.MEMSIDE_API_KEY});
const startup = await memside.context.startup();console.log(startup);

The JavaScript SDK wraps public Memside API routes for startup context, resume context, workspace profile, Memory operations, Subject organization, and Library Template workflows. See packages/memside for package details.

Python SDK

Memside also publishes a lightweight Python SDK for public API-key workflows:

bash
pip install memside

Basic usage:

python
from memside import MemsideClient
client = MemsideClient(api_key="mem_sk_example_key")
startup = client.context_startup()print(startup)

The Python SDK wraps the same public Memside API areas as the JavaScript SDK. See packages/python for package details.

MCP Server Setup

Use this hosted MCP server URL in clients that support remote MCP:

text
https://api.memside.com/mcp/

For ChatGPT, Grok, Claude, and other clients that offer OAuth during MCP setup, choose OAuth and complete Memside sign-in.

For clients that use bearer headers, create a Memside API key and pass it as:

text
Authorization: Bearer mem_sk_example_key

VS Code and GitHub Copilot can use a workspace .vscode/mcp.json file:

json
{  "servers": {    "memside": {      "type": "http",      "url": "https://api.memside.com/mcp/",      "headers": {        "Authorization": "Bearer mem_sk_example_key"      }    }  }}

Keep real API keys out of shared files. Use local user-level configuration or secret storage when the config is shared with a team.

Detailed setup guides are available for VS Code, GitHub Copilot, ChatGPT, Grok, Claude Code, Cursor, Codex, Antigravity, and opencode.

MCP Registry

This repository includes server.json for the official MCP Registry. It describes Memside as a hosted remote MCP server using Streamable HTTP at:

text
https://api.memside.com/mcp/

The registry entry is published under:

text
io.github.memside/memside

See MCP Registry metadata for registry and endpoint checks.

This repository also includes lightweight third-party directory metadata for Glama, Open Plugins, and Cursor plugin discovery. These files point to the same hosted MCP server URL and do not contain credentials.

Supported Workflows

With Memside connected, an AI tool can search saved memories, fetch specific context, create approved memories, update checkpoints, and build compact startup or resume packets. The goal is to keep useful context portable without turning every AI conversation into a long manual setup step.

This supports project movement between ChatGPT, Claude, Grok, IDEs, coding agents, and other compatible AI clients. The next AI can retrieve the project purpose, prior decisions, applicable rules, and current next step.

Memside Library adds reusable Templates for profiles, Operating Rules, AI Skills, memories, references, examples, and repeatable workflows. Public catalog discovery is read-only. Permission-controlled creator operations can search Templates, read owned drafts, replace drafts safely, and manage reviewed publication workflows. See Memside Library and Templates.

Memside keeps the normal product boundary intact. Private user data is scoped to the signed-in user, secret memories are excluded from AI-facing MCP and API-key flows, and destructive actions require stronger confirmation.

Key Features

Memside is designed around continuity, selective context retrieval, and user control. The core features are:

API Examples

The examples in this repo use public Memside API surfaces only.

The JavaScript and Python examples use normal HTTP requests against public Memside API surfaces.

The machine-readable OpenAPI document contains only the approved API-key contract. It excludes signed-in application, account, administration, billing, and infrastructure operations.

Public Repo Scope

This repo contains:

  • setup guides for MCP clients
  • MCP Registry metadata
  • third-party MCP directory metadata
  • Cursor plugin metadata
  • technical product capability docs
  • API-key usage examples
  • developer quickstart and runnable examples
  • public troubleshooting notes
  • security and support information
  • public changelog entries
  • public Library and Template integration guidance

This repo does not contain:

  • private Memside application source
  • secrets or deployment configuration
  • database or internal operations notes
  • non-public product architecture

Support

For support, contact [email protected] or use the support links in the Memside app.

Security reports should follow SECURITY.md.

Copyright and Use

Copyright (c) 2026 Memside. All rights reserved.

This repository is public documentation, not open-source application code. See LICENSE.md for the repository terms.

Memside and related names, product concepts, documentation, and branding remain the property of their respective owners.

來源:README.md,提交 43328e4

工具

0
該伺服器需要登入,因此 SourceWeft 無法在沒有帳號的情況下讀取其工具,也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

1
  1. v1.0.5最新Sep 16, 2026

評分

已滿足適用檢查項的 75%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。