Memxus

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.

No repeated explanations. No starting from zero. Better answers, faster.

Glama MCP ServerLicense: AGPL-3.0Node 20+RailwayMCPRegistry v1.2.1

▶️Watch the demo on YouTube·Demo page

Memxus reads yourreal work— not generic memory snippets. Synced content lands in a unified collection per project:project:<slug>.
- Dashboard—dashboard.memxus.com/integrations(GitHub App + Notion OAuth)
- From chat (MCP)—connect_source→check_connect_status→list_syncable_items→set_sync_selection

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 callsrememberand 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 (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

For marketplace reviewers: seeREVIEWER.mdfor OAuth and Bearer token setup.

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)

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_

npm install npm run dev # tsx watch npm run build # tsc → dist/ npm start # node dist/index.js

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

git tag -a vX.Y.Z -m "Memxus MCP vX.Y.Z" git push origin vX.Y.Z

Pushing avtag triggers.github/workflows/release.yml— quality gate + GitHub Release withserver.jsonattached.

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 rungit filter-repo --path .env --invert-pathsbefore publishing.

- GitHub connector (repo sync →project:<slug>)
- Notion connector (workspace page sync)
- MCP Registry v1.2.0 (com.memxus/memxus— AI Context Engine)
- Context Engine connector tools (GitHub/Notion from chat)
- Skill routing (deferred)
- Discord bot connector
- Slack bot connector
- Refresh tokens
- Multi-client OAuth UX
- npm publish

Licensed under theGNU 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.

Memxus Remote MCP Server Copyright (C) 2026 Gabriel Pitrella - Memxus

Historis keeps track of what happened — so you and your AI are never out of sync. Everything lands in one shared timeline, linked to the right people. Ask for the brief: what happened, what you should know, what needs handling.

Local Work Model for AI agents that learns from real outcomes.

Local stdio MCP server for coding agents: shared troubleshooting memory, agent-to-agent help posts, replies, and a unified inbox. Quick start: npx -y agent-only-mcp

One shared context every AI tool your team uses reads and writes over MCP, so Claude Code, Cursor and ChatGPT stay current together.

Open-source LLM knowledge base that turns team chat (Slack, Discord, Teams, Mattermost) into a typed knowledge graph and auto-generated wiki, exposed via a 28-tool MCP server.

Your company's brain, connected to Claude, ChatGPT, Gemini, Cursor, and VS Code. Turn your team's email history into shared memory that any AI assistant can query with natural language.

Open-source team memory layer for AI coding agents. Markdown files in git, a user→team→org hierarchy, one cross-vendor MCP server. Apache-2.0.

Access control, conflict resolution, and audit for shared agent memory.

Search what you've saved, pull up full articles, add new links, and write notes in Memlane