awslabs.frontend-mcp-server 0.0.1__py3-none-any.whl

awslabs/__init__.py

@@ -0,0 +1,13 @@
+# Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
+#
+# Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance
+# with the License. A copy of the License is located at
+#
+#    http://www.apache.org/licenses/LICENSE-2.0
+#
+# or in the 'license' file accompanying this file. This file is distributed on an 'AS IS' BASIS, WITHOUT WARRANTIES
+# OR CONDITIONS OF ANY KIND, express or implied. See the License for the specific language governing permissions
+# and limitations under the License.
+
+# This file is part of the awslabs namespace.
+# It is intentionally minimal to support PEP 420 namespace packages.

awslabs/frontend_mcp_server/__init__.py

@@ -0,0 +1,14 @@
+# Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
+#
+# Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance
+# with the License. A copy of the License is located at
+#
+#    http://www.apache.org/licenses/LICENSE-2.0
+#
+# or in the 'license' file accompanying this file. This file is distributed on an 'AS IS' BASIS, WITHOUT WARRANTIES
+# OR CONDITIONS OF ANY KIND, express or implied. See the License for the specific language governing permissions
+# and limitations under the License.
+
+"""awslabs.frontend-mcp-server"""
+
+__version__ = '0.0.0'

awslabs/frontend_mcp_server/server.py

@@ -0,0 +1,90 @@
+# Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
+#
+# Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance
+# with the License. A copy of the License is located at
+#
+#    http://www.apache.org/licenses/LICENSE-2.0
+#
+# or in the 'license' file accompanying this file. This file is distributed on an 'AS IS' BASIS, WITHOUT WARRANTIES
+# OR CONDITIONS OF ANY KIND, express or implied. See the License for the specific language governing permissions
+# and limitations under the License.
+
+"""awslabs frontend MCP Server implementation."""
+
+import argparse
+from awslabs.frontend_mcp_server.utils.file_utils import load_markdown_file
+from loguru import logger
+from mcp.server.fastmcp import FastMCP
+from pydantic import Field
+from typing import Literal
+
+
+mcp = FastMCP(
+    'awslabs.frontend-mcp-server',
+    instructions='The Frontend MCP Server provides specialized tools for modern web application development. It offers guidance on React application setup, optimistic UI implementation, and authentication integration. Use these tools when you need expert advice on frontend development best practices.',
+    dependencies=[
+        'pydantic',
+        'loguru',
+    ],
+)
+
+
+@mcp.tool(name='GetReactDocsByTopic')
+async def get_react_docs_by_topic(
+    topic: Literal[
+        'essential-knowledge',
+        'troubleshooting',
+    ] = Field(
+        ...,
+        description='The topic of React documentation to retrieve. Topics include: essential-knowledge, troubleshooting, basic-ui, authentication, routing, customizing, creating-components.',
+    ),
+) -> str:
+    """Get specific AWS web application UI setup documentation by topic.
+
+    Parameters:
+        topic: The topic of React documentation to retrieve.
+          - "essential-knowledge": Essential knowledge for working with React applications.
+          - "troubleshooting": Common issues and solutions when generating code.
+
+    Returns:
+        A markdown string containing the requested documentation
+    """
+    match topic:
+        case 'essential-knowledge':
+            return load_markdown_file('essential-knowledge.md')
+        case 'troubleshooting':
+            return load_markdown_file('troubleshooting.md')
+        case _:
+            raise ValueError(
+                f'Invalid topic: {topic}. Must be one of: essential-knowledge, basic-ui, authentication, routing, customizing, creating-components'
+            )
+
+
+def main():
+    """Run the MCP server with CLI argument support."""
+    parser = argparse.ArgumentParser(
+        description='An AWS Labs Model Context Protocol (MCP) server for frontend'
+    )
+    parser.add_argument('--sse', action='store_true', help='Use SSE transport')
+    parser.add_argument('--port', type=int, default=8888, help='Port to run the server on')
+
+    args = parser.parse_args()
+
+    logger.trace('A trace message.')
+    logger.debug('A debug message.')
+    logger.info('An info message.')
+    logger.success('A success message.')
+    logger.warning('A warning message.')
+    logger.error('An error message.')
+    logger.critical('A critical message.')
+
+    # Run server with appropriate transport
+    if args.sse:
+        mcp.settings.port = args.port
+        mcp.run(transport='sse')
+    else:
+        mcp.run()
+
+
+if __name__ == '__main__':
+    main()

awslabs/frontend_mcp_server/static/react/essential-knowledge.md

@@ -0,0 +1,251 @@
+# Web application development instructions
+
+## Introduction
+This document provides instructions to create a custom web applications based on a frontend starter template. The template uses React, Tailwind CSS, React Router v7, shadcn UI components, AWS Amplify, and Zustand for state management. You should use this information to analyze user requirements, suggest appropriate approaches, and provide implementation steps for customizing the reference template to meet their specific needs. Follow the structured approach outlined below to deliver high-quality applications efficiently while maintaining consistency with the existing architecture and best practices.
+
+## Important
+- Authentication, basic routing, and private/public layouts are already implemented
+- Sample dashboard and settings pages exist as reference
+- AWS backend integration will be handled separately
+- If you run into issues, you MUST seek guidance from the AWSLabs Frontend MCP server under the "Troubleshooting" topic.
+
+## Project Implementation Flow
+
+### 0. Requirements Analysis
+- Generate a modern app name and description
+- Identify the primary color for the app if provided by the user, if not use shadcn defaults (usually #171717)
+- Identify target users and primary purpose
+- List and prioritize core features
+- Map features to existing template structure
+- Identify new pages and components needed
+- Reuse the current authentication layouts and flow
+- Reuse the current private page layout, with the application sidebar on the left and page content on the right
+- Always include a dashboard page as the start page, and incorporate charts and lists based on the functional needs of the application
+- Incorporate an AI Chat assistant to the application if helpful
+- Make the UI design contemporary, clean and minimal.
+
+### 1. Document your plan
+
+Once you have completed your analysis, you MUST create a CHECKLIST.md in the root folder of the project with two clearly defined sections:
+
+**Section 1: Application Analysis**
+- Application name and description
+- Target users and primary purpose
+- Core features (prioritized list)
+  - Be specific and detailed for each feature
+  - Include success criteria for each feature
+  - Identify which features require backend integration
+- Complete page list with brief descriptions for each page
+  - Detail EVERY page needed for the application
+  - Include purpose, key components, and data needs for each page
+  - Map pages to features they support
+- Data models/entities needed
+- UI components required for implementation
+  - List shadcn components to be used for each page
+  - Identify any custom components needed
+
+**Example: Task Tracking App**
+```markdown
+# TaskFlow Application Analysis
+
+## Application Overview
+- **Name**: TaskFlow
+- **Description**: A collaborative task tracking application for small teams
+- **Target Users**: Small teams (5-15 people), project managers, freelancers
+- **Primary Purpose**: Simplify task management and improve team coordination
+
+## Core Features (Prioritized)
+1. **Task Management**
+   - Create, edit, delete tasks with title, description, due date, priority
+   - Assign tasks to team members
+   - Success criteria: Users can perform all CRUD operations on tasks
+   - Backend integration: Required for persistent storage
+
+2. **Task Board Views**
+   - Kanban board with customizable columns (Todo, In Progress, Done)
+   - List view with sorting and filtering options
+   - Success criteria: Users can switch between views and drag-drop tasks
+   - Backend integration: Required for state persistence
+
+3. **Team Collaboration**
+   - Comment on tasks
+   - @mention team members
+   - Success criteria: Users receive notifications when mentioned
+   - Backend integration: Required for notifications
+
+## Page List
+1. **Dashboard**
+   - Purpose: Overview of tasks, recent activity, and team performance
+   - Components: Task summary cards, activity feed, progress charts
+   - Data: Task counts by status, recent activities, completion rates
+
+2. **Task Board**
+   - Purpose: Visual kanban-style task management
+   - Components: Drag-drop columns, task cards, filtering controls
+   - Data: All tasks with status, assignee, priority information
+
+3. **Task Details**
+   - Purpose: View and edit detailed task information
+   - Components: Form fields, comments section, activity log
+   - Data: Single task with full details and comment history
+
+4. **Team Members**
+   - Purpose: Manage team members and view their tasks
+   - Components: User list, user profile cards, assigned tasks
+   - Data: User profiles and task assignments
+
+5. **Settings**
+   - Purpose: Configure application preferences
+   - Components: Form fields for notification settings, theme options
+   - Data: User preferences
+
+## Data Models
+1. **Task**
+   - id, title, description, status, priority, dueDate, assigneeId, createdAt
+
+2. **User**
+   - id, name, email, avatar, role
+
+3. **Comment**
+   - id, taskId, userId, content, createdAt
+
+## UI Components
+1. **Dashboard Page**
+   - shadcn: Card, Tabs, Avatar, Button, Select
+   - Custom: TaskSummaryCard, ActivityFeed
+
+2. **Task Board Page**
+   - shadcn: Card, Badge, Avatar, Button, DropdownMenu
+   - Custom: DraggableTaskCard, KanbanColumn
+
+3. **Task Details Page**
+   - shadcn: Form, Input, Textarea, Select, Button, Tabs, ScrollArea
+   - Custom: CommentThread, TaskActivityLog
+
+4. **Team Members Page**
+   - shadcn: Card, Avatar, Table, Dialog, Badge
+   - Custom: UserProfileCard, TaskAssignmentList
+
+5. **Settings Page**
+   - shadcn: Form, Switch, RadioGroup, Separator, Button
+   - Custom: NotificationPreferences
+```
+
+**Section 2: Implementation Checklist**
+- [ ] Generate a modern app name/description and a project folder name [app-name] based on the app name
+- [ ] Clone repo to [app-name] folder and install dependencies
+- [ ] Update the README.md based on your analysis of the codebase and frontend stack
+- [ ] Update package.json name and app name references
+- [ ] Update app name and description on the login page
+- [ ] Generate favicon.png and splash.png images using nova canvas MCP server
+- [ ] Create mock amplify_outputs.json file
+- [ ] Add/update pages and required components, using shadcn components
+- [ ] Extend routing structure
+- [ ] Add sample data to Zustand store
+- [ ] Update navigation
+- [ ] Ensure all required pages are created and wired up
+
+As you go through the implementation, keep updating the checklist to ensure that you have completely created all the pages and features necessary to meet the functional needs of the application. The analysis section should be completed BEFORE beginning any implementation tasks.
+
+### 2. Setup & Configuration
+```bash
+# Clone repository into [app-name] folder
+git clone -b starterkits https://github.com/awslabs/mcp.git [app-name]
+# navigate to the frontend folder
+cd [app-name]/frontend
+# install packages
+npm install
+```
+
+Analyze this code base after cloning to understand how it is structured and the key architectural patterns and frontend stack.
+
+Based on your analysis, update the README.md with an overview of the functional goal of the application and the frontend stack, including specific versions (e.g. React 18 instead of just React)
+
+**PHASE VERIFICATION**: Ensure repository is cloned successfully and all dependencies are installed without errors. Confirm README.md is updated with accurate information.
+
+### 3. Application Branding & Identity
+- Update package.json with new application name
+- Update app name references in components (e.g., app-sidebar.tsx)
+- Update the app name and description on the login page
+- Update document title and metadata in index.html
+- Customize the primary color for the application using Tailwind if the user has provided a custom primary color for the app
+- When setting primary color, you MUST update both the Tailwind and Amplify theme to keep them in sync
+- Use Nova Canvas MCP Server to create the following 2 images:
+  - **favicon.png (320x320)**
+    - Create a minimal abstract icon that represents the app concept
+    - Use monochromatic shades of the primary color
+    - Design should be simple enough to be recognizable at small sizes
+    - Avoid text or complex details that won't scale down well
+  - **splash.png (1024x1024)**
+    - Create a compelling minimal abstract conceptual editorial illustration relevant to the concept of the app
+    - Use primarily dark shades of the primary color with subtle accent colors if appropriate
+    - Design should convey the app's purpose through abstract visual elements
+    - Can include subtle patterns, gradients, or geometric shapes
+- You MUST use 'mv' to move the generated image and overwrite the existing image, as users can be on Windows or Unix systems and the 'move' command might not be available.
+
+```bash
+mv source-folder/file destination-folder/file
+```
+
+- Replace existing app icon references with generated favicon.png
+
+**PHASE VERIFICATION**: Confirm all branding elements are consistently updated throughout the application. Verify both favicon.png and splash.png are properly generated and placed in the public folder.
+
+### 4. UI Development
+- Add new pages following existing patterns
+- Reuse existing pages, layouts, components where possible
+- Install or use shadcn components vs. creating custom components where possible
+- Add required shadcn components: `npx shadcn add [component-name]`
+- Keep component organization flat and simple
+- Extend routing using react-router v7 as configured
+- Update navigation components
+- Add sample data to the Zustand store
+
+**PHASE VERIFICATION**: Ensure all pages in the application analysis document are implemented. Verify routing works correctly between all pages. Confirm components use shadcn UI where appropriate.
+
+### 5. Backend Configuration
+- Create a mock `amplify_outputs.json` file for development
+- Structure it to match expected backend resources
+- This file will later be updated by an external build process
+
+**PHASE VERIFICATION**: Confirm the mock amplify_outputs.json file is correctly formatted and contains all necessary configuration for local development.
+
+**Example: Task App Mock Backend Configuration**
+```json
+{
+  "auth": {
+    "userPoolId": "mock-user-pool-id",
+    "userPoolWebClientId": "mock-client-id",
+    "region": "us-east-1",
+    "identityPoolId": "mock-identity-pool-id"
+  },
+  "api": {
+    "endpoints": [
+      {
+        "name": "TasksAPI",
+        "endpoint": "https://example.com/api/tasks",
+        "region": "us-east-1"
+      }
+    ]
+  }
+}
+```
+
+## Technical Guidelines
+
+### State Management
+- Always use central Zustand store instead of component state
+- Avoid prop drilling completely
+- Components should access store directly via hooks
+- Only use component state for temporary UI states (form inputs while typing)
+
+### Component Organization
+- Keep component organization flat
+- Place new components in appropriate existing folders
+- Don't group by features unless app is complex
+- Follow existing naming conventions
+- Always use shadcn components if available
+
+## Final check
+
+Conduct a final check to make sure that all items in the CHECKLIST.md are completed with a high level of quality and there are no errors or missing functionality.

awslabs/frontend_mcp_server/static/react/troubleshooting.md

@@ -0,0 +1,14 @@
+# Solutions to common issues when generating code for the application
+
+- Always check for guidance from the awslabs.frontend-mcp-server MCP server when implementing new features or adding new pages
+- Routing - always the already installed react-router v7 in Declarative mode for routing. Do not use the outdated react-router-dom package
+- Components - always look for existing shadcn components before attempting to create new custom components
+- Copying/Moving files - the user might be on Windows, try cross-platform commands
+- Generating Images - a minimum resolution of 320x320 is required for Nova Canvas MCP server to generate images
+- Creating Charts - Use shadcn charts for any charting https://ui.shadcn.com/charts
+
+In addition:
+- You MUST carefully analyze the current patterns and packages before suggesting structural or dependency changes
+- Avoid changing existing layouts, login.tsx, app-sidebar.tsx, and authentication and keep any required changes minimal
+- When adding new features, don't complete the analysis prematurely, continue analyzing even if you think you found a solution
+- Ensure the code is complete and pages and components for new features are implemented fully and connected with the rest of the application

awslabs/frontend_mcp_server/utils/__init__.py

@@ -0,0 +1 @@
+"""Utility functions for the frontend MCP server."""

awslabs/frontend_mcp_server/utils/file_utils.py

@@ -0,0 +1,24 @@
+"""File utility functions for the frontend MCP server."""
+
+from pathlib import Path
+
+
+def load_markdown_file(filename: str) -> str:
+    """Load a markdown file from the static/react directory.
+
+    Args:
+        filename (str): The name of the markdown file to load (e.g. 'basic-ui-setup.md')
+
+    Returns:
+        str: The content of the markdown file, or empty string if file not found
+    """
+    base_dir = Path(__file__).parent.parent
+    react_dir = base_dir / 'static' / 'react'
+    file_path = react_dir / filename
+
+    if file_path.exists():
+        with open(file_path, 'r', encoding='utf-8') as f:
+            return f.read()
+    else:
+        print(f'Warning: File not found: {file_path}')
+        return ''

awslabs_frontend_mcp_server-0.0.1.dist-info/METADATA

@@ -0,0 +1,91 @@
+Metadata-Version: 2.4
+Name: awslabs.frontend-mcp-server
+Version: 0.0.1
+Summary: An AWS Labs Model Context Protocol (MCP) server for frontend
+Project-URL: homepage, https://awslabs.github.io/mcp/
+Project-URL: docs, https://awslabs.github.io/mcp/servers/frontend-mcp-server/
+Project-URL: documentation, https://awslabs.github.io/mcp/servers/frontend-mcp-server/
+Project-URL: repository, https://github.com/awslabs/mcp.git
+Project-URL: changelog, https://github.com/awslabs/mcp/blob/main/src/frontend-mcp-server/CHANGELOG.md
+Author: Amazon Web Services
+Author-email: AWSLabs MCP <203918161+awslabs-mcp@users.noreply.github.com>, Jimin Kim <jimini55@users.noreply.github.com>
+License: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.10
+Requires-Dist: loguru>=0.7.0
+Requires-Dist: mcp[cli]>=1.6.0
+Requires-Dist: pydantic>=2.10.6
+Description-Content-Type: text/markdown
+
+# AWS Labs Frontend MCP Server
+
+[![smithery badge](https://smithery.ai/badge/@awslabs/frontend-mcp-server)](https://smithery.ai/server/@awslabs/frontend-mcp-server)
+
+A Model Context Protocol (MCP) server that provides specialized tools for modern web application development.
+
+## Features
+
+### Modern React Application Documentation
+
+This MCP Server provides comprehensive documentation on modern React application development through its `GetReactDocsByTopic` tool, which offers guidance on:
+
+- **Essential Knowledge**: Fundamental concepts for building React applications
+- **Basic UI Setup**: Setting up a React project with Tailwind CSS and shadcn/ui
+- **Authentication**: AWS Amplify authentication integration
+- **Routing**: Implementing routing with React Router
+- **Customizing**: Theming with AWS Amplify components
+- **Creating Components**: Building React components with AWS integrations
+- **Troubleshooting**: Common issues and solutions for React development
+
+## Prerequisites
+
+1. Install `uv` from [Astral](https://docs.astral.sh/uv/getting-started/installation/) or the [GitHub README](https://github.com/astral-sh/uv#installation)
+2. Install Python using `uv python install 3.10`
+
+## Installation
+
+Here are some ways you can work with MCP across AWS, and we'll be adding support to more products including Amazon Q Developer CLI soon: (e.g. for Amazon Q Developer CLI MCP, `~/.aws/amazonq/mcp.json`):
+
+```json
+{
+  "mcpServers": {
+    "awslabs.frontend-mcp-server": {
+      "command": "uvx",
+      "args": ["awslabs.frontend-mcp-server@latest"],
+      "env": {
+        "FASTMCP_LOG_LEVEL": "ERROR"
+      },
+      "disabled": false,
+      "autoApprove": []
+    }
+  }
+}
+```
+
+## Usage
+
+The Frontend MCP Server provides the `GetReactDocsByTopic` tool for accessing specialized documentation on modern web application development with AWS technologies. This server will instruct the caller to clone a base web application repo and use that as the starting point for customization.
+
+### GetReactDocsByTopic
+
+This tool retrieves comprehensive documentation on specific React and AWS integration topics. To use it, specify which topic you need information on:
+
+```python
+result = await get_react_docs_by_topic('essential-knowledge')
+```
+
+Available topics:
+
+1. **essential-knowledge**: Foundational concepts for building React applications with AWS services
+2. **troubleshooting**: Common issues and solutions for React development with AWS integrations
+
+Each topic returns comprehensive markdown documentation with explanations, code examples, and implementation guidance.

awslabs_frontend_mcp_server-0.0.1.dist-info/RECORD

@@ -0,0 +1,13 @@
+awslabs/__init__.py,sha256=47wJeKcStxEJwX7SVVV2pnAWYR8FxcaYoT3YTmZ5Plg,674
+awslabs/frontend_mcp_server/__init__.py,sha256=PM0HjBXxo6pzqf6AHjqT9F6R_RB_WafgbkgTBO-z3G4,616
+awslabs/frontend_mcp_server/server.py,sha256=ZpXBzlaHocp08aUTSXgHLtq7IYO4mePxpvhQjydl4-8,3337
+awslabs/frontend_mcp_server/static/react/essential-knowledge.md,sha256=XdvbkUCyBc0_SiHYbb-a8BFcHaVJA4xttZGKAzMK3Dg,11189
+awslabs/frontend_mcp_server/static/react/troubleshooting.md,sha256=QwvnxGnkgddlg7zO3HuBh9MerIyDDa_LssGZPw371ew,1240
+awslabs/frontend_mcp_server/utils/__init__.py,sha256=Jbns_5gM4Rb-ORTnUQzAFLJDrDGoqntZPruhDdsnT0k,53
+awslabs/frontend_mcp_server/utils/file_utils.py,sha256=LKprH8kVwGcvjGmz8bCEanwlDLELpKUCqqv3ylaSr2c,720
+awslabs_frontend_mcp_server-0.0.1.dist-info/METADATA,sha256=zsx6O6w2oy6PG-WEoMYLZLtx771sJ1fjnFjGX8WgxAg,3878
+awslabs_frontend_mcp_server-0.0.1.dist-info/WHEEL,sha256=qtCwoSJWgHk21S1Kb4ihdzI2rlJ1ZKaIurTj_ngOhyQ,87
+awslabs_frontend_mcp_server-0.0.1.dist-info/entry_points.txt,sha256=oWaTyJPjUC1J5E1xzlD2uTTB5USF9lfV8WmiryUi14s,88
+awslabs_frontend_mcp_server-0.0.1.dist-info/licenses/LICENSE,sha256=CeipvOyAZxBGUsFoaFqwkx54aPnIKEtm9a5u2uXxEws,10142
+awslabs_frontend_mcp_server-0.0.1.dist-info/licenses/NOTICE,sha256=A-DPzBCgbxvwvk0Lzog3Sbq3tkDmIJbM7IZAt-ikdW4,95
+awslabs_frontend_mcp_server-0.0.1.dist-info/RECORD,,

awslabs_frontend_mcp_server-0.0.1.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: hatchling 1.27.0
+Root-Is-Purelib: true
+Tag: py3-none-any

awslabs_frontend_mcp_server-0.0.1.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+awslabs.frontend-mcp-server = awslabs.frontend_mcp_server.server:main

awslabs_frontend_mcp_server-0.0.1.dist-info/licenses/LICENSE

@@ -0,0 +1,175 @@
+
+                                 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.

awslabs_frontend_mcp_server-0.0.1.dist-info/licenses/NOTICE

@@ -0,0 +1,2 @@
+awslabs.frontend-mcp-server
+Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.