Documentation

Connect Lore.

Lore exposes its company brain as both a remote MCP server and a plain REST API. Pick whichever your agent or workflow tool speaks. All endpoints accept a Bearer token; demo reviewers can use the shared demo password.

Auth

Bearer token

Every endpoint takes Authorization: Bearer <token>. The demo workspace accepts the demo password as a token; production tenants get a per-tenant LORE_TOKEN via env.

export LORE_TOKEN="<your-token>"

MCP - IDE agents

Remote MCP server

Endpoint: https://jointhelore.com/api/mcp/northstar. Three tools: lore_skills_list, lore_skills_section_list, lore_skills_load. Modular loading so an agent only pays context for the section it needs.

Claude Code

claude mcp add lore \
  --transport http \
  --url "https://jointhelore.com/api/mcp/northstar" \
  --header "Authorization: Bearer $LORE_TOKEN"

Cursor - settings.json

{
  "mcpServers": {
    "lore": {
      "url": "https://jointhelore.com/api/mcp/northstar",
      "headers": {
        "Authorization": "Bearer ${env:LORE_TOKEN}"
      }
    }
  }
}

Codex CLI

# ~/.codex/config.toml
[mcp_servers.lore]
url = "https://jointhelore.com/api/mcp/northstar"
[mcp_servers.lore.headers]
Authorization = "Bearer ${LORE_TOKEN}"

Windsurf - mcp.json

{
  "mcpServers": {
    "lore": {
      "serverUrl": "https://jointhelore.com/api/mcp/northstar",
      "headers": {
        "Authorization": "Bearer ${LORE_TOKEN}"
      }
    }
  }
}

REST - Everything else

HTTP API

For n8n, Zapier, internal scripts, and anything that doesn't speak MCP. Same data, JSON shape.

List skills

curl https://jointhelore.com/api/v1/skills?workspace=northstar \
  -H "Authorization: Bearer $LORE_TOKEN"

Read a single skill

curl https://jointhelore.com/api/v1/skills/refund-handling?workspace=northstar \
  -H "Authorization: Bearer $LORE_TOKEN"

# Or get the raw markdown:
curl "https://jointhelore.com/api/v1/skills/refund-handling?workspace=northstar&format=md" \
  -H "Authorization: Bearer $LORE_TOKEN"

Ask the brain

curl -X POST https://jointhelore.com/api/v1/chat \
  -H "Authorization: Bearer $LORE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"workspace":"northstar","query":"What is the refund authority matrix?"}'

SDK

Anthropic Agent SDK

Anthropic's SDK supports remote MCP via the url tool type. Mount Lore as one tool and the agent uses it natively in any messages call.

import Anthropic from "@anthropic-ai/sdk";

const client = new Anthropic();
const response = await client.messages.create({
  model: "claude-opus-4-7",
  max_tokens: 1024,
  tools: [
    {
      type: "url",
      name: "lore",
      url: "https://jointhelore.com/api/mcp/northstar",
      authorization_token: process.env.LORE_TOKEN,
    },
  ],
  messages: [
    { role: "user", content: "How do we handle refunds over $5,000?" },
  ],
});

Workflow tools

n8n, Zapier, Make

Native nodes for n8n and Zapier ship after the first paid customer. In the meantime, both platforms have generic HTTP-request actions - point them at the REST endpoints above.

Questions: info@jointhelore.com