Context7
Up-to-date docs for AI agents
제작자가 쓴 설명(영어 원문)
Persistent coding memory for AI assistants. MCP stdio, hybrid search, graph, context.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
RATARY_API_KEY, RATARY_BASE_URL비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"ratary": {
"command": "npx",
"args": [
"-y",
"@ratary/mcp-server"
],
"env": {
"RATARY_API_KEY": "your-value",
"RATARY_BASE_URL": "your-value"
}
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add ratary --env RATARY_API_KEY=your-value --env RATARY_BASE_URL=your-value -- npx -y @ratary/mcp-server실행하기 전에 빈 값을 채워 주세요.
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"ratary": {
"command": "npx",
"args": [
"-y",
"@ratary/mcp-server"
],
"env": {
"RATARY_API_KEY": "your-value",
"RATARY_BASE_URL": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"ratary": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ratary/mcp-server"
],
"env": {
"RATARY_API_KEY": "your-value",
"RATARY_BASE_URL": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
RATARY_BASE_URL env이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검
레지스트리 이름이 GitHub 계정 ontorata 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: RATARY_API_KEY
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.1.1)은 4개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.
같은 카테고리에는: Context7, Codebase Memory, Exa
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Ratary
Build AI that remembers.
Ratary is the open-source AI Brain Platform — persistent memory,
structured knowledge, and intelligent retrieval for every model and agent you run.
Get started → · Star on GitHub · Website · Docs
Ratary is where AI remembers. · Built by Ontorata
Quick start · Ecosystem · Architecture · How it works · Capabilities · Docs
*Why does AI forget between sessions?*
Every AI session starts from zero.
Your model forgets yesterday's architecture decisions. Your agent drops customer context between runs. Your coding assistant can't recall why you chose Postgres over DynamoDB. Teams paste the same background into Cursor, Claude, ChatGPT, and custom bots — and knowledge still drifts.
Vector databases store chunks. RAG pipelines retrieve documents. Agent frameworks orchestrate tools.
None of them give AI a durable brain.
*Why build a brain layer now?*
AI models are getting cheaper. Context windows are getting larger. Agents are getting capable.
But AI still forgets.
The bottleneck is no longer reasoning. It's memory — durable, structured, retrievable, and owned by you.
Every serious application eventually needed a database. Every serious AI system will need a brain layer: persistent intelligence that sits between your models and your storage — independent of any single vendor, IDE, or agent framework.
AI should remember.
Developers should own that memory.
Ratary exists to be that layer. Applications bring models. Ratary brings the brain.
*What is Ratary?*
Ratary is an AI Brain Platform — infrastructure that gives AI:
It sits between AI clients and storage. One brain, many surfaces — Cursor, Claude Code, custom agents, enterprise APIs, and remote MCP hosts.
The runnable deployment is [Ratary Server](#quick-start) — this repository. Ratary is the product; Ratary Server is what you clone and run.
Bring your model. Ratary brings the memory.
*How do I run Ratary Server locally?*
Ratary is the product. Ratary Server is the open-source deployment you run — ontorata/ratary (this repository). @ratary/sdk, @ratary/cli, and Ratary MCP connect to it; sibling Ontorata products use the same source of truth.
Prerequisites: Node.js 24 · SQL metadata store (pick one — Postgres is the template default)
git clone https://github.com/ontorata/ratary.git
cd ratary && npm install cp .env.example .env # Set AUTH_SECRET + DATABASE_URL — see .env.example QUICK START npm run db:apply-postgres-schema npm run setup # wire Ratary MCP for Cursor, Claude Code, … npm run dev
Or use Docker: docker compose --profile postgres up --build — see docs/DOCKER.md.
git clone https://github.com/ontorata/ratary.git
cd ratary && npm install cp .env.example .env # Set AUTH_SECRET + SQL_PROVIDER=d1 + CLOUDFLARE_* / D1_* npm run db:migrate npm run setup npm run dev
Details: [docs/GUIDE.md](docs/GUIDE.md#1-setup) · [docs/CONFIGURATION.md](docs/CONFIGURATION.md)
→ API http://localhost:9876 · Swagger /docs
First REST call: bootstrap once to get an API key (aic_...) — see GUIDE — First REST API key.
# Save your first memory
curl -X POST http://localhost:9876/api/v1/memory \ -H "Authorization: Bearer aic_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{"title":"Hello brain","project":"demo","content":"Ratary remembers this."}'
Full guide: [docs/GUIDE.md](docs/GUIDE.md) · SDK & MCP examples in docs/examples/
@ratary)Client libraries ship on npm under the `@ratary` scope — product name, published by Ontorata. No server clone required for SDK, CLI, or hosted MCP.
npm install @ratary/sdk@1.1.0
npx @ratary/mcp-server@1.1.3 # remote REST → stdio MCP npm install -g @ratary/cli@1.1.0 # operator CLI
| Package | Version | Install | Role |
|---|---|---|---|
@ratary/sdk | 1.1.0 | npm install @ratary/sdk | Typed REST client + client.admin.* |
@ratary/cli | 1.1.0 | npm install -g @ratary/cli | Operator commands (admin, connectors) |
@ratary/mcp-server | 1.1.3 | npx @ratary/mcp-server | IDE MCP → hosted API |
Set RATARY_BASE_URL and RATARY_API_KEY (aic_...). Details: [packages/README.md](packages/README.md) · remote MCP install.
*Which repository owns what?*
The Visual architecture diagram shows logical layers inside Ratary Server. This diagram shows repository and product relationships — what ships in this repo, what connects to it, and what lives in sibling Ontorata repositories. Both views describe the same platform from different angles.
Throughout this README, Ratary MCP means the official memory MCP implementation (stdio in this repo · npm @ratary/mcp-server for hosted REST). It is not the same as Ontorata MCP (ecosystem gateway — separate repo).
┌─────────────────────────────────────────────────────────────┐
│ Ratary Cloud (opt-in) │ │ optional hosted deployment · not this repo │ └──────────────────────────────┬──────────────────────────────┘ │ ┌──────────────────────────────▼──────────────────────────────┐ │ Ratary Server ← ontorata/ratary (this repo) │ └──────────────────────────────┬──────────────────────────────┘ │ │ │ ▼ ▼ ▼ @ratary/sdk @ratary/cli @ratary/mcp-server (SDK) (CLI) (Ratary MCP · npm) │ │ │ └──────────────┴──────────────┘ │ ┌─────────────────────┴─────────────────────┐ ▼ ▼ ▼ Ontorata MCP Ontorata Studio Ontory Runtime ontorata/ontorata-mcp ontorata/Ontorata-Studio ontorata/ontory-runtime ecosystem product ecosystem product (ADR-2119; was ontorata/ontory)
Infrastructure (ships from ontorata/ratary — server plus client packages):
| Component | Repository | Role |
|---|---|---|
| Ratary Server | ontorata/ratary | Memory engine — REST, persistence, Ratary MCP stdio. You run this. |
| Ratary SDK | npm @ratary/sdk · packages/sdk | Typed REST client for Ratary Server. |
| Ratary CLI | npm @ratary/cli · packages/cli | Operator commands; delegates to Ratary SDK. |
| Ratary MCP | npm @ratary/mcp-server · stdio in repo | Memory MCP — full stdio in clone · npm proxy for hosted REST. |
Ecosystem products (separate repositories — connect to Ratary Server; not bundled here):
| Product | Repository | Role |
|---|---|---|
| Ontorata MCP | ontorata/ontorata-mcp | Ecosystem MCP gateway — Ratary MCP plus additional Ontorata tools. |
| Ontorata Studio | ontorata/Ontorata-Studio | Operator UI — uses @ratary/sdk only. |
| Ontory | ontorata/ontory-runtime | Ontory Runtime — AI orchestration (ADR-2119). Legacy URL ontorata/ontory redirects. |
Ratary Server does not depend on ecosystem product repositories.
*Which MCP should I install?*
| Ratary MCP | Ontorata MCP | |
|---|---|---|
| Layer | Ratary infrastructure | Ontorata ecosystem product |
| What it is | Official memory protocol for Ratary Server | Ecosystem gateway for Ontorata products |
| Scope | Memory — CRUD, search, context, graph | Ratary memory plus additional Ontorata tools |
| Repository | ontorata/ratary · npm @ratary/mcp-server | ontorata/ontorata-mcp |
| Typical `mcp.json` key | ratary | ontorata |
Use Ratary MCP for direct memory access. Use Ontorata MCP for one MCP entry point across the Ontorata stack. Both use Ratary Server as source of truth.
*How is Ratary different from alternatives?*
| Vector DB | Memory API | RAG | Agent framework | Ratary | |
|---|---|---|---|---|---|
| Primary job | Similarity search | Key-value recall | Document Q&A | Tool orchestration | Durable AI memory |
| Structured knowledge & graph | ❌ | ⚠️ | ❌ | ⚠️ | ✅ |
| MCP-native IDE integration | ❌ | ⚠️ | ❌ | ⚠️ | ✅ |
| Token-efficient context assembly | ❌ | ⚠️ | ❌ | ⚠️ | ✅ |
| Self-host & data sovereignty | ✅ | ⚠️ | ⚠️ | ⚠️ | ✅ |
| Clear agent boundary | N/A | ⚠️ | N/A | ❌ bundled | ✅ substrate only |
Ratary complements your stack — it does not replace pgvector, LangGraph, or your agent of choice. See the [Capability matrix](#capability-matrix) for a feature-level comparison.
Why not just pgvector, Mem0, Letta, LangGraph, or RAG?
| If you only use… | You get… | What you miss |
|---|---|---|
| pgvector | Embedding similarity | Structured memory, graph, MCP, context packing |
| Mem0 | Fast hosted memory API | Full self-host, hybrid retrie
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요