MokoConsulting/mcp-mokowaas-api
1
0
Fork 0
Code Issues 1 Pull Requests Releases 2 Wiki Activity

Rebrand MokoWaaS → MokoSuite across MCP server #18

New Issue
Open
opened 2026-06-07 14:18:22 +00:00 by jmiller · 2 comments
jmiller commented 2026-06-07 14:18:22 +00:00
Owner
Copy Link
Copy Source

Summary

The entire platform has been rebranded from MokoWaaS to MokoSuite (including the base Layer 0). This MCP server needs to be updated to reflect the new branding.

What Needs Updating

Repo-Level

  • Rename repo from mcp-mokowaas-api to mcp-mokosuite-api
  • Update repo description
  • Update topics

Source Code

  • Rename all mokowaas references in source files to mokosuite
  • Update API endpoint paths (e.g., /v1/mokowaas/ → /v1/mokosuite/)
  • Update tool names and descriptions
  • Update README and documentation
  • Update package.json name and description

Configuration

  • Update any hardcoded MokoWaaS references in config files
  • Update connection naming conventions

Context

  • Rebrand decided 2026-06-07
  • All 8 suite repos already renamed (MokoSuiteCRM, MokoSuiteERP, etc.)
  • Layer 0 base platform also renamed from MokoWaaS to MokoSuite
## Summary The entire platform has been rebranded from MokoWaaS to MokoSuite (including the base Layer 0). This MCP server needs to be updated to reflect the new branding. ## What Needs Updating ### Repo-Level - Rename repo from `mcp-mokowaas-api` to `mcp-mokosuite-api` - Update repo description - Update topics ### Source Code - Rename all `mokowaas` references in source files to `mokosuite` - Update API endpoint paths (e.g., `/v1/mokowaas/` → `/v1/mokosuite/`) - Update tool names and descriptions - Update README and documentation - Update package.json name and description ### Configuration - Update any hardcoded MokoWaaS references in config files - Update connection naming conventions ## Context - Rebrand decided 2026-06-07 - All 8 suite repos already renamed (MokoSuiteCRM, MokoSuiteERP, etc.) - Layer 0 base platform also renamed from MokoWaaS to MokoSuite
jmiller commented 2026-06-07 14:18:29 +00:00
Author
Owner
Copy Link
Copy Source

Branch created: feature/18-rebrand-mokowaas-mokosuite-across-mcp-se

git fetch origin
git checkout feature/18-rebrand-mokowaas-mokosuite-across-mcp-se
Branch created: [`feature/18-rebrand-mokowaas-mokosuite-across-mcp-se`](https://git.mokoconsulting.tech/MokoConsulting/mcp-mokowaas-api/src/branch/feature/18-rebrand-mokowaas-mokosuite-across-mcp-se) ```bash git fetch origin git checkout feature/18-rebrand-mokowaas-mokosuite-across-mcp-se ```
jmiller commented 2026-06-07 16:46:37 +00:00
Author
Owner
Copy Link
Copy Source

Rebrand Checklist

All suite repos have been rebranded and use mokosuite in their API routes (v1/mokosuite/crm/..., v1/mokosuite/erp/..., etc.). This MCP server needs to match.

Files to Update

  • package.json — name, description
  • README.md — all references
  • src/ — tool names, descriptions, endpoint URLs
  • Replace all mokowaas → mokosuite in source
  • Replace all MokoWaaS → MokoSuite in source
  • Update API endpoint paths: /v1/mokowaas/ → /v1/mokosuite/

Gitea Repo

  • Rename repo: mcp-mokowaas-api → mcp-mokosuite-api
  • Update repo description
  • Update topics

Claude Code Config

  • Update .claude/settings.json or .mcp.json with new server name
  • Update any hardcoded server references

API Route Mapping (current → new)

All suite API routes now use this pattern:

v1/mokosuite/crm/products
v1/mokosuite/crm/orders
v1/mokosuite/erp/accounts
v1/mokosuite/erp/payment-gateways
v1/mokosuite/pos/sessions
v1/mokosuite/shop/reviews
v1/mokosuite/mrp/quality
v1/mokosuite/hrm/payroll
v1/mokosuite/restaurant/kds
v1/mokosuite/child/checkin

The MCP server tools should reflect these routes.

## Rebrand Checklist All suite repos have been rebranded and use `mokosuite` in their API routes (`v1/mokosuite/crm/...`, `v1/mokosuite/erp/...`, etc.). This MCP server needs to match. ### Files to Update - [ ] `package.json` — name, description - [ ] `README.md` — all references - [ ] `src/` — tool names, descriptions, endpoint URLs - [ ] Replace all `mokowaas` → `mokosuite` in source - [ ] Replace all `MokoWaaS` → `MokoSuite` in source - [ ] Update API endpoint paths: `/v1/mokowaas/` → `/v1/mokosuite/` ### Gitea Repo - [ ] Rename repo: `mcp-mokowaas-api` → `mcp-mokosuite-api` - [ ] Update repo description - [ ] Update topics ### Claude Code Config - [ ] Update `.claude/settings.json` or `.mcp.json` with new server name - [ ] Update any hardcoded server references ### API Route Mapping (current → new) All suite API routes now use this pattern: ``` v1/mokosuite/crm/products v1/mokosuite/crm/orders v1/mokosuite/erp/accounts v1/mokosuite/erp/payment-gateways v1/mokosuite/pos/sessions v1/mokosuite/shop/reviews v1/mokosuite/mrp/quality v1/mokosuite/hrm/payroll v1/mokosuite/restaurant/kds v1/mokosuite/child/checkin ``` The MCP server tools should reflect these routes.
Sign in to join this conversation.
Labels
Clear labels
automation
Automated processes or scripts
 breaking-change
Breaking API or functionality change
 build
Build system changes
 ci-cd
CI/CD pipeline changes
 config
Configuration file changes
 css
CSS/styling changes
 dependencies
Dependency updates
 deploy-failure
Automated deploy failure tracking
 docker
Docker configuration changes
 documentation
Documentation changes
 dolibarr
Dolibarr module or extension
 generic
Generic project or library
 good first issue
Good for newcomers
 health-check
Repository health check results
 health: excellent
Health score 90-100
 health: fair
Health score 50-69
 health: good
Health score 70-89
 health: poor
Health score below 50
 help wanted
Extra attention needed
 html
HTML template changes
 javascript
JavaScript code changes
 joomla
Joomla extension or component
 mokostandards
MokoStandards compliance
 needs-review
Awaiting code review
 php
PHP code changes
 push-failure
File push failure requiring attention
 python
Python code changes
 security
Security-related changes
 size/l
Large change (101-300 lines)
 size/m
Medium change (31-100 lines)
 size/s
Small change (11-30 lines)
 size/xl
Extra large change (301-1000 lines)
 size/xs
Extra small change (1-10 lines)
 size/xxl
Extremely large change (1000+ lines)
 standards-drift
Repository drifted from MokoStandards
 standards-update
MokoStandards sync update
 sync-failure
Bulk sync failure requiring attention
 sync-report
Bulk sync run report
 template-validation-failure
Template workflow validation failure
 tests
Test suite changes
 type: bug
Something isn't working
 type: chore
Maintenance tasks
 type: enhancement
Enhancement to existing feature
 type: feature
New feature or request
 type: refactor
Code refactoring
 type: version
Version-related change
 typescript
TypeScript code changes
 version
Version bump or release
 version-drift
Version mismatch detected
 work-in-progress
Work in progress, not ready for merge
No labels
Priority -
Type -
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/mcp-mokowaas-api#18
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?