Memside MCP Server

Memside

Memside is an AI continuity and memory hub for people who work across ChatGPT, Claude, developer tools, browsers, and different devices. It gives you a private place to save reusable context, decisions, operating rules, project notes, and checkpoints so you can move from one AI to another without rebuilding the same background every time.

Use Memside when you want your AI context to survive beyond one chat window. A connected AI tool can retrieve the right memory, continue a project from a checkpoint, follow your saved working preferences, or create new durable context after you approve it. This repository is the public home for Memside integration docs, examples, and support information. It is not a mirror of the private production application source.

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

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

If your AI tool supports OAuth for MCP, choose OAuth during setup and sign in with your Memside account. If your tool supports API-key auth instead, create an API key in Memside and use it as a bearer token.

Start here:

• Capabilities
• Token savings and context reuse
• Memory types and sensitivity
• Connect AI clients
• Install in VS Code
• Use Memside with API keys
• Troubleshooting

What You Can Do

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, local coding tools, or other MCP-compatible 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.

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.

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.

Public Repo Scope

This repo contains:

• setup guides for MCP clients
• MCP Registry metadata
• technical product capability docs
• API-key usage examples
• public troubleshooting notes
• security and support information
• public changelog entries

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

Copyright (c) 2026 Memside. All rights reserved.

This repository contains public documentation, examples, and integration guidance for Memside.

You may view, reference, and link to this repository for learning about Memside and its integrations.

You may not copy, modify, redistribute, sublicense, publish, sell, or use substantial portions of this repository's contents for another product, service, documentation site, marketplace listing, or commercial purpose without written permission from Memside.

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

This repository does not grant any license to Memside's application source code, backend services, APIs, trademarks, product designs, or proprietary systems.