Potencialize seu agente
A URL do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
https://mcp.memxus.com/mcpO botão do Claude acima abre o Claude com o nome e a URL preenchidos. Você ainda precisa confirmar lá.
claude mcp add --transport http com.memxus-memxus https://mcp.memxus.com/mcpRun in a terminal.
{ "mcpServers": { "com.memxus-memxus": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.memxus.com/mcp" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
Multiply your productivity by giving every AI the right context.
Memxus brings Context Engineering to your entire AI workflow.
Save your real decisions, preferences and work context once. Find them in seconds and give Claude, Cursor, ChatGPT, Gemini or any MCP client the exact context required for each task.
Persistent memory layer that saves and recalls your project context and preferences.
No repeated explanations. No starting from zero. Better answers, faster.
AI tools are powerful, but their productivity drops when they do not have the right context.
Claude does not know what Cursor knows. Cursor does not know what ChatGPT knows. Your project decisions, preferences, architecture and workflow context get repeated across every tool and every new conversation.
That creates unnecessary work:
Memxus solves this through Context Engineering.
Save what matters once, find it in seconds and give every AI the exact context it needs for the task.
The result is less repetition, less back-and-forth, faster execution and better answers across your entire AI workflow.
Save a decision in Claude → recall it in Cursor → reuse it in ChatGPT.
Need deeper context? Connect GitHub and Notion whenever you are ready.
Memxus is a Context Engineering designed to multiply your productivity by giving every AI the right context.
It creates a shared context layer across Claude, Cursor, ChatGPT, Gemini and any MCP-compatible client.
The core workflow is simple:
remember what mattersrecall it from any AIConnect once with OAuth and your decisions, preferences and work context become portable across your entire AI workflow — without local setup, repeated explanations or copying and pasting between tools.
For deeper context, Memxus can also connect to real work sources such as GitHub and Notion. Repositories, documentation, commits, pull requests, issues and selected workspace pages become searchable alongside your manually saved context.
GitHub and Notion connectors are live in production. This deeper synchronization is optional: Memxus delivers value from the first saved decision.
Save once. Find it fast. Give every AI the right context. Work faster.
Memxus reads your real work — not generic memory snippets. Synced content lands in a unified collection per project: project:<slug>.
What gets synced
How to connect
connect_source → check_connect_status → list_syncable_items → set_sync_selectionHow to use synced context
Call recall or get_context with collection=project:<slug> (or let semantic search find it). GitHub/Notion content is tagged and searchable alongside manual memories.
flowchart LR
Save["💾 Save — from any AI"] --> Memxus["🧠 Memxus — your persistent memory"] --> Recall["✨ Recall anywhere — Claude · Cursor · ChatGPT · Gemini"]
After you connect Memxus to any AI, paste a line like this — Memxus calls remember and your context is available everywhere:
Remember this in Memxus: we use Postgres + pgvector for semantic search.
No GitHub/Notion sync needed to start. Sync later when you want deeper project context.
Optional — sync your whole stack: GitHub repos, Notion pages, files, docs and decisions become recallable context too.
Context Engine connector tools (4): connect GitHub/Notion from chat via MCP. Production advertises the 9 core tools; the 4 connector tools are enabled per account, so a newly connected client sees the core 9.
URL: https://mcp.memxus.com/mcp
Auth: OAuth 2.1 (handled automatically)
Transport: Streamable HTTP
claude_desktop_config.json){
"mcpServers": {
"memxus": {
"url": "https://mcp.memxus.com/mcp",
"transport": "streamable-http"
}
}
}
{
"mcp": {
"servers": {
"memxus": {
"url": "https://mcp.memxus.com/mcp",
"transport": "http"
}
}
}
}
Or open directly in Glama Inspector →
[https://glama.ai/mcp/inspector?url=https://mcp.memxus.com/mcp](https://glama.ai/mcp/inspector?url=https://mcp.memxus.com/mcp)
For marketplace reviewers: see REVIEWER.md for OAuth and Bearer token setup.
Registry com.memxus/memxus v1.2.1 — 9 core tools always available, plus 4 connector tools for GitHub/Notion sync from chat.
Full tool reference: memxus.com/docs/mcp · Marketplace reviewers: REVIEWER.md
GitHub App ──┐
Notion OAuth ┼──► sync (API + connector tools) ──► Supabase project:<slug>
Manual MCP ┘ │
│ pgvector
MCP Client (Claude, Cursor, etc.) │
│ │
│ POST /mcp Bearer aimem_* │
▼ ▼
mcp.memxus.com ← This repo (Railway) ──────────► Supabase (Postgres + pgvector)
│
▼
Dash-AIMemory (Dashboard + integrations)
Sync runs server-side via dashboard or MCP connector tools — no local files to manage.
Transport: Streamable HTTP (MCP 2.0)
Auth: OAuth 2.1 + PKCE + Dynamic Client Registration (RFC 9728)
1. Client → GET /.well-known/oauth-authorization-server
2. Client → GET /oauth/authorize → redirect to dashboard login
3. User signs in (Google) in the dashboard
4. Client → POST /oauth/token (PKCE) → aimem_* bearer token
5. Client → POST /mcp Authorization: Bearer aimem_*
Dynamic Client Registration is supported — clients register automatically on first connect.
supabase/migration.sql after the dashboard migration)cp .env.example .env
npm install
npm run dev # tsx watch
npm run build # tsc → dist/
npm start # node dist/index.js
Set all variables under Settings → Variables (never commit .env).
MCP_PUBLIC_URL = your Railway networking URL (no trailing /mcp).
Health check endpoint: /health (configured in [railway.toml](railway.toml)).
Note: Node 20 on Railway — Supabase Realtime needs the
wspackage (configured insrc/lib/supabase.ts).
Optional: setRAILPACK_NODE_VERSION=22for native WebSocket support.
npm install
npm run dev # tsx watch
npm run lint # ESLint
npm run typecheck # tsc --noEmit
npm run build # compile → dist/
npm start # node dist/index.js
Marketplace reviewers: REVIEWER.md · MCP docs: memxus.com/docs/mcp · Registry: com.memxus/memxus v1.2.1
## [Unreleased] in [CHANGELOG.md](CHANGELOG.md)package.json, server.json, src/mcp/server.ts, and src/mcp/public-discovery.ts## [X.Y.Z] - YYYY-MM-DDgit tag -a vX.Y.Z -m "Memxus MCP vX.Y.Z"
git push origin vX.Y.Z
Pushing a v* tag triggers [.github/workflows/release.yml](.github/workflows/release.yml) — quality gate + GitHub Release with server.json attached.
Run from the repo root before making the repository public.
Last audit: 2026-06-17 — PASSED
# 1. Verify .env was never committed
git log --all --full-history -- .env .env.local .env.production
# 2. Check for .env* files added in history
git log --all --oneline --diff-filter=A -- "*.env*"
# 3. Grep current tree for dangerous patterns (exclude .example)
git grep -rn -E "(service_role|anon_key|sk-[a-zA-Z0-9]{20,}|aimem_[a-zA-Z0-9]+|eyJ[a-zA-Z0-9_-]{20,})" \
-- ":(exclude)*.example" ":(exclude)CHANGELOG*"
# 4. Search full git history for leaked keys
git log --all -p --follow -S "service_role" -- . | head -100
git log --all -p --follow -S "SUPABASE_SERVICE_ROLE_KEY=" -- . | head -100
If commands 1 or 4 find real secrets, rotate keys immediately and run git filter-repo --path .env --invert-paths before publishing.
project:<slug>)com.memxus/memxus — AI Context Engine)Licensed under the GNU Affero General Public License v3.0 (AGPL-3.0).
You can use, modify, and distribute this code freely. If you use it to run a network service (SaaS), you must publish your source code under the same license.
© 2026 Gabriel Pitrella · memxus.com
Memxus Remote MCP Server
Copyright (C) 2026 Gabriel Pitrella - Memxus
Persistent memory layer that saves and recalls your project context and preferences.
{ "mcpServers": { "com.memxus-memxus": { "url": "https://mcp.memxus.com/mcp", "headers": {} } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração http para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Memxus é acessado por HTTP.
Última verificação: 2026-11-08. Persistent memory layer that saves and recalls your project context and preferences.