Lore MCP Server

by bluedotsoftware Your server? Claim it

answering

Lore is answering right now. Last checked 13 min ago.

Cache source-backed repository context so coding agents can reuse knowledge across sessions.

Uptime history 10 days of history · worst day 0%

10 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

433 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Lore does not always answer

Over the last week it answered 71.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://mcp.buildwithlore.ai/mcp

~/.codex/config.toml

[mcp_servers.lore]
url = "https://mcp.buildwithlore.ai/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

{
  "servers": {
    "lore": {
      "type": "http",
      "url": "https://mcp.buildwithlore.ai/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.buildwithlore.ai/mcp	streamable-http	sign-in	416 ms	13 min ago

Alternatives to Lore

same job, measured the same way

Coador

by automaticqa

Evidence-backed Android repository knowledge for humans and AI agents

64 installs/wk local only

crewlore

by srijansk

Team knowledge compiled from your coding agents' sessions and pull requests, every entry cited.

1 236 installs/wk local only

Sippion

by sitten-tokyo

Local read-only repository context retrieval for AI coding agents.

local only

LeanToken

by morluto

Token-bounded repository context for coding agents over MCP.

local only

Codeledger

by codeledgerecf

Deterministic context selection for AI coding agents. Local memory that compounds across sessions.

376 installs/wk local only

RepoContext

by shmindmaster

Read-only, commit-pinned repository context for coding agents.

local only

codemem

by jeang42

Shared memory for coding agents: projects, reusable code, sessions and commits across machines

101 installs/wk local only

Baton

by kasabeh

Pass the baton between coding agents: convert sessions across Claude Code, OpenCode, Codex & more.

36 installs/wk local only

Lore — questions

Answers built from our own checks of this server.

Why is there no tool list for Lore?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Lore working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 433 ms. The bar chart above shows every period we have measured.

How do I connect Lore?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Lore?

No API key is involved. Lore answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Lore?

It answers our handshake in 433 ms on average, which is faster than 32% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.