# 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 "Me" 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
- lore_logout — End your session

**Projects**
- lore_project — List your projects, get one project's details and members, or summarize changes since your last check (action: list | info | summary)
- lore_create_project — Create a new project (you become owner)
- lore_delete_project — Permanently delete a project (owner only)
- lore_invite_member — Add someone to a project by email
- lore_remove_member — Remove a member from a project

**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.

### 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
Cursor Settings: Tools & MCP and click Connect next to Lore.

### VS Code (GitHub Copilot)
Create `.vscode/mcp.json` in the project root:
```json
{
  "servers": {
    "lore": {
      "type": "http",
      "url": "https://mcp.onelore.ai"
    }
  }
}
```
If the file already exists, add the "lore" entry inside
the existing "servers" object.

To make Lore available in all VS Code projects, add the
same config via VS Code User MCP Configuration instead.

VS Code picks the file up immediately — tell the user to
click Start above the server entry, Allow the auth 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/config.json` under
"mcpServers" with "url" and "transport": "http".
On the legacy Cascade agent,
`~/.codeium/windsurf/mcp_config.json` with a "serverUrl"
field still works — OAuth starts automatically when the
server is added.

### 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, choose As JSON, paste:
```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 lore https://mcp.onelore.ai
This adds Lore globally for all projects.

---

### Claude Desktop

Go to Settings > Connectors, click Add, enter: https://mcp.onelore.ai

---

### 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"
    }
  }
}
```

---

### OpenAI Codex CLI

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

---

### Mistral Le Chat

Open Le Chat. In the sidebar, expand Intelligence > Connectors.
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

Go to Settings > Apps > Developer Mode, click Create app,
enter: https://mcp.onelore.ai

---

## After Setup

1. Reload or restart your IDE/app if prompted.
2. Sign in with your Google account when OAuth appears.
3. Call lore_whoami to verify the connection.

## 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
- lore_project — Your projects (action: list | info | summary)
- lore_create_project — Create a new project
- lore_delete_project — Permanently delete a project (owner only)
- lore_invite_member — Add someone to a project
- lore_remove_member — Remove someone from a project
- 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 plan, rate limits, and resource usage
- lore_feedback — Send feedback, bug reports, or help requests to the Lore team
- lore_logout — End your session

## Personal "Me" Project

Every user has a personal "Me" project, created automatically
on sign-up. Use it for personal tasks, notes, and preferences.
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.
```