superlore

The company knowledge base your agents run on.

Your agents turn specs, transcripts, and brainstorms into rich, structured docs — canvases, boards, timelines — that compound into one company knowledge base every agent can read over MCP.

One corpus. Humans and agents.

_{Open source · MCP-native · Deploy anywhere}

 

Website  ·  Docs  ·  Live demo  ·  MCP

Get started

Let your agent build it — three quick pastes into Claude (run each on its own, in order):

1 · Add the marketplace (one time)

/plugin marketplace add KrishnanSG/superlore

2 · Install the plugin

/plugin install superlore@superlore

3 · Ask for your knowledge base — in a fresh chat

Make me a docs site with superlore

That's it. Claude scaffolds the project, seeds a page or two, wires up the MCP, sets up your editor, and previews it — then you keep talking to it to author. No framework to learn.

Prefer the terminal?

curl -fsSL https://superlore.vercel.app/install.sh | sh
superlore init my-kb && cd my-kb && superlore dev

Adding superlore to an existing Next.js app? See Getting started.

One block, two faces

Half your docs are read by agents now, not people — and every other tool just bolts an MCP onto the old way of writing them, serving scraped, lossy HTML. superlore rethinks the document for a world where AI writes, reads, and maintains it: every component is dual-representation. You author once, and the same block renders a beautiful, interactive surface for humans and serializes to clean, typed data an agent reads over MCP — provably one source, no drift.

The board a human sees is the typed graph an agent reads — queryable structure, not a flat image.

What you get

• Dual-representation components — Canvas, Timeline, Board, EntityCard, Table, Decision, and more. Each renders for humans and serializes to a typed knowledge face for the MCP.
• The Canvas — FigJam, in code. Declare nodes, edges, and groups; superlore auto-designs and lays out an interactive whiteboard. The board is the typed graph.
• MCP-native. Every deploy serves an MCP at /api/mcp over the same content the site renders — search, get_page, list, navigate, get_component_data.
• The Viewer — drop in any .mdx and see it render live, with comments and export. Try it →
• Editor extension — live preview of every component in VS Code, Cursor, and Windsurf.
• One-config auth — Auth.js + Google SSO, off by default; gate the site or just the MCP, and the MCP inherits the same policy.
• Yours to deploy — it's MDX in your repo: ship to Vercel, Cloudflare, or your own box. Or let superlore Cloud host it for you.

Read the docs →

Built with superlore

Shipped a KB with superlore? Add the badge:

Built with superlore

[![Built with superlore](https://superlore.vercel.app/built-with-superlore.svg)](https://superlore.vercel.app)

Contributing & license

superlore is open source and built to grow a community. Read CONTRIBUTING.md and the CODE_OF_CONDUCT.md; report a vulnerability via SECURITY.md. PRs welcome.

Apache-2.0 © Krishnan S G