Connect via MCP

Add it to Claude Code

One command:

claude mcp add --transport http lbusd-timeline https://lbusdtimeline.org/mcp

Or commit a project-scoped .mcp.json so your whole team picks it up:

{
  "mcpServers": {
    "lbusd-timeline": {
      "type": "http",
      "url": "https://lbusdtimeline.org/mcp"
    }
  }
}

Other clients

Any MCP client that supports a remote / HTTP server works — add a custom connector with the transport set to HTTP and the URL above. No API key, no authentication: the data is already public.

To poke it directly, it's plain JSON-RPC 2.0:

curl -s https://lbusdtimeline.org/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Tools (7)

Every tool is read-only. A good flow: get_overview for orientation, search_timeline and list_entities to find things, then the get_* tools for full, cited detail.

• get_overview

  Counts and a short description of the dataset — events, sources, citations, meetings, people, and organizations. A good first call.

• search_timeline

  Search timeline events. Filter by era and/or topic, and/or match a free-text query against event titles and descriptions. Returns events in chronological order.

• list_entities

  List the ids and names of people, organizations, meetings, or sources, so you can then fetch one with the get_* tools.

• get_event

  Full detail for one timeline event by id, including every citation (source, quote, context) and the people involved.

• get_person

  Full detail for one person by id — bio, role, the timeline events they appear in, and any sources they authored.

• get_organization

  Full detail for one organization by id — description, members, and the timeline events its members appear in.

• get_meeting

  Full detail for one board meeting by id — summary, key insights, video link, and the timeline events the meeting produced.