Macroforge MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-sectionsA | Lists all Macroforge documentation sections. Returns sections with:
WORKFLOW:
Example use_cases: "setup, install", "serialization, json", "validation, email" |
| get-documentationA | Retrieves full documentation content for Macroforge sections. Supports flexible search by:
Can accept a single section name or an array of sections. After calling list-sections, analyze the use_cases and fetch ALL relevant sections at once. |
| macroforge-autofixerA | Validates TypeScript code with @derive decorators using Macroforge's native validation. Returns structured JSON diagnostics with:
This tool MUST be used before sending Macroforge code to the user. If require_another_tool_call_after_fixing is true, fix the issues and validate again. Detects:
|
| expand-codeA | Expands Macroforge macros in TypeScript code and returns the transformed result. Shows:
Useful for:
|
| get-macro-infoA | Get documentation for Macroforge macros and decorators. Returns information about:
Use without parameters to get the full manifest of all available macros and decorators. Use with a name parameter to get info for a specific macro or decorator. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: expand-code transforms TypeScript code, get-documentation retrieves documentation content, get-macro-info provides macro/decorator details, list-sections lists documentation sections, and macroforge-autofixer validates code. The descriptions clearly differentiate their functions, making misselection unlikely.
The naming is mostly consistent with a verb_noun pattern (expand-code, get-documentation, get-macro-info, list-sections), but macroforge-autofixer deviates slightly by using a compound noun prefix instead of a verb. This minor inconsistency doesn't significantly hinder readability or predictability.
With 5 tools, this server is well-scoped for its purpose of Macroforge macro handling and documentation. Each tool earns its place by covering distinct aspects like code expansion, documentation retrieval, macro info, section listing, and validation, providing a complete workflow without being overly sparse or bloated.
The tool set offers complete coverage for the Macroforge domain: expand-code handles code transformation, get-documentation and get-macro-info cover documentation needs, list-sections supports discovery, and macroforge-autofixer ensures validation. This covers the full lifecycle from setup and usage to debugging and validation, with no obvious gaps.