프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. 리뷰와 계정 기능은 다음 단계에서 열려요.
PopNx MCPAI를 쓰는 사람을 위한 MCP 서버 · 쉬운 말로 설명해요

ReasonGraph Cloud memory

제작자: bgokden버전 0.6.6i★ –i클라우드에서 실행
레지스트리 이름ai.primaxiom.memory/reasongraph

설치

개요

제작자가 쓴 설명(영어 원문)

Graph memory for AI agents: entities, cause-effect links, cross-session recall, time travel.

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

  • 연결 방식: 클라우드에서 실행
  • 전송 방식: Streamable HTTP
  • 카테고리: 검색 및 AI 기억
  • 입력해야 할 값: Authorization

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.

필요한 것

어떤 앱을 쓰세요?

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

이 주소는 요청 header에 키가 필요한데, 커넥터 추가 메뉴에서는 넣을 수 없어요. 대신 Claude Code, Cursor, VS Code를 쓰세요.

터미널에서 이 명령어를 실행하세요

claude mcp add --transport http reasongraph https://memory.primaxiom.ai/mcp --header 'Authorization: your-value'

실행하기 전에 빈 값을 채워 주세요.

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요

{
  "mcpServers": {
    "reasongraph": {
      "url": "https://memory.primaxiom.ai/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

{
  "servers": {
    "reasongraph": {
      "type": "http",
      "url": "https://memory.primaxiom.ai/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

이 주소는 요청 header에 키가 필요한데, 커넥터 추가 메뉴에서는 넣을 수 없어요. 대신 Claude Code, Cursor, VS Code를 쓰세요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

직접 입력할 값

  • Authorization 비밀 필수 HTTP header
    Bearer from https://memory.primaxiom.ai/console

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검

  • ! 주의

    제작자와 저장소 일치

    게시자(memory.primaxiom.ai)가 저장소 소유자(bgokden)가 아니에요. 다른 사람이 등록했을 수 있어요

  • … 아직 점검 안 함

    계속 관리되고 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • … 아직 점검 안 함

    라이선스 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • … 아직 점검 안 함

    엔드포인트 응답

    아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요

  • … 아직 점검 안 함

    OAuth로 로그인

    아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요

  • … 아직 점검 안 함

    도구 설명에 숨겨진 지시 없음

    아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요

검색 및 AI 기억 카테고리의 다른 서버와 비교i

  • 이 카테고리의 다른 서버 7275개 중 0%보다 스타가 많아요
  • 이 카테고리의 다른 서버 7275개 중 39%보다 최근에 레지스트리에 공개됐어요
  • 기본 점검 결과가 이 카테고리의 다른 서버 7275개 중 30%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

ReasonGraph Cloud memory, 안전한가요?

해당하는 기본 점검 1개 중 0개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

입력해야 할 값: Authorization

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.6.6)은 2개월 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Context7, Codebase Memory, Exa

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Context7

제작자: upstash

Up-to-date docs for AI agents

컴퓨터 또는 클라우드★ 64,224MIT어제 업데이트
설치

Codebase Memory

제작자: DeusData

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

내 컴퓨터에서 실행★ 48,148MIT21일 전 업데이트
설치

Exa

제작자: exa-labs

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

클라우드에서 실행★ 5,213MIT지난달 업데이트
설치

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.

ReasonGraph

A graph-based memory for AI agents: it ingests facts, auto-extracts entities and cause->effect relations, and discovers connections across independent documents *and* across agent sessions -- with conflict resolution, time-travel, causal tracing, and counterfactuals.

Why ReasonGraph?

Standard RAG retrieves documents similar to your query. ReasonGraph is a persistent, updatable memory that discovers connections *between* facts that were written independently.

When you feed text into add_texts(), ReasonGraph automatically extracts entities (via GLiNER) and cause-effect relations (via a dedicated causal model) that become nodes and typed edges in a graph. Facts that share entities or causal chains get connected -- even if they never reference each other. Multi-hop traversal then walks these connections to build reasoning chains that span multiple sources.

On top of retrieval it works as agent memory: scopes/sessions (agents discover into each other's memory through shared entities), contradiction resolution (a new fact soft-supersedes what it contradicts), time-travel (query(as_of=...)), causal tracing (trace_effects / root_causes / causal_chain), counterfactuals (what_if), and a shippable MemoryService over HTTP and MCP.

Zero config, strong defaults. ReasonGraph() picks the best available entity extractor, causal model, embedder, and reranker automatically -- the eval numbers below come from these defaults. For the SOTA causal model (~0.70 F1) use pip install reasongraph[causal] and the graph uses it automatically. The configuration sections are optional depth, not required reading.

Use it in 60 seconds

Claude Code / Cursor / any MCP client, hosted (EU, no LLM in the loop):

claude mcp add --transport http memory https://memory.primaxiom.ai/mcp \

--header "Authorization: Bearer rgm_YOUR_KEY"

Local MCP server (stdio, everything on your machine, SQLite):

pip install "reasongraph[service,gliner,fastembed,sqlite]"

claude mcp add memory -- reasongraph-mcp

Python, in-process:

pip install "reasongraph[all]"
from reasongraph import ReasonGraph

graph = ReasonGraph() graph.initialize_sync() graph.add_texts_sync(["TSMC is building a chip fab in Phoenix, Arizona.", "Arizona ordered water cuts for industrial users in Maricopa County."]) print(graph.discover_sync("water and chips")) # a path: water cuts -> Arizona -> TSMC fab

Any language, over HTTP (self-hosted or hosted):

curl -X POST https://memory.primaxiom.ai/sessions/notes/memory \

-H "Authorization: Bearer rgm_YOUR_KEY" -H "Content-Type: application/json" \ -d '{"text": "Apple sources M-series chips from TSMC in Arizona."}'

Ready-to-copy agents (Groq/OpenAI-compatible research agent, two agents sharing one memory, Claude Code with persistent memory, LangGraph) live in examples/agents/.

Hosted: ReasonGraph Cloud

memory.primaxiom.ai runs this library as a service: sign in, get a free key (10k requests a month), remote MCP endpoint, browser console and playground. Extraction runs with small models on servers PrimAxiom operates (currently in the EU); facts are only sent to an LLM provider if you ask for a synthesized answer. Early access.

JavaScript and TypeScript

Agents that are not written in Python talk to the hosted service through a dependency-free client (clients/typescript). It uses the platform fetch, so it runs on Node 18+, Bun, Deno, Cloudflare Workers and the browser. npm install reasongraph.

import { Memory, memoryTools } from "reasongraph";

const mem = new Memory({ apiKey: process.env.REASONGRAPH_API_KEY }); await mem.remember("scout", "TSMC is building a chip fab in Phoenix, Arizona."); const facts = await mem.discover("What could disrupt the Phoenix fab?");

memoryTools(mem) returns OpenAI-style tool definitions with their executors attached, for agents that call functions directly without a framework: remember, recall and why.

Installation

pip install reasongraph[all]        # everything included

Or install only what you need:

pip install reasongraph             # core: in-memory backend, NER extraction, embeddings

pip install reasongraph[gliner] # + GLiNER entity extraction + hybrid causal (default, recommended) pip install reasongraph[causal] # + SOTA span-pointer causal model (~0.70 F1) + hybrid fallback pip install reasongraph[gliner2] # + GLiNER2 alternative (single model does entities + causal) pip install reasongraph[sqlite] # + SQLite backend with sqlite-vec pip install reasongraph[postgres] # + PostgreSQL + pgvector backend pip install reasongraph[service] # + HTTP + MCP memory service pip install reasongraph[fastembed] # + pure-ONNX embedder / reranker (faster cold start)

Cross-Source Discovery

Two reports about different topics. Source A covers TSMC's semiconductor plant. Source B covers Arizona's water crisis. Neither mentions the other's subject.

import asyncio

from reasongraph import ReasonGraph

source_a = [ # Tech industry report "TSMC announced plans to build a $40 billion semiconductor fabrication plant in Phoenix, Arizona.", "The Phoenix fab requires 10 million gallons of purified water daily to cool wafers during the chip etching process.", "TSMC signed a long-term supply agreement with Apple to manufacture next-generation M-series processors at the Arizona facility.", "Construction delays at the Phoenix site pushed first production to late 2025, raising concerns among TSMC's major customers.", ]

source_b = [ # Environmental report -- never mentions TSMC, semiconductors, or chips "Arizona declared a water emergency after Lake Mead dropped to its lowest level since the 1930s, threatening water supply for millions.", "The Arizona Department of Water Resources ordered mandatory water cuts for all industrial users in Maricopa County, where Phoenix is located.", "Intel paused expansion of its Chandler, Arizona chip plant citing water availability concerns and rising operational costs.", "Apple warned investors that component shortages from its Asian and North American suppliers could impact iPhone production timelines through 2026.", ]

async def main(): async with ReasonGraph() as graph: await graph.add_texts(source_a) await graph.add_texts(source_b) results = await graph.query("How does the Arizona water crisis affect semiconductor manufacturing?") for i, text in enumerate(results, 1): source = "A" if text in source_a else "B" print(f"{i}. [Source {source}] {text}")

asyncio.run(main())

  1. [Source B] Intel paused expansion of its Chandler, Arizona chip plant citing water availability concerns and rising operational costs.
  2. [Source B] The Arizona Department of Water Resources ordered mandatory water cuts for all industrial users in Maricopa County, where Phoenix is located.
  3. [Source A] The Phoenix fab requires 10 million gallons of purified water daily to cool wafers during the chip etching process.
  4. [Source B] Arizona declared a water emergency after Lake Mead dropped to its lowest level since the 1930s.
  5. [Source A] TSMC announced plans to build a $40 billion semiconductor fabrication plant in Phoenix, Arizona.
  6. [Source A] TSMC signed a long-term supply agreement with Apple to manufacture M-series processors at the Arizona facility.

Results come from both sources. No single document contains this chain. Here is what happens under the hood:

ReasonGraph extracts entities and causal relations from each text (requires an entity+causal extractor, e.g. pip install reasongraph[gliner] or [all]):

Text (abbreviated)EntitiesCausal relations
TSMC to build fab in Phoenix, Arizona...TSMC, Phoenix, Arizona--
Phoenix fab requires 10M gallons water...Phoenix--
TSMC supply agreement with Apple...TSMC, Apple, Arizona--
Construction delays at Phoenix site...TSMC, PhoenixConstruction delays -> first production
Arizona water emergency, Lake Mead...Arizona, Lake MeadLake Mead dropped -> water emergency
Mandatory water cuts in Maricopa County...Arizona Dept. of Water Resources, Phoenix, Maricopa County--
Intel paused Arizona chip plant...Intel, Chandler, Arizona--
Apple warned of component shortages...Applecomponent shortages -> iPhone production timelines

Three entities appear in both sources, creating bridge nodes:

Bridge entitySource A connectionsSource B connections
ArizonaTSMC fab, TSMC-Apple dealwater emergency, Intel pause, water cuts
PhoenixTSMC fab, water usage, delayswater cuts for industrial users
AppleTSMC supply agreementcomponent shortage warning

The query traversal path:

Water crisis query -> finds water-related texts from both sources via embeddings -> follows Arizona and Phoenix entity edges to discover TSMC's water-intensive fab -> follows Apple entity edge from TSMC supply agreement to Apple's component shortage warning. The causal relation Lake Mead dropped -> water emergency connects the environmental trigger to the industrial impact.

Full demo: uv run python examples/cross_source_discovery.py

Quick Start

Using a built-in dataset
from reasongraph import ReasonGraph

graph = ReasonGraph() graph.initialize_sync() graph.load_dataset_sync("financial")

results = graph.query_sync("What caused the 2008 financial crisis?") for i, text in enumerate(results, 1): print(f"{i}. {text}")

graph.close_sync()

Output -- a connected reasoning chain, not just keyword matches:

1. Lehman Brothers filed for bankruptcy in September 2008 after massive MBS losses.
  1. Loose lending standards fueled a housing price bubble across the United States.
  2. Lehman's collapse triggered a global credit freeze as interbank lending stopped.
  3. Mortgage-backed securities built on subprime loans collapsed when defaults surged.
  4. The U.S. government enacted TARP, a $700 billion bailout to stabilize the financial system.
  5. Banks issued subprime mortgages to borrowers with poor credit histories.
Async API
import asyncio

from reasongraph import ReasonGraph

async def main(): async with ReasonGraph() as graph: await graph.load_dataset("financial") results = await graph.query("What caused the 2008 crisis?") for text in results: print(text)

asyncio.run(main())

Features

  • Cross-source discovery -- connect facts across independent documents through shared entities and causal relations
  • Automatic extraction -- entities (GLiNER gliner_small-v2.5 by default) and cause->effect relations (a dedicated span-pointer / hybrid causal model) are extracted on add, both on by default; falls back to GLiNER2 then BERT NER when gliner is not installed
  • Agent memory -- scopes/sessions with cross-session discovery, contradiction resolution (soft-supersede), time-travel (as_of), semantic dedup, and auto-forget
  • Causal reasoning -- trace downstream effects, root causes, and directed causal paths; ask counterfactual what_if
  • Hybrid search -- combine embedding similarity, keyword (trigram) matching, or both
  • *

앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요

PopNx에게 묻기