@bearnie/mcp 0.1.3 → 0.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -123,6 +123,25 @@ Add multiple components in one step. Resolves registry dependencies and installs
123
123
 
124
124
  **Example prompt:** "Add button, card, and barrel to my project"
125
125
 
126
+ ### `list_installed`
127
+
128
+ List the Bearnie components already installed in the project, and whether each one is up to date with the registry, modified locally, or missing files. To update an outdated component, run `add_component` with its name (this overwrites local files with the registry version).
129
+
130
+ Styles are compared against the theme recorded in `bearnie.json` (`default`, or any base/accent combination such as `blue`, `slate`, or `slate-blue`). Installing a theme entry such as `styles-slate-blue` via `add_component` switches the theme and updates `bearnie.json`.
131
+
132
+ **Parameters:**
133
+
134
+ - `cwd` (string, optional): Working directory
135
+
136
+ **Example prompts:**
137
+
138
+ - "Which Bearnie components does this project use?"
139
+ - "Are my Bearnie components up to date?"
140
+
141
+ ## Dependency Installation
142
+
143
+ When a component needs npm packages, the server installs them automatically using your project's package manager, detected from the lockfile (npm, pnpm, yarn, or bun). It also respects custom directories from `bearnie.json` if present.
144
+
126
145
  ## Environment Variables
127
146
 
128
147
  | Variable | Description |