@mokoconsulting/mcp-mokogitea-api 1.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (86) hide show
  1. package/.gitattributes +94 -0
  2. package/.gitmessage +9 -0
  3. package/.mokogitea/ISSUE_TEMPLATE/adr.md +110 -0
  4. package/.mokogitea/ISSUE_TEMPLATE/bug_report.md +48 -0
  5. package/.mokogitea/ISSUE_TEMPLATE/config.yml +18 -0
  6. package/.mokogitea/ISSUE_TEMPLATE/documentation.md +52 -0
  7. package/.mokogitea/ISSUE_TEMPLATE/enterprise_support.md +85 -0
  8. package/.mokogitea/ISSUE_TEMPLATE/feature_request.md +51 -0
  9. package/.mokogitea/ISSUE_TEMPLATE/firewall-request.md +190 -0
  10. package/.mokogitea/ISSUE_TEMPLATE/mcp_api_integration.md +48 -0
  11. package/.mokogitea/ISSUE_TEMPLATE/mcp_connection_issue.md +67 -0
  12. package/.mokogitea/ISSUE_TEMPLATE/mcp_tool_request.md +49 -0
  13. package/.mokogitea/ISSUE_TEMPLATE/question.md +82 -0
  14. package/.mokogitea/ISSUE_TEMPLATE/rfc.md +126 -0
  15. package/.mokogitea/ISSUE_TEMPLATE/security.md +51 -0
  16. package/.mokogitea/ISSUE_TEMPLATE/version.md +24 -0
  17. package/.mokogitea/auto-assign.yml +76 -0
  18. package/.mokogitea/auto-dev-issue.yml +207 -0
  19. package/.mokogitea/auto-release.yml +337 -0
  20. package/.mokogitea/branch-protection.yml +251 -0
  21. package/.mokogitea/changelog-validation.yml +101 -0
  22. package/.mokogitea/codeql-analysis.yml +115 -0
  23. package/.mokogitea/copilot-agent.yml +44 -0
  24. package/.mokogitea/deploy-demo.yml +734 -0
  25. package/.mokogitea/deploy-dev.yml +700 -0
  26. package/.mokogitea/enterprise-firewall-setup.yml +758 -0
  27. package/.mokogitea/manifest.xml +25 -0
  28. package/.mokogitea/mcp-auto-release.yml +278 -0
  29. package/.mokogitea/mcp-build-test.yml +65 -0
  30. package/.mokogitea/mcp-sdk-check.yml +109 -0
  31. package/.mokogitea/mcp-tool-inventory.yml +61 -0
  32. package/.mokogitea/pr-branch-check.yml +90 -0
  33. package/.mokogitea/repository-cleanup.yml +525 -0
  34. package/.mokogitea/standards-compliance.yml +2614 -0
  35. package/.mokogitea/sync-version-on-merge.yml +133 -0
  36. package/.mokogitea/workflows/auto-assign.yml +76 -0
  37. package/.mokogitea/workflows/auto-bump.yml +66 -0
  38. package/.mokogitea/workflows/auto-dev-issue.yml +207 -0
  39. package/.mokogitea/workflows/auto-release.yml +341 -0
  40. package/.mokogitea/workflows/branch-cleanup.yml +48 -0
  41. package/.mokogitea/workflows/cascade-dev.yml +10 -0
  42. package/.mokogitea/workflows/changelog-validation.yml +101 -0
  43. package/.mokogitea/workflows/ci-generic.yml +204 -0
  44. package/.mokogitea/workflows/cleanup.yml +87 -0
  45. package/.mokogitea/workflows/codeql-analysis.yml +115 -0
  46. package/.mokogitea/workflows/copilot-agent.yml +44 -0
  47. package/.mokogitea/workflows/deploy-manual.yml +126 -0
  48. package/.mokogitea/workflows/enterprise-firewall-setup.yml +758 -0
  49. package/.mokogitea/workflows/gitleaks.yml +96 -0
  50. package/.mokogitea/workflows/issue-branch.yml +73 -0
  51. package/.mokogitea/workflows/mcp-auto-release.yml +280 -0
  52. package/.mokogitea/workflows/mcp-build-test.yml +65 -0
  53. package/.mokogitea/workflows/mcp-sdk-check.yml +109 -0
  54. package/.mokogitea/workflows/mcp-tool-inventory.yml +61 -0
  55. package/.mokogitea/workflows/notify.yml +70 -0
  56. package/.mokogitea/workflows/npm-publish.yml +51 -0
  57. package/.mokogitea/workflows/pr-check.yml +508 -0
  58. package/.mokogitea/workflows/pre-release.yml +11 -0
  59. package/.mokogitea/workflows/repo-health.yml +711 -0
  60. package/.mokogitea/workflows/repository-cleanup.yml +525 -0
  61. package/.mokogitea/workflows/security-audit.yml +82 -0
  62. package/.mokogitea/workflows/standards-compliance.yml +2614 -0
  63. package/.mokogitea/workflows/sync-version-on-merge.yml +130 -0
  64. package/.mokogitea/workflows/update-server.yml +312 -0
  65. package/CHANGELOG.md +145 -0
  66. package/CLAUDE.md +43 -0
  67. package/CONTRIBUTING.md +161 -0
  68. package/README.md +286 -0
  69. package/SECURITY.md +91 -0
  70. package/automation/ci-issue-reporter.sh +237 -0
  71. package/config.example.json +13 -0
  72. package/dist/client.d.ts +15 -0
  73. package/dist/client.js +104 -0
  74. package/dist/config.d.ts +4 -0
  75. package/dist/config.js +48 -0
  76. package/dist/index.d.ts +3 -0
  77. package/dist/index.js +1119 -0
  78. package/dist/types.d.ts +20 -0
  79. package/dist/types.js +16 -0
  80. package/package.json +34 -0
  81. package/scripts/setup.mjs +40 -0
  82. package/src/client.ts +120 -0
  83. package/src/config.ts +58 -0
  84. package/src/index.ts +1712 -0
  85. package/src/types.ts +37 -0
  86. package/tsconfig.json +19 -0
package/.gitattributes ADDED
@@ -0,0 +1,94 @@
1
+ ###############################################################################
2
+ # Core normalization
3
+ ###############################################################################
4
+ * text=auto eol=lf
5
+
6
+ # Ensure consistent line endings for scripts
7
+ *.sh text eol=lf
8
+ *.bash text eol=lf
9
+ *.ps1 text eol=lf
10
+ *.cmd text eol=crlf
11
+ *.bat text eol=crlf
12
+
13
+ ###############################################################################
14
+ # Binary handling
15
+ ###############################################################################
16
+ *.png binary
17
+ *.jpg binary
18
+ *.jpeg binary
19
+ *.gif binary
20
+ *.svg binary
21
+ *.ico binary
22
+ *.pdf binary
23
+ *.zip binary
24
+ *.tar binary
25
+ *.tar.gz binary
26
+ *.7z binary
27
+ *.docx binary
28
+ *.xlsx binary
29
+ *.pptx binary
30
+ *.mp3 binary
31
+ *.mp4 binary
32
+ *.woff binary
33
+ *.woff2 binary
34
+ *.ttf binary
35
+ *.otf binary
36
+
37
+ ###############################################################################
38
+ # Export control for GitHub Releases
39
+ # These paths will NOT appear in generated release archives
40
+ ###############################################################################
41
+ # CI and automation
42
+ .github/ export-ignore
43
+ .github/workflows/ export-ignore
44
+ .gitea/ export-ignore
45
+ .gitlab/ export-ignore
46
+
47
+ # Development and tooling
48
+ tests/ export-ignore
49
+ testing/ export-ignore
50
+ tmp/ export-ignore
51
+ docs-internal/ export-ignore
52
+ tools/ export-ignore
53
+
54
+ # Dependency folders that should not ship in release bundles
55
+ node_modules/ export-ignore
56
+ vendor-dev/ export-ignore
57
+
58
+ # Local environment and editor configs
59
+ *.local export-ignore
60
+ *.env export-ignore
61
+ *.env.example export-ignore
62
+ *.code-workspace export-ignore
63
+
64
+ # Project specific non release scaffolding
65
+ dev-assets/ export-ignore
66
+ analysis/ export-ignore
67
+ research/ export-ignore
68
+
69
+ ###############################################################################
70
+ # Linguistic settings for code statistics
71
+ ###############################################################################
72
+ *.css linguist-language=CSS
73
+ *.scss linguist-language=SCSS
74
+ *.js linguist-language=JavaScript
75
+ *.ts linguist-language=TypeScript
76
+ *.php linguist-language=PHP
77
+ *.xml linguist-language=XML
78
+ *.json linguist-language=JSON
79
+ *.ini linguist-language=INI
80
+ *.sql linguist-language=SQL
81
+ *.md linguist-language=Markdown
82
+
83
+ ###############################################################################
84
+ # Prevent diff noise for vendor or minified content
85
+ ###############################################################################
86
+ vendor/* -diff
87
+ *.min.js -diff
88
+ *.min.css -diff
89
+
90
+ ###############################################################################
91
+ # Lockdown for generated files
92
+ ###############################################################################
93
+ *.min.js linguist-generated=true
94
+ *.min.css linguist-generated=true
package/.gitmessage ADDED
@@ -0,0 +1,9 @@
1
+ # <type>(<scope>): <subject>
2
+ # types: build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test
3
+ # subject: imperative, lower-case, no trailing period
4
+
5
+ # Body: what and why
6
+
7
+ # BREAKING CHANGE: <description>
8
+ # Closes: #123
9
+ # Signed-off-by: <Your Name> <you@example.com>
@@ -0,0 +1,110 @@
1
+ ---
2
+ name: Architecture Decision Record (ADR)
3
+ about: Propose or document an architectural decision
4
+ title: '[ADR] '
5
+ labels: 'architecture, decision'
6
+ assignees: ''
7
+
8
+ ---
9
+
10
+
11
+ ## ADR Number
12
+ ADR-XXXX
13
+
14
+ ## Status
15
+ - [ ] Proposed
16
+ - [ ] Accepted
17
+ - [ ] Deprecated
18
+ - [ ] Superseded by ADR-XXXX
19
+
20
+ ## Context
21
+ Describe the issue or problem that motivates this decision.
22
+
23
+ ## Decision
24
+ State the architecture decision and provide rationale.
25
+
26
+ ## Consequences
27
+ ### Positive
28
+ - List positive consequences
29
+
30
+ ### Negative
31
+ - List negative consequences or trade-offs
32
+
33
+ ### Neutral
34
+ - List neutral aspects
35
+
36
+ ## Alternatives Considered
37
+ ### Alternative 1
38
+ - Description
39
+ - Pros
40
+ - Cons
41
+ - Why not chosen
42
+
43
+ ### Alternative 2
44
+ - Description
45
+ - Pros
46
+ - Cons
47
+ - Why not chosen
48
+
49
+ ## Implementation Plan
50
+ 1. Step 1
51
+ 2. Step 2
52
+ 3. Step 3
53
+
54
+ ## Stakeholders
55
+ - **Decision Makers**: @user1, @user2
56
+ - **Consulted**: @user3, @user4
57
+ - **Informed**: team-name
58
+
59
+ ## Technical Details
60
+ ### Architecture Diagram
61
+ ```
62
+ [Add diagram or link]
63
+ ```
64
+
65
+ ### Dependencies
66
+ - Dependency 1
67
+ - Dependency 2
68
+
69
+ ### Impact Analysis
70
+ - **Performance**: [Impact description]
71
+ - **Security**: [Impact description]
72
+ - **Scalability**: [Impact description]
73
+ - **Maintainability**: [Impact description]
74
+
75
+ ## Testing Strategy
76
+ - [ ] Unit tests
77
+ - [ ] Integration tests
78
+ - [ ] Performance tests
79
+ - [ ] Security tests
80
+
81
+ ## Documentation
82
+ - [ ] Architecture documentation updated
83
+ - [ ] API documentation updated
84
+ - [ ] Developer guide updated
85
+ - [ ] Runbook created
86
+
87
+ ## Migration Path
88
+ Describe how to migrate from current state to new architecture.
89
+
90
+ ## Rollback Plan
91
+ Describe how to rollback if issues occur.
92
+
93
+ ## Timeline
94
+ - **Proposal Date**:
95
+ - **Decision Date**:
96
+ - **Implementation Start**:
97
+ - **Expected Completion**:
98
+
99
+ ## References
100
+ - Related ADRs:
101
+ - External resources:
102
+ - RFCs:
103
+
104
+ ## Review Checklist
105
+ - [ ] Aligns with enterprise architecture principles
106
+ - [ ] Security implications reviewed
107
+ - [ ] Performance implications reviewed
108
+ - [ ] Cost implications reviewed
109
+ - [ ] Compliance requirements met
110
+ - [ ] Team consensus achieved
@@ -0,0 +1,48 @@
1
+ ---
2
+ name: Bug Report
3
+ about: Report a bug or issue with the project
4
+ title: '[BUG] '
5
+ labels: 'bug'
6
+ assignees: ''
7
+
8
+ ---
9
+
10
+
11
+ ## Bug Description
12
+ A clear and concise description of what the bug is.
13
+
14
+ ## Steps to Reproduce
15
+ 1. Go to '...'
16
+ 2. Click on '...'
17
+ 3. Scroll down to '...'
18
+ 4. See error
19
+
20
+ ## Expected Behavior
21
+ A clear and concise description of what you expected to happen.
22
+
23
+ ## Actual Behavior
24
+ A clear and concise description of what actually happened.
25
+
26
+ ## Screenshots
27
+ If applicable, add screenshots to help explain your problem.
28
+
29
+ ## Environment
30
+ - **Project**: [e.g., MokoDoliTools, moko-cassiopeia]
31
+ - **Version**: [e.g., 1.2.3]
32
+ - **Platform**: [e.g., Dolibarr 18.0, Joomla 5.0]
33
+ - **PHP Version**: [e.g., 8.1]
34
+ - **Database**: [e.g., MySQL 8.0, PostgreSQL 14]
35
+ - **Browser** (if applicable): [e.g., Chrome 120, Firefox 121]
36
+ - **OS**: [e.g., Ubuntu 22.04, Windows 11]
37
+
38
+ ## Additional Context
39
+ Add any other context about the problem here.
40
+
41
+ ## Possible Solution
42
+ If you have suggestions on how to fix the issue, please describe them here.
43
+
44
+ ## Checklist
45
+ - [ ] I have searched for similar issues before creating this one
46
+ - [ ] I have provided all the requested information
47
+ - [ ] I have tested this on the latest stable version
48
+ - [ ] I have checked the documentation and couldn't find a solution
@@ -0,0 +1,18 @@
1
+ ---
2
+ blank_issues_enabled: true
3
+ contact_links:
4
+ - name: 💼 Enterprise Support
5
+ url: https://mokoconsulting.tech/enterprise
6
+ about: Enterprise-level support and consultation services
7
+ - name: 💬 Ask a Question
8
+ url: https://mokoconsulting.tech/
9
+ about: Get help or ask questions through our website
10
+ - name: 📚 MokoStandards Documentation
11
+ url: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
12
+ about: View our coding standards and best practices
13
+ - name: 🔒 Report a Security Vulnerability
14
+ url: https://git.mokoconsulting.tech/mokoconsulting-tech/.github-private/security/advisories/new
15
+ about: Report security vulnerabilities privately (for critical issues)
16
+ - name: 💡 Community Discussions
17
+ url: https://github.com/orgs/mokoconsulting-tech/discussions
18
+ about: Join community discussions and Q&A
@@ -0,0 +1,52 @@
1
+ ---
2
+ name: Documentation Issue
3
+ about: Report an issue with documentation
4
+ title: '[DOCS] '
5
+ labels: 'documentation'
6
+ assignees: ''
7
+
8
+ ---
9
+
10
+
11
+ ## Documentation Issue
12
+
13
+ **Location**:
14
+ <!-- Specify the file, page, or section with the issue -->
15
+
16
+ ## Issue Type
17
+ <!-- Mark the relevant option with an "x" -->
18
+ - [ ] Typo or grammar error
19
+ - [ ] Outdated information
20
+ - [ ] Missing documentation
21
+ - [ ] Unclear explanation
22
+ - [ ] Broken links
23
+ - [ ] Missing examples
24
+ - [ ] Other (specify below)
25
+
26
+ ## Description
27
+ <!-- Clearly describe the documentation issue -->
28
+
29
+ ## Current Content
30
+ <!-- Quote or describe the current documentation (if applicable) -->
31
+ ```
32
+ Current text here
33
+ ```
34
+
35
+ ## Suggested Improvement
36
+ <!-- Provide your suggestion for how to improve the documentation -->
37
+ ```
38
+ Suggested text here
39
+ ```
40
+
41
+ ## Additional Context
42
+ <!-- Add any other context, screenshots, or references -->
43
+
44
+ ## Standards Alignment
45
+ - [ ] Follows MokoStandards documentation guidelines
46
+ - [ ] Uses en_US/en_GB localization
47
+ - [ ] Includes proper SPDX headers where applicable
48
+
49
+ ## Checklist
50
+ - [ ] I have searched for similar documentation issues
51
+ - [ ] I have provided a clear description
52
+ - [ ] I have suggested an improvement (if applicable)
@@ -0,0 +1,85 @@
1
+ ---
2
+ name: Enterprise Support Request
3
+ about: Request enterprise-level support or consultation
4
+ title: '[ENTERPRISE] '
5
+ labels: 'enterprise, support'
6
+ assignees: ''
7
+
8
+ ---
9
+
10
+
11
+ ## Support Request Type
12
+ - [ ] Critical Production Issue
13
+ - [ ] Performance Optimization
14
+ - [ ] Security Audit
15
+ - [ ] Architecture Review
16
+ - [ ] Custom Development
17
+ - [ ] Migration Support
18
+ - [ ] Training & Onboarding
19
+ - [ ] Other (please specify)
20
+
21
+ ## Priority Level
22
+ - [ ] P0 - Critical (Production Down)
23
+ - [ ] P1 - High (Major Feature Broken)
24
+ - [ ] P2 - Medium (Non-Critical Issue)
25
+ - [ ] P3 - Low (Enhancement/Question)
26
+
27
+ ## Organization Details
28
+ - **Company Name**:
29
+ - **Contact Person**:
30
+ - **Email**:
31
+ - **Phone** (for P0/P1 issues):
32
+ - **Timezone**:
33
+
34
+ ## Issue Description
35
+ Provide a clear and detailed description of your request or issue.
36
+
37
+ ## Business Impact
38
+ Describe the impact on your business operations:
39
+ - Number of users affected:
40
+ - Revenue impact (if applicable):
41
+ - Deadline/SLA requirements:
42
+
43
+ ## Environment Details
44
+ - **Deployment Type**: [On-Premise / Cloud / Hybrid]
45
+ - **Platform**: [Joomla / Dolibarr / Custom]
46
+ - **Version**:
47
+ - **Infrastructure**: [AWS / Azure / GCP / Other]
48
+ - **Scale**: [Users / Transactions / Data Volume]
49
+
50
+ ## Current Configuration
51
+ ```yaml
52
+ # Paste relevant configuration (sanitize sensitive data)
53
+ ```
54
+
55
+ ## Logs and Diagnostics
56
+ ```
57
+ # Paste relevant logs (sanitize sensitive data)
58
+ ```
59
+
60
+ ## Attempted Solutions
61
+ Describe any troubleshooting steps already taken.
62
+
63
+ ## Expected Resolution
64
+ Describe your expected outcome or resolution.
65
+
66
+ ## Additional Resources
67
+ - **Documentation Links**:
68
+ - **Related Issues**:
69
+ - **Screenshots/Videos**:
70
+
71
+ ## Enterprise SLA
72
+ - [ ] Standard Support (initial response within 1–3 weeks)
73
+ - [ ] Premium Support (initial response within 5 business days)
74
+ - [ ] Critical Support (initial response within 72 hours)
75
+ - [ ] Custom SLA (specify):
76
+
77
+ ## Compliance Requirements
78
+ - [ ] GDPR
79
+ - [ ] HIPAA
80
+ - [ ] SOC 2
81
+ - [ ] ISO 27001
82
+ - [ ] Other (specify):
83
+
84
+ ---
85
+ **Note**: Enterprise support requests require an active support contract. If you don't have one, please contact us at enterprise@mokoconsulting.tech
@@ -0,0 +1,51 @@
1
+ ---
2
+ name: Feature Request
3
+ about: Suggest a new feature or enhancement
4
+ title: '[FEATURE] '
5
+ labels: 'enhancement'
6
+ assignees: ''
7
+
8
+ ---
9
+
10
+
11
+ ## Feature Description
12
+ A clear and concise description of the feature you'd like to see.
13
+
14
+ ## Problem or Use Case
15
+ Describe the problem this feature would solve or the use case it addresses.
16
+ Ex. I'm always frustrated when [...]
17
+
18
+ ## Proposed Solution
19
+ A clear and concise description of what you want to happen.
20
+
21
+ ## Alternative Solutions
22
+ A clear and concise description of any alternative solutions or features you've considered.
23
+
24
+ ## Benefits
25
+ Describe how this feature would benefit users:
26
+ - Who would use this feature?
27
+ - What problems does it solve?
28
+ - What value does it add?
29
+
30
+ ## Implementation Details (Optional)
31
+ If you have ideas about how this could be implemented, share them here:
32
+ - Technical approach
33
+ - Files/components that might need changes
34
+ - Any concerns or challenges you foresee
35
+
36
+ ## Additional Context
37
+ Add any other context, mockups, or screenshots about the feature request here.
38
+
39
+ ## Relevant Standards
40
+ Does this relate to any standards in [MokoStandards](https://git.mokoconsulting.tech/MokoConsulting/MokoStandards)?
41
+ - [ ] Accessibility (WCAG 2.1 AA)
42
+ - [ ] Localization (en_US/en_GB)
43
+ - [ ] Security best practices
44
+ - [ ] Code quality standards
45
+ - [ ] Other: [specify]
46
+
47
+ ## Checklist
48
+ - [ ] I have searched for similar feature requests before creating this one
49
+ - [ ] I have clearly described the use case and benefits
50
+ - [ ] I have considered alternative solutions
51
+ - [ ] This feature aligns with the project's goals and scope
@@ -0,0 +1,190 @@
1
+ ---
2
+ name: Firewall Request
3
+ about: Request firewall rule changes or access to external resources
4
+ title: '[FIREWALL] [Resource Name] - [Brief Description]'
5
+ labels: ['firewall-request', 'infrastructure', 'security']
6
+ assignees: ['jmiller']
7
+ ---
8
+
9
+
10
+ ## Firewall Request
11
+
12
+ ### Request Type
13
+ - [ ] Allow outbound access to external service/API
14
+ - [ ] Allow inbound access from external source
15
+ - [ ] Modify existing firewall rule
16
+ - [ ] Remove/revoke firewall rule
17
+ - [ ] Other (specify):
18
+
19
+ ### Resource Information
20
+ **Service/Domain Name**:
21
+ **IP Address(es)**:
22
+ **Port(s)**:
23
+ **Protocol**:
24
+ - [ ] HTTP (80)
25
+ - [ ] HTTPS (443)
26
+ - [ ] SSH (22)
27
+ - [ ] FTP (21)
28
+ - [ ] SFTP (22)
29
+ - [ ] Custom (specify): _______________
30
+
31
+ ### Requestor Information
32
+ **Name**:
33
+ **GitHub Username**: @
34
+ **Email**: @mokoconsulting.tech
35
+ **Team/Department**:
36
+ **Manager**: @
37
+
38
+ ### Business Justification
39
+ **Why is this access needed?**
40
+
41
+ **Which project(s) require this access?**
42
+
43
+ **What functionality will break without this access?**
44
+
45
+ **Is there an alternative solution?**
46
+ - [ ] Yes (explain):
47
+ - [ ] No
48
+
49
+ ### Security Considerations
50
+ **Data Classification**:
51
+ - [ ] Public
52
+ - [ ] Internal
53
+ - [ ] Confidential
54
+ - [ ] Restricted
55
+
56
+ **Sensitive Data Transmission**:
57
+ - [ ] No sensitive data will be transmitted
58
+ - [ ] Sensitive data will be transmitted (encryption required)
59
+ - [ ] Authentication credentials will be transmitted (secure storage required)
60
+
61
+ **Third-Party Service**:
62
+ - [ ] This is a trusted/verified third-party service
63
+ - [ ] This is a new/unverified service (security review required)
64
+
65
+ **Service Documentation**:
66
+ (Provide link to service documentation or API specs)
67
+
68
+ ### Access Scope
69
+ **Affected Systems**:
70
+ - [ ] Development environment only
71
+ - [ ] Staging environment only
72
+ - [ ] Production environment
73
+ - [ ] All environments
74
+
75
+ **Access Duration**:
76
+ - [ ] Permanent (ongoing business need)
77
+ - [ ] Temporary (specify end date): _______________
78
+ - [ ] Testing only (specify duration): _______________
79
+
80
+ ### Technical Details
81
+ **Source System(s)**:
82
+ (Which internal systems need access?)
83
+
84
+ **Destination System(s)**:
85
+ (Which external systems need to be accessed?)
86
+
87
+ **Expected Traffic Volume**:
88
+ (e.g., requests per hour/day)
89
+
90
+ **Traffic Pattern**:
91
+ - [ ] Continuous
92
+ - [ ] Periodic (specify frequency): _______________
93
+ - [ ] On-demand/manual
94
+ - [ ] Scheduled (specify schedule): _______________
95
+
96
+ ### Testing Requirements
97
+ **Pre-Production Testing**:
98
+ - [ ] Request includes dev/staging access for testing
99
+ - [ ] Testing can be done with production access only
100
+ - [ ] No testing required (modify existing rule)
101
+
102
+ **Testing Plan**:
103
+
104
+ **Rollback Plan**:
105
+ (What happens if access needs to be revoked?)
106
+
107
+ ### Compliance & Audit
108
+ **Compliance Requirements**:
109
+ - [ ] GDPR considerations
110
+ - [ ] SOC 2 compliance required
111
+ - [ ] PCI DSS considerations
112
+ - [ ] Other regulatory requirements: _______________
113
+ - [ ] No specific compliance requirements
114
+
115
+ **Audit/Logging Requirements**:
116
+ - [ ] Standard logging sufficient
117
+ - [ ] Enhanced logging/monitoring required
118
+ - [ ] Real-time alerting required
119
+
120
+ ### Urgency
121
+ - [ ] Critical (production down, immediate access needed)
122
+ - [ ] High (needed within 24 hours)
123
+ - [ ] Normal (needed within 1 week)
124
+ - [ ] Low priority (needed within 1 month)
125
+
126
+ **If critical/high urgency, explain why:**
127
+
128
+ ### Approvals
129
+ **Manager Approval**:
130
+ - [ ] Manager has been notified and approves this request
131
+
132
+ **Security Team Review Required**:
133
+ - [ ] Yes (new external service, sensitive data)
134
+ - [ ] No (minor change, established service)
135
+
136
+ ### Additional Information
137
+
138
+ **Related Documentation**:
139
+ (Links to relevant docs, RFCs, tickets, etc.)
140
+
141
+ **Dependencies**:
142
+ (Other systems or changes this depends on)
143
+
144
+ **Comments/Questions**:
145
+
146
+ ---
147
+
148
+ ## For Infrastructure/Security Team Use Only
149
+
150
+ **Do not edit below this line**
151
+
152
+ ### Security Review
153
+ - [ ] Security team review completed
154
+ - [ ] Risk assessment: Low / Medium / High
155
+ - [ ] Encryption required: Yes / No
156
+ - [ ] VPN required: Yes / No
157
+ - [ ] Additional security controls: _______________
158
+
159
+ **Reviewed By**: @_______________
160
+ **Review Date**: _______________
161
+ **Review Notes**:
162
+
163
+ ### Implementation
164
+ - [ ] Firewall rule created/modified
165
+ - [ ] Rule tested in dev/staging
166
+ - [ ] Rule deployed to production
167
+ - [ ] Monitoring/alerting configured
168
+ - [ ] Documentation updated
169
+
170
+ **Firewall Rule ID**: _______________
171
+ **Implementation Date**: _______________
172
+ **Implemented By**: @_______________
173
+
174
+ **Configuration Details**:
175
+ ```
176
+ Source:
177
+ Destination:
178
+ Port/Protocol:
179
+ Action: Allow/Deny
180
+ ```
181
+
182
+ ### Verification
183
+ - [ ] Requestor confirmed access working
184
+ - [ ] Logs reviewed (no anomalies)
185
+ - [ ] Security scan completed (if applicable)
186
+
187
+ **Verification Date**: _______________
188
+ **Verified By**: @_______________
189
+
190
+ ### Notes
@@ -0,0 +1,48 @@
1
+ ---
2
+ name: API Integration Request
3
+ about: Request integration with a new REST API or service
4
+ title: '[API] '
5
+ labels: 'enhancement, api-integration'
6
+ assignees: ''
7
+
8
+ ---
9
+
10
+ ## API Integration Request
11
+
12
+ ### Target API
13
+ - **Service Name**: [e.g., Akeeba Backup, Joomla Web Services]
14
+ - **API Documentation**: [URL to API docs]
15
+ - **API Type**: [REST / GraphQL / SOAP]
16
+ - **Authentication**: [API Key / OAuth / Bearer Token / Basic Auth]
17
+
18
+ ### Proposed Tools
19
+ List the MCP tools this integration would provide:
20
+
21
+ | Tool Name | HTTP Method | Endpoint | Description |
22
+ |---|---|---|---|
23
+ | `service_list` | GET | `/api/items` | List all items |
24
+ | `service_get` | GET | `/api/items/{id}` | Get single item |
25
+ | `service_create` | POST | `/api/items` | Create item |
26
+
27
+ ### Multi-Connection
28
+ - [ ] Single instance only
29
+ - [ ] Multiple instances (production, staging, dev)
30
+ - [ ] Multi-tenant (one connection per client)
31
+
32
+ ### Use Case
33
+ Describe the workflow this integration enables for AI assistants.
34
+
35
+ ### Priority
36
+ - [ ] Critical — blocking current work
37
+ - [ ] High — needed soon
38
+ - [ ] Medium — would improve workflow
39
+ - [ ] Low — nice to have
40
+
41
+ ### Existing Alternatives
42
+ Are there other ways to accomplish this today? If so, why is an MCP integration better?
43
+
44
+ ### Checklist
45
+ - [ ] API documentation is available and accessible
46
+ - [ ] API supports the required authentication method
47
+ - [ ] I have tested the API endpoints manually
48
+ - [ ] The integration follows the Template-MCP architecture pattern