- 11 Dec, 2025 26 commits
-
-
Ean Schuessler committed
-
Ean Schuessler committed
-
Ean Schuessler committed
-
Ean Schuessler committed
-
Ean Schuessler committed
-
Ean Schuessler committed
-
Ean Schuessler committed
-
Ean Schuessler committed
-
Ean Schuessler committed
-
Ean Schuessler committed
-
Ean Schuessler committed
-
Ean Schuessler committed
-
Ean Schuessler committed
-
Ean Schuessler committed
-
Ean Schuessler committed
-
Ean Schuessler committed
-
Ean Schuessler committed
-
Ean Schuessler committed
-
Ean Schuessler committed
-
Ean Schuessler committed
-
Ean Schuessler committed
-
Ean Schuessler committed
-
- Add YouTube video link: Moqui MCP 2025-12-08 - Document what demo shows: screen navigation, data analysis, business insights - Highlight key success: color availability discovery (blue/black only) - Include technical details: GLM-4.6, MCP v2.0.1, containerized environment - Validate that MCP integration enables meaningful AI-ERP interaction Demo provides real-world evidence of capabilities working in practice.
Ean Schuessler committed -
- Add prominent WARNING: THIS DOG MAY EAT YOUR HOMEWORK - Document all security vulnerabilities and attack vectors - Explain how LLM with ADMIN access can destroy the system - Provide mandatory safety requirements (containers, limited users, isolation) - Remove irresponsible 'production-ready' language - Add message to AI creators about warm fuzzies being dangerous This MCP implementation gives LLMs god-mode access to entire ERP system. Extreme caution required - never deploy with ADMIN access in production.
Ean Schuessler committed
-
- 08 Dec, 2025 4 commits
-
-
- Complete project overview and feature description - Quick start guide with installation and usage instructions - Tool examples for catalog, order, customer, and pricing management - Configuration details for server and security setup - Testing guide with test suite structure and examples - Development documentation with project structure - API reference for MCP protocol methods - Security considerations and performance notes - Troubleshooting guide for common issues - Contributing guidelines and license information
Ean Schuessler committed -
Ean Schuessler committed
-
- Add comprehensive logging for MCP service calls (EXECUTESCREEN, SCREENASTOOL, ToolsCall) - Update instructions to include Product_EditPrices tool for price checking - Change default render mode to 'html' for better screen output - Temporarily disable visit.update() to reduce database overhead during debugging - Improve parameter passing for screen execution tools
Ean Schuessler committed -
- Remove duplicate code blocks for screen tool execution - Simplify protocolMethodMappings to directly route MCP methods to services - Clean up tools/call special handling with single, unified flow - Preserve all existing functionality for recursive screen discovery
Ean Schuessler committed
-
- 07 Dec, 2025 10 commits
-
-
- Fixed line 153: protocolMethodMappings[name]} → protocolMethodMappings[name]} - Resolves 'Unexpected input: }' @ line 160, column 17' compilation error - Allows service to compile and run properly - Session handling issue still needs investigation
Ean Schuessler committed -
- Simplify tool name decoding logic to handle different naming conventions - Remove complex regex patterns that may cause Groovy compilation issues - Add debug logging to track decoding behavior - Tool names like screen_PopCommerce_screen_PopCommerceAdmin_Catalog.Product_FindProduct should now decode correctly - This should resolve 'Service returned null result' errors for complex screen tools
Ean Schuessler committed -
- Fixed line 200: result.result = [...] → result = [...] - Fixed line 310: result.result = [...] → result = [...] - Ensures all MCP services return flat structure for JSON-RPC response - Combined with callMcpService fix to eliminate all double nesting issues - Should resolve opencode client 'Typeundefined is not an object (evaluating result.content)' error - MCP response now has correct structure: result.content = [...] direct access
Ean Schuessler committed -
- tools/call was incorrectly nesting ScreenAsMcpTool result: result.result = [content: ...] - ScreenAsMcpTool already returns correct structure: result = [content: ...] - Creates nested result.result.result which breaks MCP spec and client parsing - Fix: Extract content directly from serviceResult.result instead of nesting - Resolves opencode client error: 'Typeundefined is not an object (evaluating result.content)' - Now result.content correctly accesses content array as expected by MCP clients
Ean Schuessler committed -
- Change default renderMode from 'html' to 'text' for screen tools - Reduces response size from 89KB to 5.6KB for FindProduct screen - Returns clean table data instead of complex HTML forms with JavaScript - Makes screen tool output LLM-friendly and resolves opencode client parsing issues - Text format shows actual data in readable table format perfect for AI consumption
Ean Schuessler committed -
- Previous edit incorrectly placed variable definition inside JSON map literal - Move actualResult assignment outside JsonOutput.toJson call - Resolves build error: Unexpected input '(' @ line 537Ean Schuessler committed -
- SSE handler was returning generic status message instead of actual service result - Extract actualResult from service response (same as regular HTTP handler) - Tool calls now return proper content including screen execution results - Fixes issue where tools worked but results didn't reach opencode client
Ean Schuessler committed -
- Move list#Tools recursive screen processing logs to debug level - Move ResourcesList entity discovery logs to debug level - Keep high-level summary logs at info level for operational visibility - Significantly reduces log noise during normal MCP operations
Ean Schuessler committed -
Ean Schuessler committed
-
