Guide

Get started

The fastest way to start a superlore knowledge base — copy two lines into Claude and watch it build the whole thing, or scaffold from the terminal with the CLI.

The fastest way to a superlore knowledge base is to let Claude build it. Copy two lines, paste them into Claude, and you get a complete, MCP-enabled KB — no setup, no framework to learn.

Let Claude build it

Add the superlore marketplace (one time)

Paste into Claude — on its own:

/plugin marketplace add KrishnanSG/superlore

Install the plugin

Then, as a separate command:

/plugin install superlore@superlore

Ask for your knowledge base

In a fresh chat, paste:

Make me a docs site with superlore

That's it. Claude takes it from there — and the superlore MCP ships with the plugin, so it can read the docs as it builds.

Copy → paste into Claude
Make me a docs site with superlore

What Claude does — automatically

Asks two quick questions

What kind of KB — a Company KB (internal, for your teams + agents) or Product Documentation (public, for your users) — and who can read itauth-protected (Google SSO gates the site and the MCP) or public.

Warns if a company KB would be public

Choose a Company KB without auth and Claude flags it — an internal KB shouldn't be world-readable, and the MCP would expose the same content — then offers to add SSO first.

Scaffolds, seeds, and connects

It generates the whole project, writes superlore.json, seeds a page or two so it isn't empty, mounts the MCP route, and offers to register the MCP with your agent — narrating each step.

Then just keep talking to Claude

"add a page about our onboarding", "make a Q3 roadmap", "diagram our architecture" — the superlore skills turn intent into structured pages. When you're ready, ask Claude to deploy (self-host anywhere today; superlore Cloud is waitlisted).

Or scaffold from the terminal

Prefer a CLI? One command installs it — nothing to clone:

curl -fsSL https://superlore.vercel.app/install.sh | sh

Windows (PowerShell): irm https://superlore.vercel.app/install.ps1 | iex. Already have a Node package manager? npm i -g superlore-cli works too.

superlore init my-kb   # asks the same 2 questions, writes superlore.json, seeds pages
cd my-kb
superlore dev          # local preview at http://localhost:3000

superlore init finishes by offering to set up your editor — it detects VS Code, Cursor, and Windsurf and installs the superlore Preview extension into each, so you get a live, dual-representation preview of every component as you type. Run it any time on its own:

superlore connect      # detects your editor(s), installs the live-preview extension

One get-started path: install the CLI → superlore init scaffolds the KB and sets up your editor → then connect the MCP so your agent reads the same corpus (connect prints the exact claude mcp add command, or just ask Claude to "connect my superlore MCP").

Author a first page

---
title: Q3 Roadmap
summary: What ships this quarter and when.
tags: [roadmap]
---

<Timeline
  items={[
    { date: "2026-07-01", title: "Kickoff", status: "done" },
    { date: "2026-Q3", title: "GA launch", status: "planned" },
  ]}
/>

That single Timeline renders a polished, accessible list for humans and serializes to a structured { kind: "timeline", items: [...] } your agent reads over the MCP. You wrote the data once — there's one source.

Where to next

Light and dark are equal

superlore ships both themes from one token set and defaults to the reader's system preference. Never branch on theme in your code — it's a pure CSS-token swap.

On this page

Built withsuperlore