# 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 source of truth. No stale docs, no context drift, no miscommunication. **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_create_project — Create a new project (you become owner) - lore_delete_project — Permanently delete a project (owner only) - lore_list_projects — List all projects you belong to - lore_project_info — Get project details and member list - lore_project_summary — Activity summary since last check - lore_invite_member — Add someone to a project by email - lore_remove_member — Remove a member from a project **Tasks** - lore_create_task — Create a task in a project - lore_list_tasks — List tasks with optional filters - lore_update_task — Update status, assignee, or priority - lore_task_detail — Get full task details - lore_delete_task — Delete a task from a project **Messaging** - lore_send_message — Send a message to a team member - lore_inbox — View messages with filters - lore_mark_read — Mark one or more messages as read - lore_delete_message — Delete an unread, unreplied message - lore_read_thread — Read a full message thread - lore_update_message — Update linkage fields on a message **Context Storage** - lore_context_list — List files and folders at a path - lore_context_read — Read a context document - lore_context_write — Create or update a context document - lore_context_delete — Delete a context document - lore_context_tree — Show full directory tree **Activity** - lore_activity_feed — Personal feed of watched events - lore_event_log — Full project event log ## 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. After creating the file, tell the user to reload the window. VS Code will show a notification to start the MCP server. ### Windsurf Add to `~/.codeium/windsurf/mcp_config.json`: ```json { "mcpServers": { "lore": { "serverUrl": "https://mcp.onelore.ai" } } } ``` ### Cline Open Cline settings in VS Code, go to MCP Servers, click Add Server. Use: Name: lore Type: SSE URL: https://mcp.onelore.ai ### Continue.dev Create `~/.continue/mcpServers/lore.yaml`: ```yaml name: lore url: https://mcp.onelore.ai transport: streamable-http ``` ### Zed Add to Zed settings (Zed > Settings > Open Settings): ```json { "context_servers": { "lore": { "url": "https://mcp.onelore.ai" } } } ``` ### JetBrains (IntelliJ, WebStorm, PyCharm, etc.) Go to Settings > Tools > AI Assistant > MCP Servers. Click Add > URL, enter: https://mcp.onelore.ai --- ### 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 --- ### 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, always-fresh, 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, always-fresh, standardized context. ## MCP Server URL: https://mcp.onelore.ai Auth: Google OAuth (auto by MCP client) ## Available Tools - lore_whoami — Check your identity and projects (call this first) - lore_set_profile — Set your GitHub username - lore_create_project — Create a new project - lore_delete_project — Permanently delete a project (owner only) - lore_list_projects — List your projects - lore_project_info — Get project details and members - lore_project_summary — Watched task changes since last check - lore_invite_member — Add someone to a project - lore_remove_member — Remove someone from a project - lore_create_task — Create a task in a project - lore_list_tasks — List tasks with optional filters - lore_update_task — Update task status, assignee, or priority - lore_task_detail — Get full task details - lore_delete_task — Delete a task - lore_send_message — Message another Lore user (supports replies) - lore_inbox — View messages with filters (status, date range) - lore_mark_read — Mark a message as read - lore_delete_message — Delete an unread, unreplied message you sent - lore_context_list — List files and folders in project context - lore_context_read — Read a context document - lore_context_write — Create or update a context document - lore_context_delete — Delete a context document - lore_context_tree — Show full directory tree of project context - lore_activity_feed — Personal feed of watched events - lore_event_log — Full project event log (unfiltered) - 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. Every tool response includes alerts about changes since your last activity. Present these to the user naturally. When the user asks "what's new?" or starts their day, call lore_project_summary + lore_inbox for a full briefing. ```