Skip to content
Logic2BUI

Search docs

Search components and documentation

New
Menu

Compare Integration Paths

Choose the right logic2b workflow for a developer, coding agent or custom registry client.

There is one source registry and six ways to consume it. The component code is the same; what changes is who resolves dependencies, who writes files and whether a terminal is available.

Browser

Website + Copy Prompt

Exploring visually and handing a complete brief to an assistant.

Terminal

CLI

A developer adding source directly to an existing repository.

Editor extension

VS Code

Developers who want visual discovery, CLI-backed installs and presets in their workspace.

Streamable HTTP

Remote MCP

Agents requesting source and plans over HTTP; applying them requires host file tools and a build runtime.

stdio via npx

Local MCP

Terminal-backed agents that prefer MCP's structured contracts.

HTTPS JSON

Raw registry

Custom tooling that owns dependency resolution and file writes.

Capability comparison for every logic2b integration path
CapabilityWebsite + Copy PromptCLIVS CodeRemote MCPLocal MCPRaw registry
No shell requiredThe access method itself works without a terminal on the client.YesNoYesYesNoYes
Returns complete sourceThe path exposes the registry files rather than an opaque runtime component.YesYesYesYesYesYes
Resolves transitive itemsRegistry dependencies are expanded into the resulting install operation or plan.GuidedYesYesYesYesManual
Writes project filesThe logic2b tool mutates the repository itself. MCP deliberately returns a plan for its host agent to write.NoYesYesPlan onlyPlan onlyNo
Complete starter planProduces a runnable Next.js, Vite or Astro application contract from an empty directory.GuidedNoNoYesYesManual
Exact preset applicationApplies the complete /create preset contract instead of only returning the base theme.GuidedYesYesYesYesManual
Theme contract lintChecks missing, duplicate and invalid tokens, drift and contrast regressions.NoNoNoYesYesNo

“Plan only” means the MCP tool returns project-relative paths, complete file contents and dependencies; the connected host or agent remains responsible for writing them.

Choose in 30 seconds

  • You are browsing or deciding: use the website. Every install surface can return source, a CLI command or a self-contained Copy Prompt.
  • You have a terminal and an existing repository: use the CLI. It resolves registry dependencies and writes the source into your configured aliases.
  • You work primarily in VS Code: use the extension preview to browse and search visually, launch CLI-backed installs and apply exact presets in local or remote workspaces.
  • Your agent has no shell or local Node runtime: connect the remote MCP at https://ui.logic2b.com/mcp. install_plan and scaffold_plan return the complete file contents as JSON plans (text fallback in the published RC).
  • Your terminal-backed agent already speaks MCP: run npx -y @logic2b/mcp@next. The local server exposes the same contracts as the remote endpoint.
  • You are building your own integration: consume /r/index.json and /r/<name>.json. Your client owns recursive dependency resolution and writes.

The maintenance boundary

Installation is only the first step. A /create preset can travel through the studio, CLI, VS Code and MCP without losing choices. Later, an MCP-connected agent can pass the repository’s stylesheet to lint_theme to detect missing, duplicate or invalid tokens, derived-token drift, exact-preset drift and measured contrast regressions. The stylesheet is parsed as text and never executed.

MCP tools do not silently mutate a repository. They return explicit plans; the connected host needs file-writing tools to apply them, plus a runtime to install dependencies, build and verify the application. This keeps the same server usable by local IDEs, web assistants and controlled enterprise clients.

Verify the claims

  • Framework benchmarks publish exact-pinned fixtures, methodology and raw measurements.
  • Agent benchmarks publish the task protocol and objective scorer before any model result is accepted.
  • The release gate packs both npm artifacts, installs them into a clean consumer and verifies CLI help/version plus the MCP tool inventory.
  • Every registry item is validated for resolvable dependencies and parseable payloads; every generated starter contract is production-built in CI.