@macroforge/mcp-server 0.1.65 → 0.1.66

package/docs/custom-macros/ts-quote.md

@@ -1,6 +1,8 @@
 # Template Syntax
 
-The `macroforge_ts_quote` crate provides template-based code generation for TypeScript. The `ts_template!` macro uses Svelte + Rust-inspired syntax for control flow and interpolation, making it easy to generate complex TypeScript code.
+The `macroforge_ts_quote` crate provides template-based code generation for TypeScript. The
+`ts_template!` macro uses Svelte + Rust-inspired syntax for control flow and interpolation, making
+it easy to generate complex TypeScript code.
 
 ## Available Macros
 
@@ -33,7 +35,8 @@ The `macroforge_ts_quote` crate provides template-based code generation for Type
 | `{$do expr}`                                                   | Execute a side-effectful expression                                                     |
 | `{$typescript stream}`                                         | Inject a TsStream, preserving its source and runtime_patches (imports)                  |
 
-**Note:** A single `@` not followed by `{` passes through unchanged (e.g., `email@domain.com` works as expected).
+**Note:** A single `@` not followed by `{` passes through unchanged (e.g., `email@domain.com` works
+as expected).
 
 ## Interpolation: `@{expr}`
 
@@ -62,9 +65,10 @@ User.prototype.toString = function () {
 };
 ```
 
-## Identifier Concatenation: ` content `
+## Identifier Concatenation: `content`
 
-When you need to build identifiers dynamically (like `getUser`, `setName`), use the ident block syntax. Everything inside ` ` is concatenated without spaces:
+When you need to build identifiers dynamically (like `getUser`, `setName`), use the ident block
+syntax. Everything inside `` is concatenated without spaces:
 
 Rust
 
@@ -88,7 +92,8 @@ function getUser() {
 }
 ```
 
-Without ident blocks, `@{}` always adds a space after for readability. Use ` ` when you explicitly want concatenation:
+Without ident blocks, `@{}` always adds a space after for readability. Use `` when you explicitly
+want concatenation:
 
 Rust
 
@@ -115,7 +120,8 @@ ts_template! { @{entity}_@{action} }  // → "user_create"
 
 ## Comments: `{> "..." <}` and `{>> "..." <<}`
 
-Since Rust's tokenizer strips whitespace before macros see them, use string literals to preserve exact spacing in comments:
+Since Rust's tokenizer strips whitespace before macros see them, use string literals to preserve
+exact spacing in comments:
 
 ### Block Comments
 
@@ -232,7 +238,8 @@ let code = ts_template! {
 
 ## Backtick Template Literals: `"'^...^'"`
 
-For JavaScript template literals (backtick strings), use the `'^...^'` syntax. This outputs actual backticks and passes through `${"${}"}` for JS interpolation:
+For JavaScript template literals (backtick strings), use the `'^...^'` syntax. This outputs actual
+backticks and passes through `${"${}"}` for JS interpolation:
 
 Rust
 
@@ -252,7 +259,8 @@ TypeScript
 const html = `<div>${content}</div>`;
 ```
 
-You can mix Rust `@{}` interpolation (evaluated at macro expansion time) with JS `${"${}"}` interpolation (evaluated at runtime):
+You can mix Rust `@{}` interpolation (evaluated at macro expansion time) with JS `${"${}"}`
+interpolation (evaluated at runtime):
 
 Rust
 
@@ -597,7 +605,8 @@ let code = ts_template! {
 
 ## Side Effects: `{$do}`
 
-Execute an expression for its side effects without producing output. This is commonly used with mutable variables:
+Execute an expression for its side effects without producing output. This is commonly used with
+mutable variables:
 
 Rust
 
@@ -620,7 +629,8 @@ Common uses for `{$do}`:
 
 ## TsStream Injection: `{$typescript}`
 
-Inject another TsStream into your template, preserving both its source code and runtime patches (like imports added via `add_import()`):
+Inject another TsStream into your template, preserving both its source code and runtime patches
+(like imports added via `add_import()`):
 
 Rust
 
@@ -758,14 +768,15 @@ pub fn derive_json_macro(input: TsStream) -> MacroResult {
 
 ## How It Works
 
-1.  **Compile-Time:** The template is parsed during macro expansion
-2.  **String Building:** Generates Rust code that builds a TypeScript string at runtime
-3.  **SWC Parsing:** The generated string is parsed with SWC to produce a typed AST
-4.  **Result:** Returns `Stmt` that can be used in `MacroResult` patches
+1. **Compile-Time:** The template is parsed during macro expansion
+2. **String Building:** Generates Rust code that builds a TypeScript string at runtime
+3. **SWC Parsing:** The generated string is parsed with SWC to produce a typed AST
+4. **Result:** Returns `Stmt` that can be used in `MacroResult` patches
 
 ## Return Type
 
-`ts_template!` returns a `Result<Stmt, TsSynError>` by default. The macro automatically unwraps and provides helpful error messages showing the generated TypeScript code if parsing fails:
+`ts_template!` returns a `Result<Stmt, TsSynError>` by default. The macro automatically unwraps and
+provides helpful error messages showing the generated TypeScript code if parsing fails:
 
 Text
 
@@ -810,7 +821,7 @@ ts_template! {
 
 ## Best Practices
 
-1.  Use `ts_template!` for complex code generation with loops/conditions
-2.  Use `ts_quote!` for simple, static statements
-3.  Keep templates readable - extract complex logic into variables
-4.  Don't nest templates too deeply - split into helper functions
+1. Use `ts_template!` for complex code generation with loops/conditions
+2. Use `ts_quote!` for simple, static statements
+3. Keep templates readable - extract complex logic into variables
+4. Don't nest templates too deeply - split into helper functions

package/docs/getting-started/first-macro.md

@@ -4,7 +4,8 @@ Let's create a class that uses Macroforge's derive macros to automatically gener
 
 ## Creating a Class with Derive Macros
 
-Start by creating a simple `User` class. We'll use the `@derive` decorator to automatically generate methods.
+Start by creating a simple `User` class. We'll use the `@derive` decorator to automatically generate
+methods.
 
 Before (Your Code)
 
@@ -163,6 +164,6 @@ Field-level decorators let you control exactly how each field is handled by the
 
 ## Next Steps
 
-*   [Learn how macros work under the hood](../../docs/concepts)
-*   [Explore all Debug options](../../docs/builtin-macros/debug)
-*   [Create your own custom macros](../../docs/custom-macros)
+- [Learn how macros work under the hood](../../docs/concepts)
+- [Explore all Debug options](../../docs/builtin-macros/debug)
+- [Create your own custom macros](../../docs/custom-macros)

package/docs/getting-started/installation.md

@@ -1,29 +1,30 @@
 # Installation
 
-Get started with Macroforge in just a few minutes. Install the package and configure your project to start using TypeScript macros.
+Get started with Macroforge in just a few minutes. Install the package and configure your project to
+start using TypeScript macros.
 
 ## Requirements
 
-*   Node.js 24.0 or later
-*   TypeScript 5.9 or later
+- Node.js 24.0 or later
+- TypeScript 5.9 or later
 
 ## Install the Package
 
 Install Macroforge using your preferred package manager:
 
-npm 
+npm
 
 ```
 npm install macroforge
 ```
 
-bun 
+bun
 
 ```
 bun add macroforge
 ```
 
-pnpm 
+pnpm
 
 ```
 pnpm add macroforge
@@ -31,13 +32,15 @@ pnpm add macroforge
 
 Info
 
-Macroforge includes pre-built native binaries for macOS (x64, arm64), Linux (x64, arm64), and Windows (x64, arm64).
+Macroforge includes pre-built native binaries for macOS (x64, arm64), Linux (x64, arm64), and
+Windows (x64, arm64).
 
 ## Basic Usage
 
-The simplest way to use Macroforge is with the built-in derive macros. Add a `@derive` comment decorator to your class:
+The simplest way to use Macroforge is with the built-in derive macros. Add a `@derive` comment
+decorator to your class:
 
-user.ts 
+user.ts
 
 ```
 /** @derive(Debug, Clone, PartialEq) */
@@ -61,7 +64,7 @@ class User {
 
 For the best development experience, add the TypeScript plugin to your `tsconfig.json`:
 
-tsconfig.json 
+tsconfig.json
 
 ```
 {
@@ -77,15 +80,15 @@ tsconfig.json
 
 This enables features like:
 
-*   Accurate error positions in your source code
-*   Autocompletion for generated methods
-*   Type checking for expanded code
+- Accurate error positions in your source code
+- Autocompletion for generated methods
+- Type checking for expanded code
 
 ## Build Integration (Vite)
 
 If you're using Vite, add the plugin to your config for automatic macro expansion during build:
 
-vite.config.ts 
+vite.config.ts
 
 ```
 import macroforge from "@macroforge/vite-plugin";
@@ -105,6 +108,6 @@ export default defineConfig({
 
 Now that you have Macroforge installed, learn how to use it:
 
-*   [Create your first macro](../docs/getting-started/first-macro)
-*   [Understand how macros work](../docs/concepts)
-*   [Explore built-in macros](../docs/builtin-macros)
+- [Create your first macro](../docs/getting-started/first-macro)
+- [Understand how macros work](../docs/concepts)
+- [Explore built-in macros](../docs/builtin-macros)

package/docs/integration/cli.md

@@ -2,7 +2,9 @@
 
 macroforge v0.1.48
 
-This binary provides command-line utilities for working with Macroforge TypeScript macros. It is designed for development workflows, enabling macro expansion and type checking without requiring Node.js integration.
+This binary provides command-line utilities for working with Macroforge TypeScript macros. It is
+designed for development workflows, enabling macro expansion and type checking without requiring
+Node.js integration.
 
 ## Installation
 
@@ -89,11 +91,14 @@ macroforge expand src/user.ts --builtin-only
 
 Note
 
-By default, the CLI uses Node.js for full macro support (including external macros). It must be run from your project's root directory where `macroforge` and any external macro packages are installed in `node_modules`.
+By default, the CLI uses Node.js for full macro support (including external macros). It must be run
+from your project's root directory where `macroforge` and any external macro packages are installed
+in `node_modules`.
 
 ### macroforge tsc
 
-Runs TypeScript type checking with macro expansion. This wraps `tsc --noEmit` and expands macros before type checking, so your generated methods are properly type-checked.
+Runs TypeScript type checking with macro expansion. This wraps `tsc --noEmit` and expands macros
+before type checking, so your generated methods are properly type-checked.
 
 Bash
 
@@ -220,11 +225,12 @@ done
 
 ## Built-in vs Full Mode
 
-By default, the CLI uses Node.js for full macro support including external macros. Use `--builtin-only` for faster expansion when you only need built-in macros:
+By default, the CLI uses Node.js for full macro support including external macros. Use
+`--builtin-only` for faster expansion when you only need built-in macros:
 
 | Feature         | Default (Node.js)                      | `--builtin-only` (Rust) |
 | --------------- | -------------------------------------- | ----------------------- |
 | Built-in macros | Yes                                    | Yes                     |
 | External macros | Yes                                    | No                      |
 | Performance     | Standard                               | Faster                  |
-| Dependencies    | Requires `macroforge` in node\_modules | None                    |
+| Dependencies    | Requires `macroforge` in node\_modules | None                    |

package/docs/integration/configuration.md

@@ -6,7 +6,7 @@ Macroforge can be configured with a `macroforge.json` file in your project root.
 
 Create a `macroforge.json` file:
 
-macroforge.json 
+macroforge.json
 
 ```
 {
@@ -26,15 +26,13 @@ macroforge.json
 
 ### allowNativeMacros
 
-| Type    | `boolean` |
-| Default | `true`    |
+| Type | `boolean` | | Default | `true` |
 
 Enable or disable native (Rust) macro packages. Set to `false` to only allow built-in macros.
 
 ### macroPackages
 
-| Type    | `string[]` |
-| Default | `[]`       |
+| Type | `string[]` | | Default | `[]` |
 
 List of npm packages that provide macros. Macroforge will look for macros in these packages.
 
@@ -51,8 +49,7 @@ JSON
 
 ### keepDecorators
 
-| Type    | `boolean` |
-| Default | `false`   |
+| Type | `boolean` | | Default | `false` |
 
 Keep `@derive` decorators in the output. Useful for debugging.
 
@@ -98,7 +95,8 @@ JSON
 
 Warning
 
-Be careful when increasing limits, as this could allow malicious macros to consume excessive resources.
+Be careful when increasing limits, as this could allow malicious macros to consume excessive
+resources.
 
 ## Environment Variables
 
@@ -113,4 +111,4 @@ Bash
 
 ```
 MACROFORGE_DEBUG=1 npm run dev
-```
+```

package/docs/integration/integration-overview.md

@@ -13,8 +13,8 @@ Macroforge integrates with your development workflow through IDE plugins and bui
 
 For the best development experience, use both integrations:
 
-1.  **TypeScript Plugin**: Provides real-time feedback in your IDE
-2.  **Vite Plugin**: Expands macros during development and production builds
+1. **TypeScript Plugin**: Provides real-time feedback in your IDE
+2. **Vite Plugin**: Expands macros during development and production builds
 
 Bash
 
@@ -51,6 +51,6 @@ Optimized output
 
 ## Detailed Guides
 
-*   [TypeScript Plugin setup](../docs/integration/typescript-plugin)
-*   [Vite Plugin configuration](../docs/integration/vite-plugin)
-*   [Configuration options](../docs/integration/configuration)
+- [TypeScript Plugin setup](../docs/integration/typescript-plugin)
+- [Vite Plugin configuration](../docs/integration/vite-plugin)
+- [Configuration options](../docs/integration/configuration)

package/docs/integration/mcp-server.md

@@ -1,8 +1,11 @@
 # MCP Server
 
-The MCP (Model Context Protocol) server enables AI assistants to understand and work with Macroforge macros, providing documentation lookup, code validation, and macro expansion.
+The MCP (Model Context Protocol) server enables AI assistants to understand and work with Macroforge
+macros, providing documentation lookup, code validation, and macro expansion.
 
-The local (stdio) version of the MCP server is available via the [`@macroforge/mcp-server`](https://www.npmjs.com/package/@macroforge/mcp-server) npm package. You can either install it globally and then reference it in your configuration or run it with `npx`:
+The local (stdio) version of the MCP server is available via the
+[`@macroforge/mcp-server`](https://www.npmjs.com/package/@macroforge/mcp-server) npm package. You
+can either install it globally and then reference it in your configuration or run it with `npx`:
 
 Bash
 
@@ -26,9 +29,10 @@ The `[scope]` must be `user`, `project` or `local`.
 
 ## Claude Desktop
 
-In the Settings > Developer section, click on Edit Config. It will open the folder with a `claude_desktop_config.json` file in it. Edit the file to include the following configuration:
+In the Settings > Developer section, click on Edit Config. It will open the folder with a
+`claude_desktop_config.json` file in it. Edit the file to include the following configuration:
 
-claude\_desktop\_config.json 
+claude\_desktop\_config.json
 
 ```
 {
@@ -43,9 +47,11 @@ claude\_desktop\_config.json
 
 ## Codex CLI
 
-Add the following to your `config.toml` (which defaults to `~/.codex/config.toml`, but refer to [the configuration documentation](https://github.com/openai/codex/blob/main/docs/config.md) for more advanced setups):
+Add the following to your `config.toml` (which defaults to `~/.codex/config.toml`, but refer to
+[the configuration documentation](https://github.com/openai/codex/blob/main/docs/config.md) for more
+advanced setups):
 
-config.toml 
+config.toml
 
 ```
 [mcp_servers.macroforge]
@@ -67,7 +73,8 @@ The `[scope]` must be `user`, `project` or `local`.
 
 ## Other Clients
 
-If we didn't include the MCP client you are using, refer to their documentation for `stdio` servers and use `npx` as the command and `-y @macroforge/mcp-server` as the arguments.
+If we didn't include the MCP client you are using, refer to their documentation for `stdio` servers
+and use `npx` as the command and `-y @macroforge/mcp-server` as the arguments.
 
 ## Available Tools
 
@@ -83,4 +90,6 @@ The MCP server provides five tools for AI assistants:
 
 Note
 
-For code validation and expansion features (`macroforge-autofixer`, `expand-code`, `get-macro-info`), the MCP server requires `macroforge` as a peer dependency. Install it in your project with `npm install macroforge`.
+For code validation and expansion features (`macroforge-autofixer`, `expand-code`,
+`get-macro-info`), the MCP server requires `macroforge` as a peer dependency. Install it in your
+project with `npm install macroforge`.

package/docs/integration/svelte-preprocessor.md

@@ -1,6 +1,7 @@
 # Svelte Preprocessor
 
-The Svelte preprocessor expands Macroforge macros in `<script>` blocks before Svelte compilation, enabling seamless macro usage in Svelte components.
+The Svelte preprocessor expands Macroforge macros in `<script>` blocks before Svelte compilation,
+enabling seamless macro usage in Svelte components.
 
 ## Installation
 
@@ -14,7 +15,7 @@ npm install -D @macroforge/svelte-preprocessor
 
 Add the preprocessor to your `svelte.config.js`:
 
-svelte.config.js 
+svelte.config.js
 
 ```
 import adapter from '@sveltejs/adapter-auto';
@@ -38,13 +39,14 @@ export default config;
 
 Warning
 
-Always place `macroforgePreprocess()` **before** other preprocessors like `vitePreprocess()`. This ensures macros are expanded before TypeScript compilation.
+Always place `macroforgePreprocess()` **before** other preprocessors like `vitePreprocess()`. This
+ensures macros are expanded before TypeScript compilation.
 
 ## Usage
 
 Use `@derive` decorators directly in your Svelte component scripts:
 
-UserCard.svelte 
+UserCard.svelte
 
 ```
 <script lang="ts">
@@ -91,10 +93,10 @@ macroforgePreprocess({
 
 The preprocessor:
 
-1.  Intercepts `<script lang="ts">` blocks in `.svelte` files
-2.  Checks for `@derive` decorators (skips files without them)
-3.  Expands macros using the native Macroforge binary
-4.  Returns the transformed code for Svelte compilation
+1. Intercepts `<script lang="ts">` blocks in `.svelte` files
+2. Checks for `@derive` decorators (skips files without them)
+3. Expands macros using the native Macroforge binary
+4. Returns the transformed code for Svelte compilation
 
 Tip
 
@@ -102,9 +104,10 @@ Files without `@derive` decorators are passed through unchanged with zero overhe
 
 ## SvelteKit Integration
 
-For SvelteKit projects, you can use both the preprocessor (for `.svelte` files) and the Vite plugin (for standalone `.ts` files):
+For SvelteKit projects, you can use both the preprocessor (for `.svelte` files) and the Vite plugin
+(for standalone `.ts` files):
 
-svelte.config.js 
+svelte.config.js
 
 ```
 // svelte.config.js
@@ -119,7 +122,7 @@ export default {
 };
 ```
 
-vite.config.ts 
+vite.config.ts
 
 ```
 // vite.config.ts
@@ -139,7 +142,7 @@ export default defineConfig({
 
 The preprocessor works seamlessly with Vitest for testing Svelte components:
 
-vitest.config.ts 
+vitest.config.ts
 
 ```
 // vitest.config.ts
@@ -163,7 +166,8 @@ export default defineConfig({
 
 ## Svelte 5 Runes Compatibility
 
-The preprocessor is fully compatible with Svelte 5 runes (`$state`, `$derived`, `$props`, etc.). Files using runes but without `@derive` decorators are skipped entirely.
+The preprocessor is fully compatible with Svelte 5 runes (`$state`, `$derived`, `$props`, etc.).
+Files using runes but without `@derive` decorators are skipped entirely.
 
 Svelte
 
@@ -182,4 +186,4 @@ Svelte
     }
   }
 </script>
-```
+```

package/docs/integration/typescript-plugin.md

@@ -1,6 +1,7 @@
 # TypeScript Plugin
 
-The TypeScript plugin provides IDE integration for Macroforge, including error reporting, completions, and type checking for generated code.
+The TypeScript plugin provides IDE integration for Macroforge, including error reporting,
+completions, and type checking for generated code.
 
 ## Installation
 
@@ -14,7 +15,7 @@ npm install -D @macroforge/typescript-plugin
 
 Add the plugin to your `tsconfig.json`:
 
-tsconfig.json 
+tsconfig.json
 
 ```
 {
@@ -30,17 +31,18 @@ tsconfig.json
 
 ## VS Code Setup
 
-VS Code uses its own TypeScript version by default. To use the workspace version (which includes plugins):
+VS Code uses its own TypeScript version by default. To use the workspace version (which includes
+plugins):
 
-1.  Open the Command Palette (`Cmd/Ctrl + Shift + P`)
-2.  Search for "TypeScript: Select TypeScript Version"
-3.  Choose "Use Workspace Version"
+1. Open the Command Palette (`Cmd/Ctrl + Shift + P`)
+2. Search for "TypeScript: Select TypeScript Version"
+3. Choose "Use Workspace Version"
 
 Tip
 
 Add this setting to your `.vscode/settings.json` to make it permanent:
 
-.vscode/settings.json 
+.vscode/settings.json
 
 ```
 {
@@ -90,13 +92,13 @@ const copy = user.clone();
 
 ### Plugin Not Loading
 
-1.  Ensure you're using the workspace TypeScript version
-2.  Restart the TypeScript server (Command Palette → "TypeScript: Restart TS Server")
-3.  Check that the plugin is listed in `tsconfig.json`
+1. Ensure you're using the workspace TypeScript version
+2. Restart the TypeScript server (Command Palette → "TypeScript: Restart TS Server")
+3. Check that the plugin is listed in `tsconfig.json`
 
 ### Errors Not Showing
 
 If errors from macros aren't appearing:
 
-1.  Make sure the Vite plugin is also installed (for source file watching)
-2.  Check that your file is saved (plugins process on save)
+1. Make sure the Vite plugin is also installed (for source file watching)
+2. Check that your file is saved (plugins process on save)

package/docs/integration/vite-plugin.md

@@ -1,6 +1,7 @@
 # Vite Plugin
 
-The Vite plugin provides build-time macro expansion, transforming your code during development and production builds.
+The Vite plugin provides build-time macro expansion, transforming your code during development and
+production builds.
 
 ## Installation
 
@@ -14,7 +15,7 @@ npm install -D @macroforge/vite-plugin
 
 Add the plugin to your `vite.config.ts`:
 
-vite.config.ts 
+vite.config.ts
 
 ```
 import macroforge from "@macroforge/vite-plugin";
@@ -64,7 +65,7 @@ macroforge({
 
 ### React (Vite)
 
-vite.config.ts 
+vite.config.ts
 
 ```
 import macroforge from "@macroforge/vite-plugin";
@@ -81,7 +82,7 @@ export default defineConfig({
 
 ### SvelteKit
 
-vite.config.ts 
+vite.config.ts
 
 ```
 import macroforge from "@macroforge/vite-plugin";
@@ -98,20 +99,21 @@ export default defineConfig({
 
 Note
 
-Always place the Macroforge plugin before other framework plugins to ensure macros are expanded first.
+Always place the Macroforge plugin before other framework plugins to ensure macros are expanded
+first.
 
 ## Development Server
 
 During development, the plugin:
 
-*   Watches for file changes
-*   Expands macros on save
-*   Provides HMR support for expanded code
+- Watches for file changes
+- Expands macros on save
+- Provides HMR support for expanded code
 
 ## Production Build
 
 During production builds, the plugin:
 
-*   Expands all macros in the source files
-*   Generates type declaration files
-*   Strips `@derive` decorators from output
+- Expands all macros in the source files
+- Generates type declaration files
+- Strips `@derive` decorators from output