Memside

io.github.memsidePublished by GitHub account memsidev1.0.5Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Memside is a hosted memory and continuity hub that lets an assistant save, search and resume project context across different AI tools.

What you can do
  • Search, fetch and create approved memories, profiles and operating rules
  • Build compact startup or resume packets to continue a project from a checkpoint
  • Update checkpoints and keep durable context between chat and IDE sessions
  • Browse read-only public Library Templates and manage permission-controlled creator drafts and publication workflows
When to use it
Useful when you move work between ChatGPT, Claude, Grok, IDEs or coding agents and want saved preferences, decisions and project state to carry over instead of re-pasting long prompts. Also relevant if you want reusable rules and templates shared across compatible AI clients.
Requirements
A remote MCP endpoint over Streamable HTTP; no local package. Authentication is required: OAuth sign-in with Memside, or an API key sent as an Authorization bearer header. A Memside account is needed.
Before you install
The connection carries a Memside API key or OAuth session; keep real keys out of shared config files and use user-level or secret storage. The assistant can create and update memories and checkpoints, so stored context persists across tools. Private data is scoped to the signed-in user and secret memories are excluded from AI-facing flows, but review what gets saved.

Installation

In SourceWeft

  1. Open Memside in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

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.memside%2Fmemside/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

Source: README.md at commit 43328e4

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.5LatestSep 16, 2026

Score

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

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.