Add licensing, automation commands, and project documentation

- Add custom non-commercial license with commercial protection
- Create Claude Code commands for automated license checking
- Add comprehensive project documentation in docs/ folder
- Move KNOWN_ISSUES.md to docs/ for better organization
- Add GitHub issue templates for MCP server context
- Update README with licensing and documentation references

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Author: gui-wf

.claude/commands/check-license.md

@@ -0,0 +1,60 @@
+---
+argument-hint: [package-name] [version-optional]
+description: Check if a package license is compatible with our non-commercial license
+---
+
+Check the license compatibility for package $1 ${2:+version $2}.
+
+## License Checking Workflow
+
+First, run the license check command:
+```bash
+npm view $1${2:+@$2} license
+```
+
+Then analyze the result using this decision tree:
+
+### ✅ COMPATIBLE LICENSES
+If the license is one of: **MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, 0BSD**
+
+**Action:** Proceed with the update
+1. Use `/update-license-docs` command to update docs/package-licenses.md
+2. If this is a license change from the previous version, note it in the "Notes" column
+3. Continue with package installation/update
+4. Confirm compatibility has been verified
+
+### 🚨 INCOMPATIBLE LICENSES  
+If the license is one of: **GPL, GPL-2.0, GPL-3.0, AGPL, AGPL-3.0, LGPL, LGPL-2.1, LGPL-3.0**
+
+**Action:** Cannot use this package version
+1. **Recommend:** Keep the current version (check current version in package.json)
+2. **Alternative:** Search for alternatives with: `npm search <package-functionality-keywords>`
+3. **Last resort:** Consider if our project license should be changed to accommodate this dependency
+4. Document the incompatibility issue for future reference
+
+### ⚠️ REQUIRES MANUAL REVIEW
+If the license contains: **"NonCommercial", "NC", "Commercial", proprietary terms**
+
+**Action:** Manual review needed
+1. Check if the license restrictions overlap with our non-commercial license (potentially redundant)
+2. Verify if the license allows our intended use case (internal productivity, open source contributions)
+3. Flag for decision: proceed, find alternatives, or contact package maintainer
+
+### ❓ UNKNOWN/UNDEFINED LICENSE
+If npm returns: **undefined, empty, or unrecognized license**
+
+**Action:** Investigation required  
+1. Check the package's GitHub repository for LICENSE file
+2. Look in package.json for license field
+3. Check README.md for license information
+4. If still unclear, consider this package high-risk and find alternatives
+
+## Output Format
+
+Always provide a clear summary:
+- **License found:** [license name]
+- **Compatibility:** ✅ Compatible / 🚨 Incompatible / ⚠️ Needs Review / ❓ Unknown
+- **Recommended action:** [specific next steps]
+- **Alternative packages:** [if applicable]
+
+This ensures consistent license checking across all package updates and maintains our project's licensing integrity.

.claude/commands/update-license-docs.md

@@ -0,0 +1,52 @@
+---
+argument-hint: [package-name] [version] [license] [notes-optional]
+description: Update docs/package-licenses.md with new package information
+---
+
+Update the package license documentation for $1 version $2 with license $3.
+
+## Update Process
+
+1. **Read current docs/package-licenses.md** to understand the existing format and find the package entry
+
+2. **Determine update type:**
+   - **New package:** Add new row to the appropriate table (Runtime Dependencies or Development Dependencies)
+   - **Version update:** Update existing package version
+   - **License change:** Update license field and add note about the change
+
+3. **Update the markdown table:**
+   - Locate the correct table (Runtime Dependencies vs Development Dependencies)
+   - Find or create the package row: `| $1 | $2 | $3 | ✅ | ${4:-Version update} |`
+   - Maintain alphabetical ordering within each table
+   - Ensure consistent formatting with existing entries
+
+4. **Update metadata:**
+   - Change "Last updated" date to today's date (2025-01-19)
+   - Keep "Package.json version" as 1.0.0 unless the package.json version field has changed
+
+5. **Add notes if provided:**
+   - If $4 is provided, use it in the Notes column
+   - For license changes, format as: "License changed from [old] to [new]"
+   - For new packages, use: "New dependency added"
+   - For version updates with same license, use: "Version update"
+
+## Table Format Reference
+
+```markdown
+| Package | Version | License | Compatible | Notes |
+|---------|---------|---------|------------|-------|
+| package-name | x.y.z | MIT | ✅ | Description |
+```
+
+## Validation Checklist
+
+Before saving the updated file:
+- [ ] Package is in the correct table (runtime vs dev dependencies)
+- [ ] Version format is consistent (x.y.z)
+- [ ] License name matches npm registry format
+- [ ] Compatible column shows ✅ (since we only update compatible packages)
+- [ ] Notes column has meaningful information
+- [ ] "Last updated" date is current
+- [ ] Markdown table formatting is preserved
+
+This command should only be used after `/check-license` has confirmed compatibility.

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,124 @@
+name: 🐛 MCP Server Bug Report
+description: Report an issue with the PurelyMail MCP Server
+title: "[Bug]: "
+labels: ["bug", "triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for reporting a bug with the PurelyMail MCP Server! 
+        This template helps us understand AI assistant interaction issues.
+        
+  - type: dropdown
+    id: assistant
+    attributes:
+      label: AI Assistant/Tool Used
+      description: Which AI assistant were you using when the issue occurred?
+      options:
+        - Claude Desktop
+        - Claude Code CLI
+        - Cursor
+        - Codex CLI
+        - Continue (VS Code)
+        - Aider
+        - Other MCP Client
+        - Custom Implementation
+    validations:
+      required: true
+      
+  - type: textarea
+    id: prompt
+    attributes:
+      label: Exact Prompt Used
+      description: Please provide the exact prompt/request you gave to the AI assistant
+      placeholder: |
+        Example: "Create a new email account [email protected] with a strong password"
+    validations:
+      required: true
+      
+  - type: dropdown
+    id: context-pollution
+    attributes:
+      label: Context Pollution Level
+      description: On a scale of 1-10, how much of your prior conversation with the assistant was related to PurelyMail account management?
+      options:
+        - "1 - No prior PurelyMail context"
+        - "2 - Minimal PurelyMail mentions"
+        - "3 - Some unrelated PurelyMail discussion"
+        - "4 - Mixed topics with some PurelyMail"
+        - "5 - Half PurelyMail, half other topics"
+        - "6 - Mostly PurelyMail with some other topics"
+        - "7 - Primarily PurelyMail focused"
+        - "8 - Almost entirely PurelyMail discussion"
+        - "9 - Continuous PurelyMail conversation"
+        - "10 - Pure PurelyMail management session"
+    validations:
+      required: true
+      
+  - type: textarea
+    id: expected-result
+    attributes:
+      label: Expected Result
+      description: What did you expect the AI assistant to accomplish?
+      placeholder: |
+        Example: "Assistant should create user 'thomas' on domain 'cool.shop' with a secure password"
+    validations:
+      required: true
+      
+  - type: textarea
+    id: actual-result
+    attributes:
+      label: Actual Result
+      description: What actually happened? Include any error messages from the assistant or MCP server
+      placeholder: |
+        Example: "Assistant failed with error 'invalidRequest' or used wrong parameters"
+    validations:
+      required: true
+      
+  - type: textarea
+    id: expected-parameters
+    attributes:
+      label: Expected MCP Tool Parameters
+      description: |
+        What parameters should the assistant have used? (Based on PurelyMail API requirements)
+        For CreateUser: userName (required), domainName (required), password (required)
+        Optional: enablePasswordReset, recoveryEmail, enableSearchIndexing, sendWelcomeEmail
+      placeholder: |
+        Example for CreateUser:
+        - userName: "thomas" (required)
+        - domainName: "cool.shop" (required)  
+        - password: "[generated]" (required)
+        - enablePasswordReset: true (optional, defaults to true)
+        
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment Details
+      description: Technical environment information
+      placeholder: |
+        - MCP Client: [e.g. Claude Desktop v1.0.0]
+        - MCP Server Version: [e.g. 1.2.3]
+        - Node.js Version: [e.g. 18.17.0]
+        - Operating System: [e.g. macOS 13.0, Windows 11, Ubuntu 22.04]
+    validations:
+      required: true
+      
+  - type: textarea
+    id: conversation-flow
+    attributes:
+      label: Conversation Flow (if relevant)
+      description: |
+        If this bug occurred after multiple exchanges, briefly describe the conversation flow
+      placeholder: |
+        1. Asked assistant to list domains
+        2. Asked to create user on specific domain  
+        3. Bug occurred when trying to create app password
+        
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our Code of Conduct
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,133 @@
+name: 🚀 MCP Server Feature Request
+description: Suggest a new feature or improvement for the PurelyMail MCP Server
+title: "[Feature]: "
+labels: ["enhancement", "triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for suggesting a feature for the PurelyMail MCP Server!
+        Help us understand how to improve AI assistant interactions.
+        
+  - type: dropdown
+    id: feature-type
+    attributes:
+      label: Feature Type
+      description: What type of feature are you requesting?
+      options:
+        - New MCP Tool (expose new PurelyMail API endpoint)
+        - Improve Existing Tool (better parameters, validation, etc.)
+        - Better AI Assistant Integration (prompting, context handling)
+        - Developer Experience (docs, error messages, etc.)
+        - Performance/Reliability Improvement
+        - Other
+    validations:
+      required: true
+      
+  - type: textarea
+    id: use-case
+    attributes:
+      label: Use Case Description
+      description: Describe the specific use case or workflow this feature would enable
+      placeholder: |
+        Example: "I want AI assistants to be able to bulk-create multiple email accounts 
+        from a CSV file or list, instead of creating them one by one"
+    validations:
+      required: true
+      
+  - type: textarea
+    id: current-limitation
+    attributes:
+      label: Current Limitation
+      description: What's currently missing or difficult to achieve?
+      placeholder: |
+        Example: "Currently, the assistant has to make separate API calls for each user creation, 
+        which is slow and prone to partial failures"
+    validations:
+      required: true
+      
+  - type: textarea
+    id: proposed-solution
+    attributes:
+      label: Proposed Solution & Flow
+      description: |
+        Describe your proposed solution and how it would work from a high-level perspective.
+        Include the expected conversation flow with an AI assistant.
+      placeholder: |
+        Example:
+        1. User provides: "Create these email accounts: [email protected], [email protected], [email protected]"
+        2. Assistant uses new "Bulk Create Users" tool with array of user definitions
+        3. Tool validates all inputs before starting, returns detailed success/failure report
+        4. Assistant reports back with summary of created accounts and any failures
+    validations:
+      required: true
+      
+  - type: textarea
+    id: purelymail-api
+    attributes:
+      label: Related PurelyMail API Endpoints
+      description: |
+        If this involves new API integration, which PurelyMail endpoints would be involved?
+        Check the swagger spec or mention if this requires new PurelyMail API features.
+      placeholder: |
+        Example: 
+        - Extends existing "Create User" endpoint
+        - OR requires new bulk endpoint from PurelyMail
+        - OR combines "Create User" + "Create App Password" operations
+        
+  - type: dropdown
+    id: priority
+    attributes:
+      label: Priority
+      description: How important is this feature for your workflow?
+      options:
+        - Low - Nice to have
+        - Medium - Would improve efficiency  
+        - High - Significantly impacts workflow
+        - Critical - Blocking important use cases
+    validations:
+      required: true
+      
+  - type: dropdown
+    id: assistant-used
+    attributes:
+      label: Primary AI Assistant
+      description: Which AI assistant would you primarily use this feature with?
+      options:
+        - Claude Desktop
+        - Claude Code CLI
+        - Cursor
+        - Codex CLI
+        - Continue (VS Code)
+        - Aider
+        - Multiple assistants
+        - Other MCP Client
+    validations:
+      required: true
+      
+  - type: textarea
+    id: ai-assistant-benefit
+    attributes:
+      label: AI Assistant Benefit
+      description: |
+        How would this feature specifically improve AI assistant interactions?
+        Consider prompt clarity, error handling, context efficiency, etc.
+      placeholder: |
+        Example: "This would reduce the number of back-and-forth exchanges needed,
+        make prompts more natural ('create these 5 accounts' vs individual requests),
+        and provide clearer success/failure feedback"
+        
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional Context
+      description: Any other context, examples, or considerations
+      
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our Code of Conduct
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.mcp.json

@@ -17,6 +17,13 @@
         "PURELYMAIL_API_KEY": "${PURELYMAIL_API_KEY}",
         "MOCK_MODE": "false"
       }
+    },
+    "perplexity": {
+      "command": "npx",
+      "args": ["-y", "perplexity-mcp"],
+      "env": {
+        "PERPLEXITY_API_KEY": "${PERPLEXITY_API_KEY}"
+      }
     }
   }
 }