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 your memory into one assistant.

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

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

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

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

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

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

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

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

Authorization: Bearer mem_sk_your_memside_api_key

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

{ "servers": { "memside": { "type": "http", "url": "https://api.memside.com/mcp/", "headers": { "Authorization": "Bearer mem_sk_your_memside_api_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.

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

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.

With Memside connected, an AI tool can search your saved memories, fetch specific context, create new memories after you approve, 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 is useful when you want to move a project between ChatGPT, Claude, Grok, IDEs, coding agents, or other compatible AI clients. Memside can help the next AI understand what you are building, what decisions were already made, what rules it should follow, and what the next step is.

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.

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

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.

- 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

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

Copyright (c) 2026 Memside. All rights reserved.

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

Persistent memory for AI assistants and coding agents across ChatGPT, Claude, Cursor, and other MCP-compatible tools.

One shared, versioned memory for your AI agents across Claude Code, Cursor, Kiro and Grok, with a source on every answer and full history.

Operational memory for AI agents that persists across sessions and tools.

MCP (Model Context Protocol) server that exposes 70 tools spanning cognitive memory, working memory, sessions, agents, the L0–L3 knowledge hierarchy, orchestration tasks, and training pipelines. The server speaks stdio and is consumed by Claude Desktop, Claude Code, OpenCodex, and any MCP-aware client.

MEMANTO is a memory agent. It remembers, recalls, and answers — so your agents can achieve long-term goals and avoid confusion.

A local-first, LLM-agnostic memory layer for AI assistants

Hosted MCP memory across Claude Code, Cursor, ChatGPT and any MCP client. Community-hosted instance of the MIT-licensed MemPalace engine. EU-hosted, GDPR-compliant. Free tier with 200 memories.

Shared memory layer for AI coding agents with dream pipeline distillation, session grounding, and multi-instance coherence.

Your portable context layer — load it into any AI.