MokoConsulting/MokoJoomBackup
1
0
Fork 0
Code Issues 31 Pull Requests 1 Packages Projects Releases 1 Wiki Activity

Feature: update mcp_mokobackup MCP server for MokoJoomBackup endpoints #21

New Issue
Open
opened 2026-06-02 20:29:34 +00:00 by jmiller · 3 comments
jmiller commented 2026-06-02 20:29:34 +00:00
Owner
Copy Link
Copy Source

Update the mcp_mokobackup MCP server to support MokoJoomBackup's REST API alongside Akeeba.

Description

The existing mcp_mokobackup MCP server talks to Akeeba's /api/index.php/v1/akeebabackup/ endpoints. Update it to support MokoJoomBackup's /api/index.php/v1/mokobackup/ endpoints.

Requirements

  • Add mokobackup target type alongside akeeba
  • Detect endpoint format based on target config
  • All 5 MCP tools work with MokoJoomBackup backend
  • Backwards compatible with existing Akeeba targets
Update the mcp_mokobackup MCP server to support MokoJoomBackup's REST API alongside Akeeba. ## Description The existing mcp_mokobackup MCP server talks to Akeeba's `/api/index.php/v1/akeebabackup/` endpoints. Update it to support MokoJoomBackup's `/api/index.php/v1/mokobackup/` endpoints. ## Requirements - [ ] Add mokobackup target type alongside akeeba - [ ] Detect endpoint format based on target config - [ ] All 5 MCP tools work with MokoJoomBackup backend - [ ] Backwards compatible with existing Akeeba targets
jmiller added the type: featurepriority: highcomponent: apistatus: ready labels 2026-06-02 20:29:34 +00:00
jmiller commented 2026-06-02 20:29:34 +00:00
Author
Owner
Copy Link
Copy Source

Testing Plan

TC-F8.1: MCP tool compatibility

  1. Configure mcp_mokobackup with a MokoJoomBackup target
  2. Test each tool:
    • akeeba_list → should list MokoJoomBackup records
    • akeeba_backup → should start a MokoJoomBackup backup
    • akeeba_profiles → should list MokoJoomBackup profiles
    • akeeba_download → should download archive
    • akeeba_delete → should delete record

TC-F8.2: Backwards compatibility

  1. Keep existing Akeeba target configs
  2. Verify they still work alongside MokoJoomBackup targets

TC-F8.3: Auto-detection

  1. Test with both endpoint formats
  2. Verify correct API path used based on target type
## Testing Plan **TC-F8.1: MCP tool compatibility** 1. Configure mcp_mokobackup with a MokoJoomBackup target 2. Test each tool: - akeeba_list → should list MokoJoomBackup records - akeeba_backup → should start a MokoJoomBackup backup - akeeba_profiles → should list MokoJoomBackup profiles - akeeba_download → should download archive - akeeba_delete → should delete record **TC-F8.2: Backwards compatibility** 1. Keep existing Akeeba target configs 2. Verify they still work alongside MokoJoomBackup targets **TC-F8.3: Auto-detection** 1. Test with both endpoint formats 2. Verify correct API path used based on target type
jmiller reopened this issue 2026-06-05 00:15:51 +00:00
jmiller commented 2026-06-05 00:16:38 +00:00
Author
Owner
Copy Link
Copy Source

Status: pending testing

Status: **pending testing**
jmiller commented 2026-06-05 00:16:56 +00:00
Author
Owner
Copy Link
Copy Source

Status: pending testing

Status: **pending testing**
Sign in to join this conversation.
Labels
Clear labels
component: admin
Admin UI and views
 component: api
REST API
 component: engine
Backup/restore engine
 component: remote
Remote storage (FTP/GDrive)
 component: scheduler
Scheduled tasks
 priority: critical
Must fix before release
 priority: high
Important for release
 priority: low
Nice to have
 priority: medium
Normal priority
 status: blocked
Blocked by dependency
 status: ready
Ready for development
 type: bug
Something is broken
 type: docs
Documentation
 type: feature
New feature or enhancement
 type: testing
Testing and QA
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 pending: dependency
Blocked by another issue or external dependency
 pending: deployment
Tested and approved, awaiting deployment to production
 pending: design
Needs UI/UX or architecture design before implementation
 pending: documentation
Feature works, needs documentation/wiki update
 pending: feedback
Awaiting feedback or decision from stakeholder
 pending: review
Implementation complete, awaiting code review
 pending: testing
Feature implemented but not yet tested
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels component: api priority: high status: ready type: feature
Type —
Status —
Priority —
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoJoomBackup#21
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?