larkx generates a compact, plain-text index of your project that GitHub Copilot can read as context. Instead of Copilot guessing at your codebase structure, it gets a clean map of every file, export, and relationship, at whatever level of detail fits your token budget.
GitHub Copilot does not natively support MCP (or has limited support depending on your plan). larkx handles this with a companion file: .larkx/context.md
Every time you run larkx index, this file is regenerated with a structured snapshot of your codebase. Drop it into Copilot Chat as context, reference it in your instructions file, or attach it to any AI session. No MCP configuration required.
context.md is human-readable Markdown. You can review it, trim it, or feed it to any AI tool, not just Copilot.
Generate the index at paths, symbols, signatures, or summary level. Pick what fits your Copilot context window.
larkx index only re-processes changed files. Add it as a pre-commit hook or run it manually, both work.
If your Copilot setup supports MCP, larkx serves both paths. One index, accessed two ways.
Generate the index at different levels depending on what you need and how much context you want to use.
~1–2KSmallest context, project structure overview~8–10KEvery exported function, class, and type~16KFull API surface with parameter types~24KOne-line explanation per filenpm install -g larkxlarkx init && larkx index.larkx/context.mdDoes GitHub Copilot support MCP?
GitHub Copilot in VS Code has limited MCP support in some configurations. larkx generates a .larkx/context.md file that Copilot can read directly as project context, no MCP required.
How does larkx help Copilot understand my project?
larkx generates a structured plain-text index of your codebase, file paths, exports, function signatures, and module relationships. You reference this file as context so Copilot has a map of your project without reading every file.
Does this work with VS Code Copilot Chat?
Yes. You can reference .larkx/context.md in Copilot Chat with @workspace or by adding it to your context window. Copilot gets a compact project map instead of raw file reads.
How often do I need to update the index?
Run larkx index after significant changes. For daily development, once per session is enough. larkx only re-processes changed files so re-indexing is fast.
Can I use larkx with Copilot and Claude Code at the same time?
Yes. larkx serves both: Copilot reads context.md, while Claude Code and Cursor use the MCP server. One index, two consumption paths.
Using Claude Code or Cursor?
Those tools support full MCP, larkx connects as a server and exposes six structured query tools, not just a static file. Token savings are typically higher with MCP. larkx for Claude Code → · larkx for Cursor →
Free, open source, no account. Works on any codebase.
Get started