graphiti-folder
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GRAPHITI_FOLDER_API_KEY | Yes | Your OpenRouter API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_graphiti_statusA | 현재 원본 변경 계획과 manifest·Graphiti 그래프 개수를 반환한다. |
| search_graphitiA | Graphiti 공식 하이브리드 검색으로 시간 Fact·Entity·Episode와 출처를 찾는다. |
| get_episode_sourcesA | Episode UUID를 원본 Markdown 경로·revision·원문 미리보기로 되돌린다. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: status retrieval, search, and episode source resolution. No functional overlap.
All tools follow a consistent verb_noun pattern (get_*, search_*) with domain-specific suffixes, making names predictable and clear.
Three tools is a focused, well-scoped set for a Graphiti folder server, covering essential read/search operations without redundancy.
Core operations for querying status, searching, and retrieving episode sources are present. Minor gaps like graph traversal or metadata listing are absent but not critical for the apparent purpose.