# Leadtype

> Framework-neutral docs pipeline tooling for MDX, LLM bundles, and search.

## Product Summary

Leadtype is a docs pipeline for teams that want one MDX source to serve humans, search interfaces, and coding agents. It turns authored docs into markdown mirrors, `llms.txt`, `llms-full.txt`, static search indexes, Agent Readability metadata, package-bundled `AGENTS.md`, and optional MCP-ready artifacts.

Use Leadtype when you already own the docs UI or framework integration and need a reliable content layer for agent-readable documentation. It works with custom apps and docs frameworks, including Next.js, Fumadocs, Astro, Nuxt, SvelteKit, and TanStack Start.

## When to Use Leadtype

- Use Leadtype to generate agent-readable docs artifacts from MDX without replacing your existing docs UI.
- Use Leadtype for documentation sites that need static markdown mirrors, local search, source-grounded AI answers, or MCP retrieval.
- Use Leadtype for package docs when consumers should get version-matched `AGENTS.md` and markdown files inside `node_modules`.
- Use Leadtype collections when a docs UI repo renders source content from another repo and needs a reviewed, reproducible source pin.
- Do not use Leadtype as a rendered component library or visual docs framework; the host app owns UI, routes, styling, and accessibility.

## Agent Guidance

- Start with `/llms.txt` for the curated map of important pages.
- Use `/llms-full.txt` only when page-level markdown is not enough or a complete fallback context is needed.
- Prefer the linked markdown pages for implementation details because they are generated from the same MDX source as the human docs.
- For package-local usage, read the bundled `AGENTS.md` shipped with the installed `leadtype` package.
- For retrieval workflows, use the generated search index or MCP surface instead of scraping rendered HTML.

## Best Starting Points

- [Leadtype](/docs/index.md): Understand what Leadtype generates and where it fits in a docs stack.
- [Quickstart](/docs/quickstart.md): Install Leadtype, author the first MDX page, and create a docs source.
- [Build a docs site](/docs/pipeline/build-a-docs-site.md): Choose the right integration shape for a hosted docs app.
- [Generate static artifacts](/docs/pipeline/generate-static-artifacts.md): Generate markdown mirrors, search files, sitemaps, robots, and agent metadata.
- [Sync docs across repos](/docs/pipeline/sync-docs-across-repos.md): Pin remote docs sources and inherit source-owned navigation/config.
- [Bundle docs into a package](/docs/package-docs/bundle.md): Ship version-matched `AGENTS.md` and markdown docs inside an npm package.
- [CLI](/docs/reference/cli.md): Reference for `generate`, `sync`, `lint`, `score`, and MCP commands.
- [MCP](/docs/reference/mcp.md): Expose generated docs through stdio or hosted Streamable HTTP MCP.
- [WebMCP](/docs/reference/webmcp.md): Register generated docs as browser-side WebMCP tools for on-page agents.
- [Changelog](/changelog.md): Read Leadtype release notes and product updates.

## Community and Social Links

- Inth website: [inth.com](https://inth.com)
- GitHub: [github.com/inthhq/leadtype](https://github.com/inthhq/leadtype)
- npm: [npmjs.com/package/leadtype](https://www.npmjs.com/package/leadtype)
- Discord: [leadtype.dev/discord](https://leadtype.dev/discord)
- X / Twitter: [@inth](https://x.com/inth)
- Bluesky: [@inth.com](https://bsky.app/profile/inth.com)

## Agent Interfaces

- MCP server (Streamable HTTP): https://leadtype.dev/mcp (server card: https://leadtype.dev/.well-known/mcp/server-card.json) — search-docs, get-page tools over this documentation.
- NLWeb /ask endpoint: https://leadtype.dev/ask — natural-language queries over this documentation, JSON or SSE.