# Lore — Connect Your Team Around Shared Context

Lore is a platform for product development teams where
documentation, tasks, and communication live in one place —
accessible to both humans and AI agents through MCP.

Multi-project workspace with team and personal projects.
Every user gets a personal project for private tasks
and notes. Invite members, assign tasks, send messages,
share context documents, and get activity notifications —
all through MCP tools.

## Why Lore

Every team member — human or AI — reads from the same
project record: docs, tasks, and messages in one place.

**Standardized Documentation**
Architecture decisions, API specs, database schemas, coding
rules — all follow consistent templates with metadata tracking.

**Task Management**
A shared backlog where tasks are created, assigned, discussed,
and completed. Agents can pick up tasks, update progress, and
coordinate with teammates — all through the same workflow.

**Team Communication**
Send messages to teammates by email, check your inbox, discuss
tasks in threads, or start conversations on any topic.
Agents and humans communicate through the same channels.

## Available Tools (after connecting)

**Identity**
- lore_whoami — Check your identity, projects, and roles
- lore_set_profile — Set or update your GitHub username and timezone
- lore_notifications — View how Lore emails you: digest schedule and task emails
- lore_set_notifications — Change the digest schedule and task emails
- lore_logout — End your session

**Projects**
- lore_project — List your projects, get one project's details and members, summarize changes since your last check, or list invitations waiting for your answer (action: list | info | summary | invitations)
- lore_create_project — Create a new project (you become owner)
- lore_delete_project — Delete a project (owner only); it waits 7 days in the bin, where lore_cancel_deletion restores it
- lore_invite_member — Invite someone to a project by email; they join when they accept
- lore_invitation — Accept or decline an invitation to a project
- lore_remove_member — Remove a member, leave a project, or cancel a pending invitation

**Tasks**
- lore_task — List tasks, get full detail for one, or list the project's tags (action: list | detail | tags)
- lore_create_task — Create one or more tasks
- lore_update_task — Update status, assignee, priority, or followers
- lore_delete_task — Delete one or more tasks

**Messaging**
- lore_message — Send a message, edit an undelivered one, or mark messages read (action: send | update | mark_read)
- lore_inbox — View your inbox or read a full thread (action: list | thread)
- lore_delete_message — Delete an undelivered, unreplied message

**Context Storage**
- lore_context — Read a document, list a folder, or show the full directory tree (action: read | list | tree)
- lore_context_write — Create or update a context document
- lore_context_delete — Delete a context document

**Activity**
- lore_activity — Your watched-event feed or the full project event log (action: feed | log)

**Feedback & Support**
- lore_feedback — Send bug reports, feature requests, help requests, or general feedback to the Lore team without leaving your chat. The team may reply at your account email.

## How to Connect

Add Lore as an MCP server in your IDE or AI client.
Authentication uses Google OAuth — the user will see a
Google sign-in prompt and just needs to confirm their account.

Coding agents (Cursor, Claude Code, Codex and the others
with config files below) can write the config or run the add
command, but the user may have to approve that step, and in
Claude Code's auto mode it is refused: then give the user the
command to run. The sign-in is always the user's. Chat
apps (Claude, ChatGPT, Gemini, Le Chat) take the URL in
their own settings, which only the user can open — give the
user the steps for their app.

### Cursor
Create `.cursor/mcp.json` in the project root:
```json
{
  "mcpServers": {
    "lore": {
      "url": "https://mcp.onelore.ai"
    }
  }
}
```
If the file already exists, add the "lore" entry inside
the existing "mcpServers" object.

To make Lore available in all Cursor projects, add the
same config to `~/.cursor/mcp.json` instead.

After creating the file, tell the user to open Customize
in Cursor's sidebar, find Lore among the MCP servers and
finish the Google sign-in when Cursor asks.

### VS Code (GitHub Copilot)
Add to `~/.copilot/mcp-config.json` (or
`$COPILOT_HOME/mcp-config.json`), which covers every project:
```json
{
  "mcpServers": {
    "lore": {
      "type": "http",
      "url": "https://mcp.onelore.ai"
    }
  }
}
```
If the file already exists, add the "lore" entry inside
the existing "mcpServers" object.

Without a file, the user runs MCP: Add Server from the
Command Palette, chooses HTTP, pastes the URL, names it lore
and picks Global, then Copilot Global. An older
`.vscode/mcp.json` with a "servers" object still works, but
VS Code marks it deprecated. Tell the user to allow the
sign-in prompt and finish the Google sign-in.

### Devin Desktop (formerly Windsurf)
Run:
  devin mcp add lore https://mcp.onelore.ai
  devin mcp login lore
Or add the server to `~/.config/devin/mcp_config.json`
under "mcpServers" with "url" and "transport": "http"
(versions before v3000.3 read `~/.config/devin/config.json`).
If the server shows Needs authentication on the Customize
page, tell the user to click Authenticate.

### Cline
Open Cline's MCP Servers panel, Remote Servers tab. Use:
  Name: lore
  URL: https://mcp.onelore.ai
  Transport: Streamable HTTP (the default)
Click Add Server; when it reports authentication required,
click Authenticate to finish the Google sign-in.
If editing config JSON directly, set "type":
"streamableHttp" explicitly — omitting it falls back to
SSE, which this server does not support.

### Continue.dev
The extension cannot complete OAuth over streamable-http;
connect through the mcp-remote bridge (needs Node.js).
Add to `~/.continue/config.yaml`:
```yaml
mcpServers:
  - name: lore
    command: npx
    args: ["-y", "mcp-remote", "https://mcp.onelore.ai"]
```

### Zed
Add to `~/.config/zed/settings.json`:
```json
{
  "context_servers": {
    "lore": {
      "url": "https://mcp.onelore.ai"
    }
  }
}
```
Zed picks it up instantly. Tell the user to open
Settings > AI > MCP Servers and click Authenticate next
to lore, then finish the Google sign-in.

### JetBrains (IntelliJ, WebStorm, PyCharm, etc.)

AI Assistant does not support MCP OAuth yet — connect
through the mcp-remote bridge (needs Node.js).
Go to Settings > Tools > AI Assistant > Model Context
Protocol (MCP). Click Add and paste into the JSON
configuration field:
```json
{
  "mcpServers": {
    "lore": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.onelore.ai"]
    }
  }
}
```
The first connection opens Google sign-in in the browser.

---

### Claude Code (CLI)

Run: claude mcp add --transport http --scope user lore https://mcp.onelore.ai
--scope user makes Lore available in every project; without
it, Lore is added to the current project only.
If the add is refused (auto mode treats it as self-
modification), give the user that command to run in a
terminal. Sign-in: the user runs claude mcp login lore in a
terminal, or /mcp inside Claude Code, and signs in with
Google. No restart is needed (verified 2026-11-02).

---

### Claude (web, desktop and mobile)

The user adds Lore in Claude's settings; an agent cannot.
Go to Customize > Connectors, click + Add, then Add custom
connector. Name: Lore. URL: https://mcp.onelore.ai
Click Continue, keep the detected settings, choose Sign in
now and finish the Google sign-in, then click Add. In each
chat, click + and switch Lore on under Connectors. The Free
plan allows one custom connector. On Team and Enterprise
plans an Owner adds Lore under Organization settings >
Connectors, and members click Connect next to it.

---

### Gemini CLI

Create `~/.gemini/extensions/lore/gemini-extension.json`:
```json
{
  "name": "lore",
  "version": "1.0.0",
  "mcpServers": {
    "lore": {
      "httpUrl": "https://mcp.onelore.ai"
    }
  }
}
```

---

### Gemini Code Assist (VS Code)

Add to `~/.gemini/settings.json`:
```json
{
  "mcpServers": {
    "lore": {
      "httpUrl": "https://mcp.onelore.ai"
    }
  }
}
```

---

### Gemini app (gemini.google.com)

US-only for now: Gemini offers custom apps only to personal
Google accounts located in the US (18+, English, Keep
Activity on; Google lists no plan requirement). Elsewhere,
or on a work or school account, Gemini may still accept the
URL and the Google sign-in but will not use Lore in a chat
(seen from Sweden, Nov 2026). Say so before the user tries,
and offer Gemini CLI or Gemini Code Assist (no such limit),
or Claude, ChatGPT or Le Chat, instead.

The user adds Lore in Gemini's settings; an agent cannot.
On gemini.google.com (web only to add; it then works in the
mobile app too), click Settings > Connected Apps (or
Personal Intelligence > Connected Apps). Under Custom apps,
click Add a custom app, enter https://mcp.onelore.ai and click
Next, then finish the Google sign-in. In a chat, type @ and
pick Lore.

---

### OpenAI Codex CLI

Run:
  codex mcp add lore --url https://mcp.onelore.ai
  codex mcp login lore

---

### Mistral Le Chat

Open Le Chat and go to the Connectors page from the sidebar.
Click + Add Connector and switch to the Custom MCP Connector tab.
Connector name: lore (no spaces).
Server URL: https://mcp.onelore.ai
Click Connect. Mistral auto-detects OAuth and walks the user
through Google sign-in. Available on the Free plan.

---

### ChatGPT

The user adds Lore in ChatGPT's Settings; ChatGPT cannot add
an MCP server from inside a chat, so do not offer to.
In ChatGPT, open Settings > Plugins > Browse catalog, click
Add and choose Add custom MCP server (or go straight to
chatgpt.com/plugins). Name: Lore. Server URL: https://mcp.onelore.ai
Authentication: OAuth. Accept the risk notice, click Create
as a plugin, then install the plugin. In a chat, type @ and
pick Lore; the first Lore call opens the Google sign-in.
Works on every ChatGPT plan, including Free (tested on a Free
account, 2026-11-02). If the user does not see Add custom MCP
server, it is not enabled for their account or workspace yet.
Developer Mode and "Create app" are no longer part of the
path; if older notes say so, they are out of date.

---

## After Setup

1. Reload or restart your IDE/app if prompted.
2. Sign in with your Google account when OAuth appears.
3. In chat apps, switch Lore on for the chat: Claude, click +
   and turn Lore on under Connectors; ChatGPT and Gemini, type
   @ and pick Lore. Coding agents have it on already.
4. Call lore_whoami to verify the connection. The first call
   on a new account also returns a welcome for the user with
   three things to try: "Remember in Lore that I prefer short
   answers", "Save a summary of this chat to Lore", and, in
   another chat or AI, "What did I save in Lore?"

## Skill File (Optional)

Platforms that support skill files can auto-activate Lore
in future sessions. Create at the path for your platform:
- Claude Code: `~/.claude/skills/lore/SKILL.md`
- Gemini: `~/.gemini/skills/lore/SKILL.md`
- Codex: `~/.agents/skills/lore/SKILL.md`

Content:
```
---
name: lore
description: >
  Connect to Lore, a platform where products are developed
  around a shared, standardized context. Use
  when the user mentions Lore, wants to manage projects,
  check messages, or coordinate with team members.
---

# Lore

Lore is a platform where products are developed around a
shared, standardized context.

## MCP Server
URL: https://mcp.onelore.ai
Auth: Google OAuth (auto by MCP client)

## Available Tools
- lore_whoami — Returns your identity and projects; useful as a first call
- lore_set_profile — Set your GitHub username and timezone
- lore_notifications — View digest schedule and task emails; lore_set_notifications changes them
- lore_project — Your projects and invitations (action: list | info | summary | invitations)
- lore_create_project — Create a new project
- lore_delete_project — Delete a project (owner only); it waits 7 days in the bin, where lore_cancel_deletion restores it
- lore_invite_member — Invite someone to a project (they join when they accept)
- lore_invitation — Accept or decline a project invitation
- lore_remove_member — Remove a member, leave a project, or cancel an invitation
- lore_task — Read tasks (action: list | detail | tags)
- lore_create_task — Create one or more tasks
- lore_update_task — Update task status, assignee, or priority
- lore_delete_task — Delete one or more tasks
- lore_message — Send/edit/mark-read messages (action: send | update | mark_read)
- lore_inbox — Read messages (action: list | thread)
- lore_delete_message — Delete an undelivered, unreplied message you sent
- lore_context — Read context storage (action: read | list | tree)
- lore_context_write — Create or update a context document
- lore_context_delete — Delete a context document
- lore_activity — Project activity (action: feed | log)
- lore_usage — Your rate limits and each project's usage against its caps
- lore_feedback — Send feedback, bug reports, or help requests to the Lore team
- lore_logout — End your session

## Personal Project

Every user has a personal project, created automatically
on sign-up. Use it for personal tasks, notes, and preferences;
pass projectId "personal" to reach it from any project tool.
It does not count toward the project quota. It cannot be
deleted or shared with other members.

Tool responses may include alerts about changes since your
last activity; they are intended for display to the user.

When the user asks "what's new?" or starts their day,
lore_project (action summary) + lore_inbox give a full briefing.
```