Lore / Docs

Appearance

Connect your agent ​

Set up your coding agent

Copy this prompt and paste it into your coding agent’s chat. Complete GitHub sign-in in the browser when prompted.

Set up Lore for this coding agent across all my projects using its user-level MCP configuration. Read https://docs.buildwithlore.ai/SKILL.md and follow its instructions. Preserve existing MCP settings, add Lore if needed, and start its OAuth login. If I am new to Lore, guide me through GitHub signup and repository onboarding in the browser, then retry the agent login if needed. Verify access to my current project's repository using list_repos and get_context. Tell me what succeeded and any steps I still need to complete.
Read the setup skill ↗

The public setup skill contains instructions for Claude Code, Codex, and Cursor, plus guidance for other clients that support remote HTTP MCP with OAuth. Your agent chooses the matching instructions. You do not need to download or permanently install the skill to use this prompt.

The connection is saved once for the agent you use, rather than separately in every repository. If you use multiple agents, connect each one once. This does not grant access to every repository: Lore still respects your GitHub permissions and the repositories selected in the GitHub App installation.

Your agent can configure the connection where it has access. You complete browser sign-in and choose which GitHub repositories to connect. Lore ingests them automatically; there is no review queue to work through afterward. New users are returned to the agent authorization screen after repository setup. Approve the connection there and return to your agent. If setup takes long enough for the request or client to time out, start agent login again; repository setup stays saved.

If your agent cannot open links, open SKILL.md yourself and paste its contents into the same chat. If it cannot change MCP settings, use the manual instructions below. A client without remote HTTP MCP and OAuth support cannot connect just by receiving the prompt.

Manual setup ​

Lore exposes a remote Streamable HTTP MCP endpoint:

text
https://mcp.buildwithlore.ai/mcp

MCP is the connection that lets your agent call tools provided by Lore. “Remote” means Lore runs on our servers. “Streamable HTTP” is the connection type to choose when your client asks. You do not start a local Lore process.

Your client must support remote HTTP MCP and browser-based OAuth. Authorize with your own GitHub account; you do not need a Lore operator's GitHub App private key or provider API keys.

OAuth is the browser sign-in and approval step. It lets you grant the client access without copying your password into its configuration. Adding the server and authorizing it are separate steps: a server can be listed but not yet signed in.

Claude Code ​

sh
claude mcp add --transport http --scope user lore https://mcp.buildwithlore.ai/mcp

Open Claude Code, run /mcp, and authenticate the Lore connection if prompted. The --scope user option makes Lore available across your projects.

What to expect: Lore appears in the MCP server list. After sign-in, ask Claude to use Lore's list_repos tool. Confirm it makes a tool call rather than answering from the files already open in your session.

Codex ​

sh
codex mcp add lore --url https://mcp.buildwithlore.ai/mcp
codex mcp login lore

Complete the browser authorization, then start a session with the connection enabled.

The first command saves the server URL. The second signs in. If your browser opens, finish the approval and return to the terminal; do not copy an authorization code or access token into chat.

The connection uses your user-level Codex configuration, normally ~/.codex/config.toml, so you do not need to add it to every repository.

Cursor ​

Add this server to your user-level ~/.cursor/mcp.json, or copy the configuration from Lore's Agent setup page:

json
{
  "mcpServers": {
    "lore": {
      "url": "https://mcp.buildwithlore.ai/mcp"
    }
  }
}

Enable the server in Cursor's MCP settings and complete authentication when prompted.

If your configuration already contains other MCP servers, add the lore entry inside the existing mcpServers object. Do not replace the entire file and lose your other connections.

Use .cursor/mcp.json inside a project only if you specifically want a project-only connection. Do not add passwords or operator credentials to either file.

Other clients ​

Add a remote HTTP server named lore with the endpoint above in your client's user-level settings so it is available across projects. Configuration file formats and authentication controls vary by client. Use your client's instructions for remote MCP with OAuth rather than assuming the Cursor JSON format applies.

Verify the connection ​

Ask the agent to call list_repos. It should return only repositories your GitHub account can access. Next, call get_context with a returned repository's full name.

If authorization fails or a repository is missing, see Troubleshooting.

Disconnect an agent ​

In Lore, open Agent setup, find the client under Connected clients, and choose Revoke. This revokes that connection's tokens. The client must sign in again to regain access. Removing a local configuration entry only removes it from that client; use Lore's revoke control when you want to invalidate the connection.