@iress-oss/ids-mcp-server 0.0.1 → 5.14.2

package/LICENSE.txt

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1.  Definitions.
+
+    "License" shall mean the terms and conditions for use, reproduction,
+    and distribution as defined by Sections 1 through 9 of this document.
+
+    "Licensor" shall mean the copyright owner or entity authorized by
+    the copyright owner that is granting the License.
+
+    "Legal Entity" shall mean the union of the acting entity and all
+    other entities that control, are controlled by, or are under common
+    control with that entity. For the purposes of this definition,
+    "control" means (i) the power, direct or indirect, to cause the
+    direction or management of such entity, whether by contract or
+    otherwise, or (ii) ownership of fifty percent (50%) or more of the
+    outstanding shares, or (iii) beneficial ownership of such entity.
+
+    "You" (or "Your") shall mean an individual or Legal Entity
+    exercising permissions granted by this License.
+
+    "Source" form shall mean the preferred form for making modifications,
+    including but not limited to software source code, documentation
+    source, and configuration files.
+
+    "Object" form shall mean any form resulting from mechanical
+    transformation or translation of a Source form, including but
+    not limited to compiled object code, generated documentation,
+    and conversions to other media types.
+
+    "Work" shall mean the work of authorship, whether in Source or
+    Object form, made available under the License, as indicated by a
+    copyright notice that is included in or attached to the work
+    (an example is provided in the Appendix below).
+
+    "Derivative Works" shall mean any work, whether in Source or Object
+    form, that is based on (or derived from) the Work and for which the
+    editorial revisions, annotations, elaborations, or other modifications
+    represent, as a whole, an original work of authorship. For the purposes
+    of this License, Derivative Works shall not include works that remain
+    separable from, or merely link (or bind by name) to the interfaces of,
+    the Work and Derivative Works thereof.
+
+    "Contribution" shall mean any work of authorship, including
+    the original version of the Work and any modifications or additions
+    to that Work or Derivative Works thereof, that is intentionally
+    submitted to Licensor for inclusion in the Work by the copyright owner
+    or by an individual or Legal Entity authorized to submit on behalf of
+    the copyright owner. For the purposes of this definition, "submitted"
+    means any form of electronic, verbal, or written communication sent
+    to the Licensor or its representatives, including but not limited to
+    communication on electronic mailing lists, source code control systems,
+    and issue tracking systems that are managed by, or on behalf of, the
+    Licensor for the purpose of discussing and improving the Work, but
+    excluding communication that is conspicuously marked or otherwise
+    designated in writing by the copyright owner as "Not a Contribution."
+
+    "Contributor" shall mean Licensor and any individual or Legal Entity
+    on behalf of whom a Contribution has been received by Licensor and
+    subsequently incorporated within the Work.
+
+2.  Grant of Copyright License. Subject to the terms and conditions of
+    this License, each Contributor hereby grants to You a perpetual,
+    worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+    copyright license to reproduce, prepare Derivative Works of,
+    publicly display, publicly perform, sublicense, and distribute the
+    Work and such Derivative Works in Source or Object form.
+
+3.  Grant of Patent License. Subject to the terms and conditions of
+    this License, each Contributor hereby grants to You a perpetual,
+    worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+    (except as stated in this section) patent license to make, have made,
+    use, offer to sell, sell, import, and otherwise transfer the Work,
+    where such license applies only to those patent claims licensable
+    by such Contributor that are necessarily infringed by their
+    Contribution(s) alone or by combination of their Contribution(s)
+    with the Work to which such Contribution(s) was submitted. If You
+    institute patent litigation against any entity (including a
+    cross-claim or counterclaim in a lawsuit) alleging that the Work
+    or a Contribution incorporated within the Work constitutes direct
+    or contributory patent infringement, then any patent licenses
+    granted to You under this License for that Work shall terminate
+    as of the date such litigation is filed.
+
+4.  Redistribution. You may reproduce and distribute copies of the
+    Work or Derivative Works thereof in any medium, with or without
+    modifications, and in Source or Object form, provided that You
+    meet the following conditions:
+
+    (a) You must give any other recipients of the Work or
+    Derivative Works a copy of this License; and
+
+    (b) You must cause any modified files to carry prominent notices
+    stating that You changed the files; and
+
+    (c) You must retain, in the Source form of any Derivative Works
+    that You distribute, all copyright, patent, trademark, and
+    attribution notices from the Source form of the Work,
+    excluding those notices that do not pertain to any part of
+    the Derivative Works; and
+
+    (d) If the Work includes a "NOTICE" text file as part of its
+    distribution, then any Derivative Works that You distribute must
+    include a readable copy of the attribution notices contained
+    within such NOTICE file, excluding those notices that do not
+    pertain to any part of the Derivative Works, in at least one
+    of the following places: within a NOTICE text file distributed
+    as part of the Derivative Works; within the Source form or
+    documentation, if provided along with the Derivative Works; or,
+    within a display generated by the Derivative Works, if and
+    wherever such third-party notices normally appear. The contents
+    of the NOTICE file are for informational purposes only and
+    do not modify the License. You may add Your own attribution
+    notices within Derivative Works that You distribute, alongside
+    or as an addendum to the NOTICE text from the Work, provided
+    that such additional attribution notices cannot be construed
+    as modifying the License.
+
+    You may add Your own copyright statement to Your modifications and
+    may provide additional or different license terms and conditions
+    for use, reproduction, or distribution of Your modifications, or
+    for any such Derivative Works as a whole, provided Your use,
+    reproduction, and distribution of the Work otherwise complies with
+    the conditions stated in this License.
+
+5.  Submission of Contributions. Unless You explicitly state otherwise,
+    any Contribution intentionally submitted for inclusion in the Work
+    by You to the Licensor shall be under the terms and conditions of
+    this License, without any additional terms or conditions.
+    Notwithstanding the above, nothing herein shall supersede or modify
+    the terms of any separate license agreement you may have executed
+    with Licensor regarding such Contributions.
+
+6.  Trademarks. This License does not grant permission to use the trade
+    names, trademarks, service marks, or product names of the Licensor,
+    except as required for reasonable and customary use in describing the
+    origin of the Work and reproducing the content of the NOTICE file.
+
+7.  Disclaimer of Warranty. Unless required by applicable law or
+    agreed to in writing, Licensor provides the Work (and each
+    Contributor provides its Contributions) on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+    implied, including, without limitation, any warranties or conditions
+    of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+    PARTICULAR PURPOSE. You are solely responsible for determining the
+    appropriateness of using or redistributing the Work and assume any
+    risks associated with Your exercise of permissions under this License.
+
+8.  Limitation of Liability. In no event and under no legal theory,
+    whether in tort (including negligence), contract, or otherwise,
+    unless required by applicable law (such as deliberate and grossly
+    negligent acts) or agreed to in writing, shall any Contributor be
+    liable to You for damages, including any direct, indirect, special,
+    incidental, or consequential damages of any character arising as a
+    result of this License or out of the use or inability to use the
+    Work (including but not limited to damages for loss of goodwill,
+    work stoppage, computer failure or malfunction, or any and all
+    other commercial damages or losses), even if such Contributor
+    has been advised of the possibility of such damages.
+
+9.  Accepting Warranty or Additional Liability. While redistributing
+    the Work or Derivative Works thereof, You may choose to offer,
+    and charge a fee for, acceptance of support, warranty, indemnity,
+    or other liability obligations and/or rights consistent with this
+    License. However, in accepting such obligations, You may act only
+    on Your own behalf and on Your sole responsibility, not on behalf
+    of any other Contributor, and only if You agree to indemnify,
+    defend, and hold each Contributor harmless for any liability
+    incurred by, or claims asserted against, such Contributor by reason
+    of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/README.md

@@ -14,92 +14,45 @@ A Model Context Protocol (MCP) server specifically designed for the **Iress Desi
 
 ## Installation
 
-1. Clone or download this repository
-2. Install dependencies:
-   ```bash
-   yarn install
-   ```
-3. Build the project:
-   ```bash
-   yarn build
-   ```
+### Quick Setup (VS Code)
 
-## Usage
+**🚀 One-Click Installation**: Click the link below to automatically add the IDS MCP server to your VS Code settings:
 
-### Development Server
+[**Add IDS MCP Server to VS Code**](vscode:mcp/install?%7B%22name%22%3A%22iress-design-system%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22%40iress-oss%2Fids-mcp-server%22%5D%7D)
 
-For easy testing during development, use the interactive dev server:
+This will automatically configure VS Code to use the IDS Component Library MCP Server with your AI assistant.
 
-```bash
-yarn dev-server
-```
+### Manual Setup (VS Code)
 
-This starts an interactive shell where you can test MCP commands and shows detailed connection information:
+Alternatively, you can manually add the server to your VS Code settings:
 
-```
-🚀 IDS Component Library MCP Server
-===================================
-
-📍 Server Configuration:
-   Protocol: stdio (Model Context Protocol)
-   Server Path: /Users/luke.peary/Sandbox/ids-mcp-server/build/index.js
-   Docs Directory: /Users/luke.peary/Sandbox/ids-mcp-server/docs/ids
-   Working Directory: /Users/luke.peary/Sandbox/ids-mcp-server
-
-🔌 Starting MCP server...
-✅ MCP server is ready!
-📡 Connection: stdio transport established
-🔗 MCP Client Config:
-   {
-     "command": "node",
-     "args": ["/Users/luke.peary/Sandbox/ids-mcp-server/build/index.js"],
-     "cwd": "/Users/luke.peary/Sandbox/ids-mcp-server"
-   }
-
-Available commands:
-  find-component <name>     - Find IDS components by name or functionality
-  get-props <component>     - Get component props and API details
-  get-examples <component>  - Get usage examples and patterns
-  search-ids <query>        - Search across all IDS documentation
-  list-components [category] - List available components
-  get-tokens [type]         - Get design tokens (colors, spacing, etc.)
-  list-resources           - List available resources
-  help                     - Show this help
-  exit                     - Exit the dev server
-
-> find-component button
-📤 Request: {"jsonrpc":"2.0","id":123,"method":"tools/call","params":{"name":"find_component","arguments":{"query":"button"}}}
-📥 Response: {
-  "result": {
-    "content": [
-      {
-        "type": "text",
-        "text": "Found 3 relevant IDS components:\n\n1. **components-button-docs.md**\n   button: A button is a clickable item used to perform an action.\n\n2. **components-buttongroup-docs.md**\n   buttongroup: Button group component documentation..."
-      }
-    ]
+1. Open VS Code Settings (⌘/Ctrl + ,)
+2. Search for "MCP"
+3. Add the following server configuration:
+
+```json
+"mcp": {
+  "servers": {
+    "iress-design-system": {
+      "command": "npx",
+      "args": ["@iress-oss/ids-mcp-server"]
+    }
   }
 }
 ```
 
-#### Common Dev Server Commands
-
-- `find-component button` - Find button-related components
-- `get-props button` - Get IressButton component props and API
-- `get-examples input` - Get IressInput usage examples
-- `search-ids "mode=primary"` - Search for primary mode usage
-- `list-components components` - List all UI components
-- `get-tokens colors` - Get IDS color design tokens
-- `raw {"jsonrpc":"2.0","id":1,"method":"tools/list"}` - Send custom MCP request
+### Other MCP Clients
 
-### Running the Server
+For other MCP clients or manual configuration, use this server configuration:
 
-The server runs on stdio and communicates using the MCP protocol:
-
-```bash
-node build/index.js
+```json
+{
+  "command": "npx",
+  "args": ["@iress-oss/ids-mcp-server"]
+}
 ```
 
-### Available Tools
+## Available Tools
 
 1. **find_component**: Find IDS components by name or functionality - perfect for component discovery
 2. **get_component_props**: Get detailed prop information and API reference for specific components
@@ -108,7 +61,7 @@ node build/index.js
 5. **list_components**: List all available components organized by category
 6. **get_design_tokens**: Access IDS design tokens (colors, spacing, typography, etc.)
 
-### Available Resources
+## Available Resources
 
 All IDS component documentation files are exposed as categorized resources:
 
@@ -116,45 +69,9 @@ All IDS component documentation files are exposed as categorized resources:
 - **Foundations**: Colors, Typography, Spacing, etc. (`foundations-*-docs.md`)
 - **Resources**: Changelog, Guidelines, etc. (`resources-*-docs.md`)
 
-Resources have URIs like: `file:///absolute/path/to/docs/ids/components-button-docs.md`
-
-## Example Usage
-
-### With MCP Client
-
-```bash
-# List available IDS tools
-echo '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | node build/index.js
-
-# Find button components
-echo '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"find_component","arguments":{"query":"button"}}}' | node build/index.js
-
-# Get IressButton props
-echo '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"get_component_props","arguments":{"component":"button"}}}' | node build/index.js
-
-# Search for primary mode usage
-echo '{"jsonrpc":"2.0","id":4,"method":"tools/call","params":{"name":"search_ids_docs","arguments":{"query":"mode=\"primary\""}}}' | node build/index.js
-```
-
-### Configuration for MCP Clients
-
-Add this to your MCP client configuration:
-
-```json
-{
-  "mcpServers": {
-    "ids-component-library": {
-      "command": "node",
-      "args": ["/path/to/ids-mcp-server/build/index.js"],
-      "cwd": "/path/to/ids-mcp-server"
-    }
-  }
-}
-```
-
 ## Documentation Structure
 
-The server works with the IDS component library documentation in the `docs/ids/` directory:
+The server works with the IDS component library documentation in the `generated/docs/` directory:
 
 **Components** (50+ UI components):
 
@@ -164,60 +81,13 @@ The server works with the IDS component library documentation in the `docs/ids/`
 - `components-modal-docs.md` - IressModal component
 - `components-*-recipes-docs.md` - Usage patterns and recipes
 
-**Foundations** (Design system basics):
+**Foundations** (Guidelines and tokens):
 
 - `foundations-colours-docs.md` - Color palette and usage
 - `foundations-typography-docs.md` - Text styles and hierarchy
 - `foundations-spacing-docs.md` - Layout and spacing tokens
 
-**Resources** (Guidelines and tools):
+**Resources** (Supporting documentation):
 
 - `resources-changelog-docs.md` - Version history and updates
 - `introduction-docs.md` - Getting started guide
-
-## Development
-
-### Project Structure
-
-```
-├── src/
-│   └── index.ts          # IDS MCP server implementation
-├── docs/
-│   └── ids/              # IDS component library documentation
-│       ├── components-*-docs.md     # Component documentation
-│       ├── foundations-*-docs.md    # Design tokens and foundations
-│       └── resources-*-docs.md      # Guidelines and resources
-├── build/                # Compiled JavaScript output
-├── package.json
-├── tsconfig.json
-└── README.md
-```
-
-### Adding Documentation
-
-The server automatically discovers all `.md` files in the `docs/ids/` directory. To add new IDS component documentation:
-
-1. Add new component docs as `components-{name}-docs.md`
-2. Add foundation docs as `foundations-{name}-docs.md`
-3. Add resource docs as `resources-{name}-docs.md`
-
-The server will automatically categorize and expose them through the MCP protocol.
-
-### Customization
-
-To use a different documentation directory, modify the `DOCS_DIR` constant in `src/index.ts`:
-
-```typescript
-const DOCS_DIR = path.join(__dirname, "..", "docs", "your-docs-folder");
-```
-
-## Security
-
-- Files are restricted to the configured docs directory
-- Path traversal attacks are prevented
-- Only `.md` files are processed
-- All input parameters are validated
-
-## License
-
-[Your License Here]

package/dist/componentHandlers.js

@@ -0,0 +1,241 @@
+/**
+ * Tool handlers for component-related operations
+ */
+import { z } from 'zod';
+import * as path from 'path';
+import { getMarkdownFiles, mapIressComponentToFile, extractIressComponents, readFileContent, } from './utils.js';
+import { DOCS_DIR } from './config.js';
+function checkIressComponentMatch(query) {
+    if (query.startsWith('Iress')) {
+        const componentFile = mapIressComponentToFile(query);
+        if (componentFile) {
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Found exact match for **${query}**:\n\n**${componentFile}**\n   ${query} component documentation\n\n*Use \`get_iress_component_info\` with "${query}" for detailed information.*`,
+                    },
+                ],
+            };
+        }
+    }
+    return null;
+}
+function calculateRelevanceScore(file, content, query, lines) {
+    let relevanceScore = 0;
+    const queryLower = query.toLowerCase();
+    const filenameLower = file.toLowerCase();
+    // Check for Iress component mentions in content
+    const iressComponents = extractIressComponents(content);
+    const hasMatchingIressComponent = iressComponents.some((comp) => comp.toLowerCase().includes(queryLower) ||
+        queryLower.includes(comp.toLowerCase().replace('iress', '')));
+    if (hasMatchingIressComponent) {
+        relevanceScore += 75;
+    }
+    // High relevance for filename matches
+    if (filenameLower.includes(queryLower)) {
+        relevanceScore += 100;
+    }
+    // Medium relevance for title matches
+    const title = lines.find((line) => line.startsWith('#'))?.replace(/^#+\s*/, '') ?? '';
+    if (title.toLowerCase().includes(queryLower)) {
+        relevanceScore += 50;
+    }
+    // Lower relevance for content matches
+    const contentMatches = content.toLowerCase().split(queryLower).length - 1;
+    relevanceScore += contentMatches * 2;
+    return relevanceScore;
+}
+function createSearchResult(file, relevanceScore, lines) {
+    const componentName = file
+        .replace(/^components-/, '')
+        .replace('-docs.md', '');
+    const description = lines
+        .slice(0, 10)
+        .find((line) => line.trim() && !line.startsWith('#') && !line.startsWith('<!--'))
+        ?.trim() ?? 'IDS component documentation';
+    return {
+        file,
+        relevance: relevanceScore,
+        description: `${componentName}: ${description}`,
+    };
+}
+export function handleFindComponent(args) {
+    const schema = z.object({
+        query: z.string(),
+        category: z.enum(['components', 'foundations', 'resources']).optional(),
+    });
+    const { query, category } = schema.parse(args);
+    // Check if query is an Iress component name
+    const iressMatch = checkIressComponentMatch(query);
+    if (iressMatch) {
+        return iressMatch;
+    }
+    const markdownFiles = getMarkdownFiles();
+    // Filter files by category if specified
+    const filteredFiles = category
+        ? markdownFiles.filter((file) => file.startsWith(`${category}-`))
+        : markdownFiles;
+    const results = [];
+    for (const file of filteredFiles) {
+        try {
+            const filePath = path.join(DOCS_DIR, file);
+            const content = readFileContent(filePath);
+            const lines = content.split('\n');
+            const relevanceScore = calculateRelevanceScore(file, content, query, lines);
+            if (relevanceScore > 0) {
+                results.push(createSearchResult(file, relevanceScore, lines));
+            }
+        }
+        catch (error) {
+            console.error(`Error reading file ${file}:`, error);
+        }
+    }
+    // Sort by relevance
+    results.sort((a, b) => b.relevance - a.relevance);
+    return {
+        content: [
+            {
+                type: 'text',
+                text: results.length > 0
+                    ? `Found ${results.length} relevant IDS components:\n\n${results
+                        .slice(0, 10) // Limit to top 10 results
+                        .map((r, index) => `${index + 1}. **${r.file}**\n   ${r.description}`)
+                        .join('\n\n')}`
+                    : `No IDS components found matching "${query}". Try searching for common component names like "button", "input", "table", or "modal".`,
+            },
+        ],
+    };
+}
+function findComponentFile(component, markdownFiles) {
+    return markdownFiles.find((file) => file.includes(`components-${component.toLowerCase()}`) ||
+        file.toLowerCase().includes(component.toLowerCase()));
+}
+function formatAvailableComponents(markdownFiles) {
+    return markdownFiles
+        .filter((f) => f.startsWith('components-'))
+        .map((f) => `- ${f.replace('components-', '').replace('-docs.md', '')}`)
+        .join('\n');
+}
+function isPropsRelatedLine(line) {
+    return (line.includes('mode') ||
+        line.includes('prop') ||
+        line.includes('Properties') ||
+        line.includes('API') ||
+        line.includes('Examples'));
+}
+function extractPropSections(content) {
+    const lines = content.split('\n');
+    const propSections = [];
+    let inPropsSection = false;
+    let currentSection = '';
+    for (const line of lines) {
+        if (isPropsRelatedLine(line)) {
+            if (currentSection) {
+                propSections.push(currentSection);
+            }
+            currentSection = line + '\n';
+            inPropsSection = true;
+        }
+        else if (inPropsSection && line.trim()) {
+            currentSection += line + '\n';
+        }
+        else if (inPropsSection && !line.trim()) {
+            if (currentSection) {
+                propSections.push(currentSection);
+                currentSection = '';
+            }
+            inPropsSection = false;
+        }
+    }
+    if (currentSection) {
+        propSections.push(currentSection);
+    }
+    return propSections;
+}
+function formatPropsResponse(propSections, content, componentFile) {
+    return propSections.length > 0
+        ? propSections.join('\n---\n\n')
+        : `Props information extracted from ${componentFile}:\n\n${content.slice(0, 2000)}...`;
+}
+export function handleGetComponentProps(args) {
+    const schema = z.object({
+        component: z.string(),
+    });
+    const { component } = schema.parse(args);
+    const markdownFiles = getMarkdownFiles();
+    const componentFile = findComponentFile(component, markdownFiles);
+    if (!componentFile) {
+        return {
+            content: [
+                {
+                    type: 'text',
+                    text: `Component "${component}" not found. Available components:\n${formatAvailableComponents(markdownFiles)}`,
+                },
+            ],
+        };
+    }
+    try {
+        const filePath = path.join(DOCS_DIR, componentFile);
+        const content = readFileContent(filePath);
+        const propSections = extractPropSections(content);
+        return {
+            content: [
+                {
+                    type: 'text',
+                    text: `**${component} Component Props & API**\n\n${formatPropsResponse(propSections, content, componentFile)}`,
+                },
+            ],
+        };
+    }
+    catch (error) {
+        throw new Error(`Failed to read component file ${componentFile}: ${error instanceof Error ? error.message : String(error)}`);
+    }
+}
+export function handleListComponents(args) {
+    const schema = z.object({
+        category: z
+            .enum(['components', 'foundations', 'resources', 'all'])
+            .default('all'),
+    });
+    const { category } = schema.parse(args);
+    const markdownFiles = getMarkdownFiles();
+    const categorized = {
+        components: markdownFiles
+            .filter((f) => f.startsWith('components-'))
+            .map((f) => f.replace('components-', '').replace('-docs.md', '')),
+        foundations: markdownFiles
+            .filter((f) => f.startsWith('foundations-'))
+            .map((f) => f.replace('foundations-', '').replace('-docs.md', '')),
+        resources: markdownFiles
+            .filter((f) => f.startsWith('resources-'))
+            .map((f) => f.replace('resources-', '').replace('-docs.md', '')),
+    };
+    let output = '**IDS Component Library**\n\n';
+    if (category === 'all') {
+        const componentsList = categorized.components
+            .map((c) => `- ${c}`)
+            .join('\n');
+        const foundationsList = categorized.foundations
+            .map((c) => `- ${c}`)
+            .join('\n');
+        const resourcesList = categorized.resources.map((c) => `- ${c}`).join('\n');
+        output += `**Components (${categorized.components.length})**\n${componentsList}\n\n`;
+        output += `**Foundations (${categorized.foundations.length})**\n${foundationsList}\n\n`;
+        output += `**Resources (${categorized.resources.length})**\n${resourcesList}`;
+    }
+    else {
+        const items = categorized[category];
+        const itemsList = items.map((c) => `- ${c}`).join('\n');
+        const categoryTitle = category.charAt(0).toUpperCase() + category.slice(1);
+        output += `**${categoryTitle} (${items.length})**\n${itemsList}`;
+    }
+    return {
+        content: [
+            {
+                type: 'text',
+                text: output,
+            },
+        ],
+    };
+}