membridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| membridge_extractA | Extract and categorize portable memories (identity, projects, stack, preferences, rules) from raw text, a ChatGPT/Claude conversations.json export, or a .brain.json. Provide either "text" or "path". |
| membridge_formatA | Convert memories into a ready-to-paste pack for a destination AI. Secrets (API keys, emails) are redacted by default. |
| membridge_redactA | Mask API keys, tokens, and emails in any text. |
| membridge_rememberA | Save a durable memory fact into your local portable brain file (~/.membridge/brain.json) so it persists across Claude, Cursor, Antigravity, and other MCP clients. |
| membridge_recallA | Retrieve and search persisted user memories from the local portable brain (~/.membridge/brain.json). Use this before answering personalized questions or switching AI tools to recall identity, tech stack, active projects, preferences, or rules. Filter by optional keyword query and/or category, and optionally format the result for a specific target platform (e.g. claude, chatgpt, gemini, markdown, json). Returns JSON with matching memory count and items, or a formatted memory pack when target is provided. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| extract-ai-memory | Prompt to dump all stored user memories from ChatGPT, Claude, or Gemini |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Universal AI Memory Quick-Extract Prompt | Prompt to extract stored memories from any AI assistant. |
TDQS
Scored across 5 tools
recall vs remember are clearly read/write opposites, and redact is distinct. However, recall's optional 'target' formatting parameter substantially duplicates membridge_format (both produce a destination-specific memory pack), and extract vs remember have fuzzy boundaries (parse text into memories vs save a fact). An agent could reasonably pick the wrong one for 'give me a Claude-ready pack'.
All five tools use the identical membridge_ prefix with a single lowercase verb (recall, extract, redact, format, remember). No casing or convention mixing.
Five tools is well within the ideal 3-15 range and matches the narrow scope of a portable memory bridge. Each tool maps to a recognizable step: capture, parse, store, retrieve, sanitize, export.
The lifecycle covers create (remember), read/search (recall), import (extract), and export (format/redact). But there is no way to update, delete/forget, or list/clear memories — agents cannot correct a wrong memory or remove stale ones, which is a notable gap for a persistence tool.