Read the right contract.
Use focused tools and stable resources to build from the catalog, check compatibility, and keep your agent’s context current.
- Tools
- 14
- Resources
- 10
What agents can do
Focused MCP tools
Every tool returns readable text plus validated structured content, grounded in the same catalog, docs, web and native source, tokens, and rules the packages ship.
lumen_check_compatibilityCompare resolved installed versions before applying catalog contracts.
lumen_get_migrationRead v4 migration guidance and package-specific review decisions without changing files.
lumen_list_componentsList every component with its framework availability and recipe membership. Filter by framework, recipe, or a name query.
lumen_get_componentReturn framework-specific imports, styles, props or attributes, examples, accessibility behavior, events, and optional source.
lumen_list_native_componentsList native components with React Native, SwiftUI, and Compose availability, accessibility, category, and contract tier.
lumen_get_native_componentReturn native install and setup steps, imports, API rows, examples, accessibility guidance, and optional adapter source.
lumen_get_recipeReturn a recipe’s purpose, categories, components, files, and framework-specific install command.
lumen_searchRank natural-language matches across web or native platform contracts, recipes, tokens, and rules.
lumen_get_metaReturn the schema version, package versions, component count, and deterministic catalog hash.
lumen_get_catalog_manifestReturn stable fingerprints for every web component, native component, and recipe.
lumen_diff_catalogCompare a retained manifest with the current catalog and identify exactly which entries changed.
lumen_diagnoseVerify snapshot integrity and report web framework plus native platform coverage.
lumen_get_tokensReturn semantic token names, base color values, glass tokens, and the theme attribute for generated code.
lumen_get_rulesReturn the Lumen agent rules (llms.txt) to read before producing Lumen code.
Stable context
Browsable MCP resources
Clients can read or cache stable catalog context without calling a tool. Component and recipe templates are enumerable and support name completion.
lumen://metaSnapshot provenance, package versions, and deterministic catalog hash.
lumen://catalog-manifestStable web, native, and recipe fingerprints for change detection.
lumen://diagnosticsSnapshot integrity checks and web plus native coverage.
lumen://rulesAgent generation rules as Markdown.
lumen://tokensStructured semantic, color, glass, and theme tokens.
lumen://componentsCompact structured component catalog.
lumen://components/{name}One component’s metadata and default Astro usage.
lumen://native-componentsNative component catalog with platform availability.
lumen://native-components/{name}One native component’s metadata and platform usage.
lumen://recipes/{name}Recipe metadata and framework install commands.
How agents use it
Discover, read, and stay on-system
Start compact, read the target framework or platform usage contract, and request full source only when the imports, examples, accessibility notes, and API rows are insufficient.
- 01
Verify the snapshot
lumen_get_meta identifies the snapshot and lumen_diagnose verifies web and native coverage.
- 02
Check installed versions
lumen_check_compatibility compares resolved versions; use installed types when the catalog differs.
- 03
Discover
The agent lists web or native components, or searches with a target framework or platform.
- 04
Read target usage
The matching get tool returns installation, setup, imports, API, examples, accessibility, and runtime guidance.
- 05
Compose a recipe
lumen_get_recipe explains multi-component patterns and gives the correct framework install command.
- 06
Track changes
Retain lumen://catalog-manifest and compare it after upgrades to refresh only contracts that changed.