Skip to main content
Join the waitlist

Local MCP

Component discovery, token lookup and saved-file checks for an agent working in your repository.

This server comes from @usefragments/cli. It is optional package tooling. Fragments desktop manages its own agent tools and Checks; it does not require this setup.

  1. Configure the project

    Start from a working React app with its dependencies installed. From the app root, configure the CLI and available agent integrations:

    npx @usefragments/cli@latest init --install --metadata-only --no-ci

    To select one host, add --agents claude, --agents codex or --agents cursor. Review the generated files and resolve any action-required output. The launcher uses the project’s installed CLI.

  2. Verify the connection

    Restart the agent and approve its project integration when prompted. Ask it to call contract and confirm the intended repository context. Then try search for a component your app uses.

    npx @usefragments/cli doctor

    Doctor separates configuration, command probes and observed host delivery. A successful probe does not prove that the agent loaded the integration. Follow any recovery steps; an unavailable authority or an incomplete check is not a clean result.

Use the local tools

Published local MCP tools
Tool
Use it to
contractInspect the selected authority and component/token counts.
searchFind matching components or curated patterns.
getRead a component’s members, props and usage guidance.
tokensLook up matching token vocabulary.
checkCheck a saved file in the repository and inspect the reported findings.

Results depend on the project’s selected sources and available metadata. Discover the relevant components before editing; save the file before asking the tool to check it.

Manual stdio launch

For an MCP client that asks for a command, use the local launcher below with the app root as its working directory. Let the client manage the process.

npx @usefragments/cli mcp --stdio

Next steps