Memside

Name: Memside
Author: memside

by memsideversion 1.0.5i★ –iRuns in the cloud

Registry nameio.github.memside/memside

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Other
You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http memside https://api.memside.com/mcp/ --header 'Authorization: your-value'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "memside": {
      "url": "https://api.memside.com/mcp/",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "memside": {
      "type": "http",
      "url": "https://api.memside.com/mcp/",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

Authorization secret required HTTP header
Bearer token using a Memside API key. Format: Bearer mem_sk_example_key

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account memside, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32380 servers in this category
Published to the registry more recently than 30% of the other 32380 servers in this category
Basic checks equal to or better than 100% of the other 32380 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Memside safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.5) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Dechonet MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Dechonet MCP

by node-man

30 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

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:

Official documentation
Developer quickstart
JavaScript SDK
Python SDK
Capabilities
Continuity and context results
Token savings and context reuse
Memory types and sensitivity
Connect AI clients
Client support matrix
Install in VS Code
Use Memside with API keys
Public API reference
Memside Library and Templates
Curated OpenAPI document
MCP Registry metadata
Directory metadata
Troubleshooting

Developer Quickstart

Select the path that matches the client or integration.

Goal	Use	Start here
Connect ChatGPT, Grok, Claude, or another hosted client	OAuth MCP	Client guides
Connect IDEs and coding agents such as VS Code, Copilot, Cursor, Claude Code, Codex, Antigravity, opencode, or a local MCP client	Bearer-header MCP	VS Code guide
Call Memside from scripts or automation	API key	API keys

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

curl https://api.memside.com/context/startup \

-H "Authorization: Bearer mem_sk_example_key"

For a runnable JavaScript example:

cd examples/javascript

npm 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:

npm install memside

Basic usage:

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:

pip install memside

Basic usage:

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:

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:

Authorization: Bearer mem_sk_example_key

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

"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:

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

The registry entry is published under:

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:

Startup and resume context for compact handoffs.
Operating Rules for durable behavior guidance.
User AI Profile for personal working preferences.
AI Skills for reusable instruction packs.
Public, private, and secret memories for practical data boundaries.
MCP and API-key access for connecting multiple AI clients.
Memside Library and Templates for reusable AI setup and creator workflows.

API Examples

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

curl examples
JavaScript examples
Python examples

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 support@memside.com or use the support links in the Memside app.

Security reports should follow SECURITY.md.

Copyright and Use

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.

Memside

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Dechonet MCP

README from the maker

Memside

Continuity With Less Repeated Prompting

Connect Memside

Developer Quickstart

JavaScript SDK

Python SDK

MCP Server Setup

MCP Registry

Supported Workflows

Key Features

API Examples

Public Repo Scope

Support

Copyright and Use