@rashidazarang/airtable-mcp 2.1.0 → 2.2.0

package/.github/ISSUE_TEMPLATE/custom.md

@@ -1,10 +0,0 @@
----
-name: Custom issue template
-about: Describe this issue template's purpose here.
-title: ''
-labels: ''
-assignees: ''
-
----
-
-

package/.github/ISSUE_TEMPLATE/feature-request.yml

@@ -1,209 +0,0 @@
-name: ✨ Feature Request
-description: Suggest an enhancement or new feature for the Airtable MCP Server
-title: "[FEATURE] "
-labels: ["enhancement", "feature-request"]
-assignees: []
-
-body:
-  - type: markdown
-    attributes:
-      value: |
-        ## ✨ Feature Request for Airtable MCP Server
-        
-        Thank you for suggesting a new feature! Your ideas help us build a better MCP server and work towards our **100/100 Trust Score** goal.
-
-  - type: checkboxes
-    id: preflight
-    attributes:
-      label: 🔍 Pre-flight Checklist
-      description: Please verify you've completed these steps
-      options:
-        - label: I've searched existing issues and feature requests
-          required: true
-        - label: I've checked the roadmap and planned features
-          required: true
-        - label: This feature aligns with the MCP protocol standards
-          required: true
-        - label: I've considered the security implications
-          required: true
-
-  - type: dropdown
-    id: category
-    attributes:
-      label: 🎯 Feature Category
-      description: What type of feature is this?
-      options:
-        - MCP Protocol Enhancement
-        - Authentication & Security
-        - Airtable API Integration
-        - Performance & Optimization
-        - Developer Experience
-        - Documentation & Guides
-        - CI/CD & Testing
-        - Monitoring & Observability
-        - Enterprise Features
-        - Community & Ecosystem
-      default: 0
-    validations:
-      required: true
-
-  - type: dropdown
-    id: priority
-    attributes:
-      label: 📊 Priority Level
-      description: How important is this feature?
-      options:
-        - Critical - Blocking major use cases
-        - High - Significantly improves functionality
-        - Medium - Nice to have enhancement
-        - Low - Minor improvement or convenience
-      default: 2
-    validations:
-      required: true
-
-  - type: textarea
-    id: problem
-    attributes:
-      label: 🎯 Problem Statement
-      description: What problem does this feature solve?
-      placeholder: |
-        Describe the current limitation or pain point that this feature would address...
-    validations:
-      required: true
-
-  - type: textarea
-    id: solution
-    attributes:
-      label: 💡 Proposed Solution
-      description: Describe your proposed feature in detail
-      placeholder: |
-        Explain how this feature would work and what it would do...
-    validations:
-      required: true
-
-  - type: textarea
-    id: use-cases
-    attributes:
-      label: 🎬 Use Cases
-      description: Provide specific examples of how this feature would be used
-      placeholder: |
-        1. As a developer, I want to...
-        2. When integrating with..., I need to...
-        3. For enterprise customers, this would enable...
-    validations:
-      required: true
-
-  - type: textarea
-    id: alternatives
-    attributes:
-      label: 🔄 Alternatives Considered
-      description: What other solutions have you considered?
-      placeholder: |
-        - Alternative approach 1: ...
-        - Workaround currently used: ...
-        - Why those don't work: ...
-
-  - type: textarea
-    id: implementation
-    attributes:
-      label: 🛠️ Implementation Ideas
-      description: Do you have ideas about how this could be implemented?
-      placeholder: |
-        - Technical approach: ...
-        - Required changes: ...
-        - Dependencies: ...
-        - API design: ...
-
-  - type: checkboxes
-    id: requirements
-    attributes:
-      label: 📋 Requirements & Considerations
-      description: What should this feature include?
-      options:
-        - label: Backward compatibility maintained
-        - label: Security review required
-        - label: Performance impact minimized
-        - label: Documentation and examples included
-        - label: Unit and integration tests added
-        - label: CLI/API interface designed
-        - label: Error handling implemented
-        - label: Logging and monitoring added
-
-  - type: textarea
-    id: acceptance
-    attributes:
-      label: ✅ Acceptance Criteria
-      description: How do we know when this feature is complete?
-      placeholder: |
-        - [ ] Feature works as described
-        - [ ] All tests pass
-        - [ ] Documentation updated
-        - [ ] Performance benchmarks met
-        - [ ] Security review passed
-    validations:
-      required: true
-
-  - type: dropdown
-    id: trust-score
-    attributes:
-      label: 🎯 Trust Score Impact
-      description: How would this feature contribute to our 100/100 Trust Score goal?
-      options:
-        - High Impact - Directly improves security, reliability, or protocol compliance
-        - Medium Impact - Enhances developer experience or documentation quality
-        - Low Impact - Minor convenience or optimization
-        - No Impact - Neutral feature
-      default: 1
-
-  - type: textarea
-    id: trust-score-details
-    attributes:
-      label: 📈 Trust Score Benefits
-      description: Explain how this feature supports our Trust Score goals
-      placeholder: |
-        This feature would improve our Trust Score by:
-        - Enhancing security through...
-        - Improving protocol compliance via...
-        - Better developer experience with...
-        - Enterprise readiness by...
-
-  - type: checkboxes
-    id: contribution
-    attributes:
-      label: 🤝 Contribution Interest
-      description: Are you interested in helping implement this feature?
-      options:
-        - label: I'm willing to implement this feature
-        - label: I can help with design and specification
-        - label: I can provide testing and feedback
-        - label: I can help with documentation
-        - label: I can sponsor development of this feature
-
-  - type: textarea
-    id: additional
-    attributes:
-      label: ➕ Additional Context
-      description: Any other information about this feature request
-      placeholder: |
-        - Links to relevant specifications
-        - Examples from other projects
-        - User feedback or requests
-        - Business justification
-        - Timeline requirements
-
-  - type: markdown
-    attributes:
-      value: |
-        ## 🚀 Next Steps
-        
-        Thank you for your feature request! Here's what happens next:
-        
-        1. **Triage** (24-48 hours): We'll review and label your request
-        2. **Community Input** (1 week): Other users can comment and vote
-        3. **Technical Review** (1-2 weeks): We'll assess feasibility and design
-        4. **Roadmap Planning**: Approved features get added to our roadmap
-        5. **Implementation**: Features are built according to priority
-        
-        **Want to stay updated?** Watch this repository and join our [discussions](https://github.com/rashidazarang/airtable-mcp/discussions)!
-        
-        **🎯 Our Mission**: Building the most trusted and comprehensive MCP server for Airtable with a perfect **100/100 Trust Score**.

package/.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,20 +0,0 @@
----
-name: Feature request
-about: Suggest an idea for this project
-title: ''
-labels: ''
-assignees: ''
-
----
-
-**Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
-
-**Describe the solution you'd like**
-A clear and concise description of what you want to happen.
-
-**Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
-
-**Additional context**
-Add any other context or screenshots about the feature request here.

package/.github/ISSUE_TEMPLATE/security-report.yml

@@ -1,216 +0,0 @@
-name: 🔒 Security Vulnerability Report
-description: Report a security vulnerability privately and responsibly
-title: "[SECURITY] "
-labels: ["security", "urgent"]
-assignees: ["rashidazarang"]
-
-body:
-  - type: markdown
-    attributes:
-      value: |
-        ## 🔒 Security Vulnerability Report
-        
-        **⚠️ IMPORTANT**: If this is a critical security vulnerability that could be exploited, please **DO NOT** create a public issue. Instead, please email us directly at security@[domain] or use GitHub's private vulnerability reporting feature.
-        
-        For non-critical security improvements or questions, you can use this template.
-
-  - type: checkboxes
-    id: severity-check
-    attributes:
-      label: 🚨 Severity Assessment
-      description: Please confirm this is appropriate for public reporting
-      options:
-        - label: This is NOT a critical vulnerability that could be immediately exploited
-          required: true
-        - label: I understand that critical vulnerabilities should be reported privately
-          required: true
-        - label: This is a security improvement suggestion or non-critical finding
-          required: true
-
-  - type: dropdown
-    id: vulnerability-type
-    attributes:
-      label: 🎯 Vulnerability Type
-      description: What type of security issue is this?
-      options:
-        - Authentication/Authorization
-        - Input Validation
-        - Information Disclosure
-        - Configuration Security
-        - Dependency Vulnerability
-        - Cross-Site Scripting (XSS)
-        - SQL Injection
-        - Code Injection
-        - Denial of Service
-        - Cryptographic Issue
-        - Access Control
-        - Security Misconfiguration
-        - Other
-    validations:
-      required: true
-
-  - type: dropdown
-    id: severity
-    attributes:
-      label: 📊 Severity Level
-      description: Based on CVSS or similar standards
-      options:
-        - Info - No immediate security impact
-        - Low - Minimal security impact
-        - Medium - Moderate security impact  
-        - High - Significant security impact
-        - Critical - Severe security impact
-      default: 1
-    validations:
-      required: true
-
-  - type: textarea
-    id: description
-    attributes:
-      label: 📝 Vulnerability Description
-      description: Describe the security issue in detail
-      placeholder: |
-        Provide a clear description of the security vulnerability or concern...
-    validations:
-      required: true
-
-  - type: textarea
-    id: impact
-    attributes:
-      label: 💥 Potential Impact
-      description: What could an attacker accomplish?
-      placeholder: |
-        - Data exposure: ...
-        - Unauthorized access: ...
-        - System compromise: ...
-        - Service disruption: ...
-    validations:
-      required: true
-
-  - type: textarea
-    id: reproduction
-    attributes:
-      label: 🔄 Reproduction Steps
-      description: How can this vulnerability be reproduced? (Use general terms for public issues)
-      placeholder: |
-        1. Configure the server with...
-        2. Send a request to...
-        3. Observe the security issue...
-    validations:
-      required: true
-
-  - type: textarea
-    id: environment
-    attributes:
-      label: 🖥️ Affected Environment
-      description: Where does this vulnerability exist?
-      value: |
-        **Server Version**: 
-        **Component**: 
-        **Configuration**: 
-        **Operating System**: 
-        **Deployment Method**: 
-      render: markdown
-    validations:
-      required: true
-
-  - type: textarea
-    id: mitigation
-    attributes:
-      label: 🛡️ Suggested Mitigation
-      description: How do you think this should be fixed?
-      placeholder: |
-        - Input validation: ...
-        - Authentication checks: ...
-        - Configuration changes: ...
-        - Code modifications: ...
-
-  - type: textarea
-    id: workaround
-    attributes:
-      label: 🔧 Temporary Workaround
-      description: Is there a way users can protect themselves now?
-      placeholder: |
-        Users can temporarily mitigate this by:
-        - Configuring...
-        - Avoiding...
-        - Using...
-
-  - type: checkboxes
-    id: affected-components
-    attributes:
-      label: 🎯 Affected Components
-      description: Which parts of the system are affected?
-      options:
-        - label: MCP Protocol Handler
-        - label: OAuth2 Authentication
-        - label: API Token Handling
-        - label: Rate Limiting
-        - label: Input Validation
-        - label: Logging System
-        - label: Docker Container
-        - label: CI/CD Pipeline
-        - label: Documentation/Examples
-        - label: Dependencies
-
-  - type: dropdown
-    id: disclosure
-    attributes:
-      label: 📅 Disclosure Timeline
-      description: When should this be publicly disclosed?
-      options:
-        - Immediately (already public or low risk)
-        - After fix is released
-        - Coordinated disclosure (30-90 days)
-        - Vendor discretion
-      default: 1
-    validations:
-      required: true
-
-  - type: textarea
-    id: references
-    attributes:
-      label: 📚 References
-      description: Any relevant links or documentation
-      placeholder: |
-        - CVE references: ...
-        - Security advisories: ...
-        - Documentation: ...
-        - Similar issues: ...
-
-  - type: checkboxes
-    id: responsible-disclosure
-    attributes:
-      label: 🤝 Responsible Disclosure
-      description: Please confirm your commitment to responsible disclosure
-      options:
-        - label: I will not publicly disclose details until a fix is available
-          required: true
-        - label: I will coordinate with the maintainers on disclosure timing
-          required: true
-        - label: I understand this may be moved to a private security advisory
-          required: true
-
-  - type: markdown
-    attributes:
-      value: |
-        ## 🔒 Security Response Process
-        
-        **Our commitment to security:**
-        
-        1. **Acknowledgment** (24 hours): We'll confirm receipt of your report
-        2. **Initial Assessment** (48 hours): We'll evaluate severity and impact
-        3. **Investigation** (1-7 days): We'll reproduce and analyze the issue
-        4. **Fix Development** (varies): We'll develop and test a solution
-        5. **Release & Disclosure** (coordinated): We'll release fixes and advisories
-        
-        **🎯 Trust Score Impact**: Security vulnerabilities directly impact our **100/100 Trust Score** goal. Your responsible reporting helps us maintain the highest security standards.
-        
-        **Contact Information:**
-        - Email: security@[domain] (for critical issues)
-        - GitHub Security Advisories (preferred for coordination)
-        - Matrix/Discord: [community channels] (for questions)
-        
-        **Bug Bounty**: While we don't currently have a formal bug bounty program, we deeply appreciate security researchers and will acknowledge your contributions publicly (with your permission).
-        
-        Thank you for helping keep the Airtable MCP Server secure! 🙏

package/.github/pull_request_template.md

@@ -1,245 +0,0 @@
-# 🚀 Pull Request - Trust Score 100/100
-
-<!-- 
-Thank you for contributing to the Airtable MCP Server! 
-Your contribution helps us achieve our goal of a perfect 100/100 Trust Score.
--->
-
-## 📋 PR Information
-
-**PR Type**: <!-- Check all that apply -->
-- [ ] 🐛 Bug Fix
-- [ ] ✨ New Feature  
-- [ ] 🔒 Security Enhancement
-- [ ] 📚 Documentation Update
-- [ ] 🧹 Code Refactoring
-- [ ] ⚡ Performance Improvement
-- [ ] 🧪 Test Enhancement
-- [ ] 🔧 Build/CI Changes
-- [ ] 💥 Breaking Change
-
-**Issue Reference**: 
-<!-- Link to the issue this PR addresses -->
-- Closes #[issue_number]
-- Related to #[issue_number]
-
-## 📝 Description
-
-### What Changed
-<!-- Provide a clear and concise description of what this PR does -->
-
-### Why This Change
-<!-- Explain the motivation behind this change -->
-
-### How It Works
-<!-- Describe the technical approach and implementation -->
-
-## 🎯 Trust Score Impact
-
-**Trust Score Categories Affected**: <!-- Check all that apply -->
-- [ ] 🛡️ Security & Authentication
-- [ ] 📊 Code Quality & Standards
-- [ ] 🧪 Testing & Reliability
-- [ ] 📚 Documentation & Usability
-- [ ] 🚀 Performance & Scalability
-- [ ] 🔧 CI/CD & Automation
-- [ ] 🌐 Protocol Compliance
-- [ ] 👥 Community & Support
-
-**Expected Impact**: 
-<!-- Describe how this contributes to our 100/100 Trust Score goal -->
-
-## 🧪 Testing Checklist
-
-### Automated Tests
-- [ ] Unit tests added/updated
-- [ ] Integration tests added/updated
-- [ ] Security tests added/updated
-- [ ] Performance tests added/updated
-- [ ] All existing tests pass
-- [ ] Coverage maintained or improved
-
-### Manual Testing
-- [ ] MCP protocol functionality verified
-- [ ] OAuth2 authentication tested (if applicable)
-- [ ] Rate limiting verified (if applicable)
-- [ ] Error handling tested
-- [ ] Edge cases covered
-- [ ] Backward compatibility confirmed
-
-### Test Environment
-**Tested On**:
-- [ ] Node.js 16.x
-- [ ] Node.js 18.x  
-- [ ] Node.js 20.x
-- [ ] Docker container
-- [ ] Multiple operating systems
-
-**MCP Clients Tested**:
-- [ ] Claude Desktop
-- [ ] Cursor IDE
-- [ ] VS Code with Cline
-- [ ] Custom MCP client
-
-## 🔒 Security Review
-
-### Security Checklist
-- [ ] No hardcoded secrets or credentials
-- [ ] Input validation implemented
-- [ ] Output sanitization applied
-- [ ] Authentication/authorization checked
-- [ ] SQL injection prevention verified
-- [ ] XSS prevention implemented
-- [ ] CSRF protection maintained
-- [ ] Rate limiting respected
-- [ ] Error messages don't leak sensitive info
-- [ ] Dependencies updated and secure
-
-### Security Impact Assessment
-<!-- If this PR has security implications, describe them -->
-- **Authentication Changes**: 
-- **Data Access Changes**: 
-- **New Attack Vectors**: 
-- **Mitigation Measures**: 
-
-## 📊 Performance Impact
-
-### Performance Checklist
-- [ ] No significant performance regression
-- [ ] Memory usage optimized
-- [ ] Database queries optimized (if applicable)
-- [ ] Network requests minimized
-- [ ] Caching implemented where appropriate
-- [ ] Async/await used properly
-
-### Benchmarks
-<!-- If applicable, include performance measurements -->
-**Before**:
-```
-Metric: [value]
-```
-
-**After**:
-```
-Metric: [value]
-```
-
-## 📚 Documentation
-
-### Documentation Updates
-- [ ] README.md updated
-- [ ] API documentation updated
-- [ ] Code comments added/updated
-- [ ] Examples updated
-- [ ] Troubleshooting guide updated
-- [ ] CHANGELOG.md updated
-- [ ] Migration guide provided (for breaking changes)
-
-### Documentation Quality
-- [ ] Clear and concise explanations
-- [ ] Code examples provided
-- [ ] Screenshots/diagrams included (if applicable)
-- [ ] Links verified and working
-
-## 🔄 Breaking Changes
-
-### Breaking Change Assessment
-- [ ] This is NOT a breaking change
-- [ ] This is a breaking change (explain below)
-
-<!-- If breaking change, provide details -->
-**Breaking Changes**:
-- **What breaks**: 
-- **Migration path**: 
-- **Deprecation timeline**: 
-
-## 🎬 Demo/Examples
-
-### How to Test This PR
-```bash
-# Step-by-step instructions to test this PR
-git checkout [branch-name]
-npm install
-# ... additional setup steps
-```
-
-### Usage Examples
-```javascript
-// Provide code examples showing the new functionality
-```
-
-## 📋 Review Checklist
-
-### Code Quality
-- [ ] Code follows project style guidelines
-- [ ] No console.log or debug statements
-- [ ] Error handling is comprehensive
-- [ ] Code is well-commented
-- [ ] Functions are properly documented
-- [ ] Variable names are descriptive
-- [ ] Magic numbers avoided
-
-### Git History
-- [ ] Commit messages are clear and descriptive
-- [ ] Commits are logically organized
-- [ ] No merge commits (rebased if needed)
-- [ ] No sensitive information in commit history
-
-## 🤝 Collaboration
-
-### Review Requests
-**Reviewers Needed**:
-- [ ] Security review required
-- [ ] Performance review required
-- [ ] Documentation review required
-- [ ] UI/UX review required
-
-**Specific Review Areas**:
-<!-- Ask reviewers to focus on specific aspects -->
-- Please review the OAuth2 implementation for security
-- Please check the new API endpoints for usability
-- Please verify the documentation is clear
-
-### Follow-up Tasks
-<!-- List any follow-up work needed -->
-- [ ] Create/update related issues
-- [ ] Plan future enhancements
-- [ ] Update project roadmap
-- [ ] Coordinate with documentation team
-
-## 🎯 Success Criteria
-
-### Definition of Done
-- [ ] All acceptance criteria met
-- [ ] All tests passing
-- [ ] Security review completed
-- [ ] Documentation updated
-- [ ] Performance impact assessed
-- [ ] Backward compatibility verified
-- [ ] CI/CD pipeline passing
-
-### Trust Score Validation
-- [ ] Contributes to security improvements
-- [ ] Maintains or improves code quality
-- [ ] Includes comprehensive testing
-- [ ] Provides clear documentation
-- [ ] Follows community best practices
-
-## 📸 Screenshots/Media
-
-<!-- Include screenshots, GIFs, or videos demonstrating the changes -->
-
-## 🙏 Acknowledgments
-
-<!-- Thank contributors, mention inspiration, or credit sources -->
-
----
-
-## 📞 Need Help?
-
-- 💬 **Questions**: Start a [discussion](https://github.com/rashidazarang/airtable-mcp/discussions)
-- 🐛 **Issues**: Check our [issue tracker](https://github.com/rashidazarang/airtable-mcp/issues)
-- 📚 **Docs**: Read our [documentation](./README.md)
-- 🔒 **Security**: Email security@[domain] for private matters
-
-**🎯 Our Mission**: Building the most trusted and comprehensive MCP server for Airtable with a perfect **100/100 Trust Score**. Thank you for contributing to this goal! 🚀