Genexus18MCP
Enables AI assistants to directly read, edit, and analyze GeneXus 18 knowledge base objects, reducing manual context switching and accelerating code review, …
GeneXus 18 MCP server for Claude, Cursor, and AI agents — read, edit, analyze KB objects (transactions, web panels, procedures, SDTs) over the Model Context Protocol.
- Ask Claude to analyze a GeneXus transaction for redundant fields and suggest consolidations.
- Generate documentation for existing SDT structures by extracting attributes and relationships.
- Find all procedure dependencies across your knowledge base to plan refactoring work.
Enables AI assistants to directly read, edit, and analyze GeneXus 18 knowledge base objects, reducing manual context switching and accelerating code review, refactoring, and maintenance workflows for teams using the GeneXus low-code platform.
GeneXus development teams integrating Claude or Cursor for KB object analysis and automated code changes.
https://github.com/lennix1337/Genexus18MCP
By lennix1337
How to Get It
claude mcp add Genexus18MCP -- npx -y Genexus18MCP
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
Once it’s connected, paste this into Claude:
Analyze a GeneXus transaction for redundant fields and suggest consolidations
Trust Signals Auto-scanned
Data & Access
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 28 GitHub stars; 2 contributors; last commit 1d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 28 GitHub stars; 2 contributors; last commit 1d ago; license MIT.