@rsc-kit/mcp/dist/bundleGuides.d.ts

An MCP server over what an rsc-kit build decided: the routes, why each one is static or not, and what it costs the browser.

export interface GuideEntry {
    slug: string;
    title: string;
    description: string;
}
/** One guide's MDX as markdown, with the samples it names inlined. */
export declare function toMarkdown(mdx: string, repoRoot: string): {
    entry: Omit<GuideEntry, 'slug'>;
    body: string;
};
/**
 * Every page under each of `from`, written as markdown into `into`, with an
 * index. The top-level pages - installation, coming from Next - and the
 * guides land in one flat list, because a slug is what an agent asks for and
 * which directory the site keeps it in is not its concern.
 */
export declare function bundleGuides(from: string | string[], into: string, repoRoot: string): GuideEntry[];
/** Where the bundled guides are, beside dist — or nowhere, before a build. */
export declare function guidesDir(): string | null;
export declare function listGuides(): string;
export declare function readGuide(slug: string): string;
/**
 * Lines matching a phrase across every bundled guide, with the guide and a
 * little context. A grep, deliberately - the guides are 250 KB and an agent
 * asking "where is fieldErrors mentioned" wants the lines, not a ranking.
 */
export declare function searchGuides(phrase: string, limit?: number): string;