🔄 Refactor API endpoints to use MCP resources vs tools (v0.3.0)
ARCHITECTURAL IMPROVEMENT: Proper separation of concerns in MCP design
📖 RESOURCES (Read-only data retrieval):
- mailu://users - All users
- mailu://domains - All domains
- mailu://aliases - All aliases
- mailu://alternative-domains - All alternative domains
- mailu://relays - All relays
- mailu://user/{email} - Specific user details
- mailu://domain/{domain} - Specific domain details
- mailu://alias/{alias} - Specific alias details
- mailu://alternative-domain/{alt} - Specific alternative domain
- mailu://relay/{name} - Specific relay details
- mailu://domain/{domain}/users - Users in specific domain
- mailu://domain/{domain}/managers - Managers for specific domain
- mailu://domain/{domain}/manager/{email} - Specific manager details
- mailu://alias/destination/{domain} - Aliases by destination domain
⚡ TOOLS (Actions and modifications):
- create_user, update_user, delete_user
- create_domain, update_domain, delete_domain, generate_dkim_keys
- create_domain_manager, delete_domain_manager
- create_alias, update_alias, delete_alias
- create_alternative_domain, delete_alternative_domain
- create_relay, update_relay, delete_relay
✨ BENEFITS:
- Better UX: Resources are discoverable and browsable
- Cleaner separation: Read vs Write operations
- Structured data: Resources return properly formatted JSON
- URI-based access: RESTful resource addressing
- Improved performance: Resources can be cached by clients
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Ryan Malloy
3fe5bb02ad