Lex
Wire Claude Code into the Lex typed-effects toolchain and lex-hub MCP gateway for check, repair, publish, and run loops on Lex projects.
Overview
lex is a plugin marketplace for the Build phase that connects Claude Code to the Lex toolchain, idiom rules, and lex-hub MCP tools for agent-driven check, repair, publish, and run workflows.
What is this marketplace?
- Lex agent-code loop covering check, repair, publish, and run against Lex sources
- Idiom and style rules baked in for consistent Lex agent output
- MCP tools aimed at a hosted lex-hub gateway for remote operations
- Single integrations/claude-plugin entry focused on lex-lang and typed-effects
- Keywords surface lex-hub, typed-effects, and MCP for catalog discovery
- Marketplace bundles 1 plugin: lex (languages category, MCP and lex-hub keywords).
Community signal: 3 GitHub stars.
What problem does it solve?
Generic coding agents do not understand Lex typed-effects, hub gateways, or project-specific idioms, so Lex authors waste cycles correcting output and wiring tools by hand.
Who is it for?
Solo builders already on Lex or lex-hub who want Claude Code to enforce language idioms and automate the check-repair-publish-run cycle.
Skip if: Teams with no Lex footprint who only need generic TypeScript or Python assistance without a typed-effects language or hub gateway.
What do I get? / Deliverables
After adding the marketplace plugin, Claude can run the Lex agent loop and call lex-hub via MCP so fixes and publishes align with your Lex project conventions.
- Registered lex Claude plugin with check-repair-publish-run commands
- MCP-connected agent sessions against lex-hub when configured
- Idiom-guided Lex edits consistent with the bundled rules
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Lex plugins target the implementation window where agents need language-specific rules and gateway tools alongside code generation. Agent-tooling is the canonical shelf because the bundle is an agent-code loop plus MCP exposure to lex-hub, not a one-off UI or deploy script.
How it compares
Language-specific agent toolchain with MCP gateway hooks, not a general-purpose skill pack or standalone CI marketplace.
Common Questions / FAQ
Who is Lex for?
Lex language authors and indie agent builders who use Claude Code and optionally a hosted Lex-hub gateway for typed-effects projects.
When should I use Lex?
Use it during active Lex development when you want automated checks, repairs, publishes, and runs with MCP-backed hub access instead of manual CLI juggling.
How do I add Lex to my agent?
Install the alpibrusl/Lex-lang Claude marketplace plugin from the repo integrations/claude-plugin path and configure MCP toward your Lex-hub endpoint per the plugin docs.