Lore MCP
A stateless MCP server that gives AI agents team-shared lore including area context documents, session captures, and structured docs (ADRs, logs, TODOs, plans) via the lore-api GraphQL endpoint.
README
@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 |
|---|---|
lore_projects |
List the projects in the token's org (the token fixes the org). Returns the org name + each project's slug/name. Powers /lore:init. |
lore_create_project |
Create a project in the token's org (name, optional slug — derived from the name if omitted). Returns the created slug/name. |
lore_start |
Team /start: loads the project briefing (area context docs + recent captures). Optional directive. |
lore_capture |
Append a session capture to a node (by path or id). Append-only; triggers server-side context synthesis. |
lore_adr |
Create/update an ADR node by path (kind adr). |
lore_log |
Create/update a log node by path (kind log). |
lore_todo |
Create/update a TODO node by path (kind todo). |
lore_plan |
Create/update a plan node by path (kind plan). |
lore_tree |
List the folder/doc tree (optionally scoped by parentId or kind). |
lore_context |
Fetch the derived area context document at a path. |
lore_search |
Search nodes by path substring (optional kind). |
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.
Configuration (env)
| Var | Default | Purpose |
|---|---|---|
LORE_API_URL |
http://localhost:3030/graphql |
GraphQL endpoint. |
LORE_API_TOKEN |
— | The lore_sk_... API token. Sent as Authorization: Bearer <token>. The token scopes the org server-side, so no org header is needed. |
LORE_PROJECT |
— | Fallback project slug used when a tool omits project and no .lorerc is found. Prefer .lorerc (per-repo) over this. |
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 --watch
Requires Node 20+ (uses the global fetch).
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.