Lore MCP
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Lore MCPload the project briefing"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@sharedlore/mcp
A thin MCP server over the lore-api GraphQL endpoint. It gives an AI agent team-shared "lore": area context docs, append-only session captures, and structured docs (ADRs, logs, TODOs, plans).
The server is stateless - every tool call hits the lore-api GraphQL endpoint over HTTPS.
Tools
Tool | What it does |
| List the projects in the token's org (the token fixes the org). Returns the org name + each project's |
| Create a project in the token's org ( |
| Team |
| Append a session capture to a node (by |
| Create/update an ADR node by path (kind |
| Create/update a log node by path (kind |
| Create/update a TODO node by path (kind |
| Create/update a plan node by path (kind |
| List the folder/doc tree (optionally scoped by |
| Fetch the derived area context document at a |
| Search nodes by path substring (optional |
Every write/read tool accepts an optional project slug. Resolution precedence when a tool
omits project: the .lorerc file at the repo root (a { "project": "<slug>" } JSON file,
found by walking up parent directories from the server's cwd, like git finds .git) → the
LORE_PROJECT env var. Run lore link <slug> (from @sharedlore/cli) to write .lorerc.
Related MCP server: knitbrain
Configuration (env)
Var | Default | Purpose |
|
| GraphQL endpoint. |
| - | The |
| - | Fallback project slug used when a tool omits |
Getting a token
In the SharedLore dashboard, go to API tokens and create a new token. Copy the
lore_sk_... value (shown once) into LORE_API_TOKEN. A token's role (admin / member /
viewer) determines what it can do - a viewer token cannot capture or upsert and tools will
return a clear "not authorized" message.
Connect (.mcp.json)
Install straight from the public GitHub repo - npx clones and builds it on first run (a
prepare script runs tsc), so nothing needs to be published:
{
"mcpServers": {
"sharedlore": {
"command": "npx",
"args": ["-y", "github:sharedlore-ai/lore-mcp"],
"env": {
"LORE_API_URL": "https://lore.example.com/graphql",
"LORE_API_TOKEN": "lore_sk_xxx"
}
}
}
}Variants (same env in all cases):
npm (once published):
"args": ["-y", "@sharedlore/mcp"].Local checkout (no npx):
"command": "node", "args": ["/abs/path/lore-mcp/dist/index.js"]- runnpm run buildfirst.Local lore-api: set
LORE_API_URLtohttp://localhost:3030/graphql.
Develop
npm install
npm run build # tsc -> dist/
npm run dev # tsc --watchRequires Node 20+ (uses the global fetch).
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sharedlore-ai/lore-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server