Global Agent Memory

Name: Global Agent Memory
Author: ozankasikci

by ozankasikciversion 0.1.6i★ –iRuns on your computer

Registry nameio.github.ozankasikci/global-agent-memory

Install

Overview

Description from the maker (original English)

Shared, project-aware memory for Claude Code, Codex, and other agents with human review.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "global-agent-memory": {
      "command": "uvx",
      "args": [
        "global-memory-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add global-agent-memory -- uvx global-memory-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "global-agent-memory": {
      "command": "uvx",
      "args": [
        "global-memory-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "global-agent-memory": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "global-memory-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account ozankasikci, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 7282 servers in this category
Published to the registry more recently than 22% of the other 7282 servers in this category
Basic checks equal to or better than 100% of the other 7282 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Global Agent Memory safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.6) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Global Agent Memory

Local-first, project-aware, durable memory for Claude Code, Codex, and other

MCP-compatible agents.

Global Agent Memory gives multiple coding agents one shared, reviewable memory without handing control of your knowledge base to a hosted service. Markdown files are canonical, a hybrid local MCP runtime is the public agent interface, and the dashboard lets a human approve, edit, protect, or remove what agents remember. Agent commands work without a background server. The authenticated localhost server starts on demand for the dashboard and can optionally run continuously for live file watching and shared embedding work.

One Vault. Multiple agents. Human-controlled memory.

Quick start · Obsidian Vault · Dashboard · How it works · Security · MCP contract · Documentation

Why Global Agent Memory?

Coding agents are useful inside a session, but important context is often lost between sessions or fragmented across individual clients. Global Agent Memory provides a durable layer for knowledge such as:

architectural decisions and project conventions;
verified workflows and operational runbooks;
recurring problems and their proven solutions;
project preferences, entities, and handoff summaries;
bounded context for a new task or agent session.

Agents propose memories as candidates. A human reviews them before they become durable, controls their visibility, and can later update, supersede, archive, or hard-delete them.

How it compares

Approach	Shared across agents	Human-reviewable	Project-aware	Owner-controlled access	Portable source of truth
`CLAUDE.md` / `AGENTS.md`	Limited	✓	✓	—	✓
Basic memory MCP	✓	Varies	Varies	Varies	Varies
Hosted agent memory	✓	Varies	✓	Provider-defined	—
Global Agent Memory	✓	✓	✓	✓	Markdown

Use project instruction files for compact rules that always belong in a prompt. Use Global Agent Memory when knowledge should be searchable, shared between clients, reviewed by a person, updated over time, or hidden behind explicit permission.

Highlights

Shared across agents — Claude Code, Codex, and other MCP clients use the same service and immutable memory IDs.
Project-aware by default — Git roots, remotes, aliases, and the project registry keep retrieval scoped to the active project.
Markdown is canonical — the Vault remains readable, portable, backup-friendly, and usable with Obsidian.
Human review workflow — agents create candidates; owners approve, edit, reject, or resolve conflicts in the dashboard.
Protected and sealed memory — sensitive knowledge can be excluded from ordinary retrieval and placed behind owner-controlled access.
Hybrid local search — SQLite FTS5 provides keyword retrieval; optional Ollama embeddings and sqlite-vec add semantic ranking.
Offline-friendly — keyword search and lifecycle operations continue when Ollama is unavailable.
Rebuildable generated state — SQLite, FTS, vectors, queues, and caches can be recreated from Markdown.
Frozen MCP V1 contract — tools, resources, prompts, envelopes, and compatibility rules are versioned in the repository.
No required background server: Claude Code, Codex, and CLI commands fall back to the same MCP application services in-process when the optional daemon is offline.
Local security boundary: when the dashboard or HTTP MCP is active, the server binds to 127.0.0.1 and requires a generated bearer token stored outside the Vault.

Built for real project vaults

The opt-in performance suite creates 10,000 synthetic memories and exercises the same indexing and retrieval paths used by both runtime modes. On the recorded macOS ARM64 baseline, a full rebuild takes 36.5 seconds, warm keyword search P95 is 56 ms, warm hybrid search P95 is 76 ms, and incremental stdio proxy overhead is 1.5 ms. Results vary by machine; the changed-note, search, and proxy budgets run as regression gates. See the methodology and complete baseline.

Three surfaces, one memory system

Global Agent Memory is more than an MCP server. Agents, owners, and knowledge workers use the same canonical memories through three purpose-built surfaces:

Surface	Designed for	What it provides
MCP	Claude Code, Codex, and other agents	Project-aware context, search, candidate creation, safe updates, lifecycle actions, and permission requests through a frozen V1 contract
Obsidian Vault	Reading, writing, linking, and long-term knowledge ownership	Portable Markdown and YAML, templates, native Bases views, project overview hubs, wikilinks, backlinks, graph navigation, and direct-edit synchronization
Local dashboard	Fast owner review and administration	Candidate approval and editing, conflict comparison, visibility classification, protected-access decisions, search, projects, activity, backups, and system health

The Vault is the durable source of truth. The dashboard is a complementary control plane, and the MCP interface is the safe automation layer used by agents. You can use Obsidian, the dashboard, or both without creating separate copies of your memory.

Dashboard at a glance

Real dashboard UI with synthetic Atlas project data. No private Vault content is shown.

Quick start

This is the shortest path to persistent memory for Claude Code, Codex, and other MCP clients. The guided installer creates the local service, Obsidian-compatible Vault, dashboard, MCP registrations, and agent skills together.

Requirements

macOS or Linux
Python 3.12 or newer
uv
Claude Code or Codex for the managed client integrations
Optional: Obsidian for browsing the Markdown Vault
Optional: Ollama for semantic retrieval

1. Install

uv tool install global-memory-mcp

To install the latest unreleased source, use uv tool install git+https://github.com/ozankasikci/global-agent-memory.git. For a local checkout, use uv tool install ..

2. Run guided setup

global-memory setup

Setup shows one plan and asks once before it changes anything. It initializes the local Vault, creates the protected token, detects Claude Code and Codex, installs their MCP integrations and skills, verifies healthy clients, and opens the dashboard. Opening the dashboard starts its authenticated localhost server on demand. The command is idempotent, so running it again repairs or updates managed components without replacing unrelated client configuration.

Use flags when you need a non-default setup:

# Non-interactive installation

global-memory setup --yes

Choose a different Vault on first setup

global-memory setup --vault "$HOME/Memory"

Install only one client, or no client yet

global-memory setup --clients claude-code global-memory setup --clients none

Optional: install an always-on native service for live watching and shared indexing

global-memory setup --service

Preview without changing files or services

global-memory setup --dry-run

3. Use the installed agent shortcuts

Setup installs five basic shortcuts for each detected client:

Shortcut	Purpose
`gam-context`	Load project-aware context for a task
`gam-search`	Find a decision, fact, error, convention, or solution
`gam-remember`	Propose explicitly supplied durable knowledge as a candidate
`gam-review`	Show the candidate queue without changing it
`gam-dashboard`	Open the authenticated dashboard

In Claude Code, invoke them directly, for example /gam-context fix the upload retry bug. In Codex, type /skills and choose one, or mention it directly, for example $gam-context fix the upload retry bug.

4. Open the dashboard again

global-memory dashboard

You can also ask a connected agent:

Open the Global Agent Memory dashboard.

The agent calls memory_dashboard_open and opens the same authenticated local dashboard.

Manual installation and repair

The individual commands remain available for advanced setups and troubleshooting:

global-memory init --vault "$HOME/Documents/Global Agent Memory"

global-memory daemon install-service --kind launchd # use systemd on Linux global-memory integrations install all global-memory integrations verify all global-memory doctor

Using it with an agent

After integration, you normally describe your intent instead of running memory commands manually.

Retrieve context before work

Before you start, load the relevant memory for this project and summarize the

conventions and recent decisions.

Propose a durable memory

Remember that production ARM64 binaries must be built locally and uploaded to the

server. Add it as a project convention with the deployment discussion as evidence.

The agent creates a candidate. Nothing becomes active until it is approved.

Update existing knowledge

Find the deployment memory and update it with the new health-check command. Do not

create a duplicate.

Open the review surface

Open the memory dashboard so I can review the candidates.

The shared integration skill teaches supported agents when to retrieve, propose, update, and avoid duplicating memory.

Obsidian Vault

The configured Obsidian Vault is the human-readable, durable source of truth—not an export of an opaque database. Every managed memory is a normal Markdown file with YAML properties, a stable memory ID, lifecycle metadata, and project-aware links.

Initialization adds an Obsidian workspace without replacing your existing files:

templates for decisions, facts, solutions, conventions, preferences, entities, references, session summaries, and project overviews;
native Bases views for the candidate review queue, active knowledge, recent updates, decisions by project, verified solutions, and lifecycle history;
project overview hubs that embed project memories and remain stable as notes move through candidate, active, rejected, superseded, or archived folders;
wikilinks and reciprocal supersession links for backlinks and graph navigation;
request-time synchronization, so ordinary content and descriptive-property edits made in Obsidian become searchable without a background service;
optional watcher synchron

Only the beginning is shown; read the rest in the repo

Global Agent Memory

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

Global Agent Memory

Why Global Agent Memory?

How it compares

Highlights

Built for real project vaults

Three surfaces, one memory system

Dashboard at a glance

Quick start

Requirements

1. Install

2. Run guided setup

Choose a different Vault on first setup

Install only one client, or no client yet

Optional: install an always-on native service for live watching and shared indexing

Preview without changing files or services

3. Use the installed agent shortcuts

4. Open the dashboard again

Manual installation and repair

Using it with an agent

Retrieve context before work

Propose a durable memory

Update existing knowledge

Open the review surface

Obsidian Vault