Skip to content

Add memxus configuration to mcp-servers.json#2355

Open
gpitrella wants to merge 3 commits into
affaan-m:mainfrom
gpitrella:add-memxus-mcp-server
Open

Add memxus configuration to mcp-servers.json#2355
gpitrella wants to merge 3 commits into
affaan-m:mainfrom
gpitrella:add-memxus-mcp-server

Conversation

@gpitrella

Copy link
Copy Markdown

What Changed

Added Memxus to mcp-configs/mcp-servers.json as a remote HTTP MCP server for persistent memory.

Why This Change

Memxus is a universal persistent memory layer for AI tools — saves context once across Claude Code, Cursor, Gemini CLI and any MCP-compatible tool, and recalls it automatically in every session. Connects GitHub + Notion as context sources. Free tier available at memxus.com.

Listed on: registry.modelcontextprotocol.io, Glama and Smithery

Testing Done

  • Manual testing completed — endpoint https://mcp.memxus.com/mcp responds correctly
  • JSON validates cleanly
  • No secrets committed (uses YOUR_MEMXUS_API_KEY_HERE placeholder)

Type of Change

  • feat: New feature

Security & Quality Checklist

  • No secrets or API keys committed
  • JSON files validate cleanly
  • Follows conventional commits format

Added configuration for Memxus service with API key placeholder and description.
@gpitrella gpitrella requested a review from affaan-m as a code owner June 24, 2026 18:54
@coderabbitai

coderabbitai Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: f2128143-cd96-43d9-842b-ef44c2d0e8f3

📥 Commits

Reviewing files that changed from the base of the PR and between 66345cd and 4280c79.

📒 Files selected for processing (1)
  • mcp-configs/mcp-servers.json
📜 Recent review details
🧰 Additional context used
📓 Path-based instructions (2)
**/*.{js,ts,jsx,tsx,py,java,cs,rb,go,php,swift,kt,rs,c,cpp,h,hpp,properties,yml,yaml,json,env,config}

📄 CodeRabbit inference engine (.cursor/rules/common-security.md)

NEVER hardcode secrets in source code - ALWAYS use environment variables or a secret manager

Files:

  • mcp-configs/mcp-servers.json
**/*.{js,ts,jsx,tsx,json,env*}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Do not hardcode secrets, API keys, passwords, or tokens

Files:

  • mcp-configs/mcp-servers.json
🧠 Learnings (1)
📚 Learning: 2026-06-17T07:32:15.038Z
Learnt from: Minkeez
Repo: affaan-m/ECC PR: 2280
File: agents/al-build-resolver.md:30-30
Timestamp: 2026-06-17T07:32:15.038Z
Learning: In this repo, MCP server config JSON files under `mcp-configs/` use `mcpServers` as the top-level key (not `servers`). When querying MCP server entries with `jq`, read from `.mcpServers` (e.g., `jq '.mcpServers["microsoft-learn"]' mcp-configs/mcp-servers.json`) rather than iterating `.servers[]`.

Applied to files:

  • mcp-configs/mcp-servers.json
🔇 Additional comments (1)
mcp-configs/mcp-servers.json (1)

131-131: LGTM!


📝 Walkthrough

Summary by CodeRabbit

  • New Features
    • Added a new MCP server connection option for Memxus, available over HTTP.
    • Included setup guidance for authenticating with an API key using a Bearer token.

Walkthrough

Adds a new memxus MCP server entry in mcp-configs/mcp-servers.json with HTTP transport, an authorization header placeholder, and a persistent-memory description.

Changes

MCP server configuration

Layer / File(s) Summary
Add memxus server entry
mcp-configs/mcp-servers.json
Adds a memxus MCP server definition with HTTP transport, an Authorization header placeholder, and descriptive text.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

  • affaan-m

Poem

A tiny key to a memory door,
memxus settles in the config store.
One HTTP path, one header to hold,
A new little bridge in JSON told.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: adding a Memxus MCP server entry to mcp-servers.json.
Description check ✅ Passed The description is clearly related to the change and matches the added Memxus MCP server configuration.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@greptile-apps

greptile-apps Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR adds memxus as a cloud-hosted HTTP MCP server to the mcp-configs/mcp-servers.json template, providing cross-tool persistent memory (Claude Code, Cursor, Gemini CLI, etc.) via https://mcp.memxus.com/mcp.

  • The entry follows the existing headers-based auth pattern already used by browser-use, with a proper YOUR_MEMXUS_API_KEY_HERE placeholder as required by SECURITY.md.
  • The description now includes the agreed-upon prompt-injection / memory-poisoning warning from the previous review thread.
  • No secrets are committed; JSON structure is valid and consistent with the rest of the file.

Confidence Score: 5/5

Safe to merge — this is a single config template entry with no real credentials, a proper placeholder, and a security warning already incorporated per the previous review discussion.

The change is a one-entry addition to a config template. It uses the YOUR_MEMXUS_API_KEY_HERE placeholder pattern required by SECURITY.md, mirrors the headers-based auth format already used by browser-use, and the description now carries the agreed prompt-injection warning from the earlier thread. No logic paths, no executable code, and no secrets are affected.

No files require special attention.

Important Files Changed

Filename Overview
mcp-configs/mcp-servers.json Adds memxus HTTP MCP entry with bearer-token auth placeholder and security warning in description; format matches existing browser-use pattern; no real credentials committed.

Sequence Diagram

%%{init: {'theme': 'neutral'}}%%
sequenceDiagram
    participant Agent as AI Agent (Claude Code / Cursor)
    participant MCP as MCP Client
    participant Memxus as mcp.memxus.com/mcp
    participant Src as GitHub / Notion (context sources)

    Agent->>MCP: Tool call (save_memory / recall_memory)
    MCP->>Memxus: "HTTP POST with Authorization: Bearer <key>"
    Memxus-->>MCP: Stored / recalled context
    MCP-->>Agent: Context injected into session

    Note over Memxus,Src: Memxus auto-indexes connected sources
    Src-->>Memxus: Commit messages, Notion pages (auto-indexed)
    Note over Agent,MCP: Auto-recall surfaces external content into context window each session
Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
sequenceDiagram
    participant Agent as AI Agent (Claude Code / Cursor)
    participant MCP as MCP Client
    participant Memxus as mcp.memxus.com/mcp
    participant Src as GitHub / Notion (context sources)

    Agent->>MCP: Tool call (save_memory / recall_memory)
    MCP->>Memxus: "HTTP POST with Authorization: Bearer <key>"
    Memxus-->>MCP: Stored / recalled context
    MCP-->>Agent: Context injected into session

    Note over Memxus,Src: Memxus auto-indexes connected sources
    Src-->>Memxus: Commit messages, Notion pages (auto-indexed)
    Note over Agent,MCP: Auto-recall surfaces external content into context window each session
Loading

Reviews (2): Last reviewed commit: "Update description in mcp-servers.json" | Re-trigger Greptile

Comment thread mcp-configs/mcp-servers.json
Updated the description to include a note about reviewing stored memories to prevent prompt-injection.
Update description in mcp-servers.json

@daltino daltino left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR adds a "memxus" configuration to mcp-servers.json, which integrates a memory persistence feature for AI tools via an HTTP endpoint. The addition is clear and includes necessary details such as URL, headers, and a helpful description. The contribution aligns with the repo's intent of supporting customizable MCP integrations. The configuration looks well-documented, but contributors should ensure sensitive keys like YOUR_MEMXUS_API_KEY_HERE are properly managed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants