Going through the native SDK is what separates this from text manipulation: the model can list every transaction carrying an attribute, add a rule, refactor a name across the KB, and then build and run the tests — with GeneXus validating each change the way it would in the IDE.
A bridge from an AI client into a real GeneXus 18 Knowledge Base. It talks to the native GeneXus SDK — the same code paths the IDE uses — so edits are validated by GeneXus itself rather than being text surgery on KB files. A gateway process fronts a worker, reachable over stdio or an HTTP `/mcp` endpoint.
- Explore — `genexus_query` and `genexus_list_objects` search and list, with `parentPath` for hierarchical folder filtering; `genexus_read` extracts source, rules, events, structure, documentation or pattern XML; `genexus_inspect` and `genexus_get_sql` add context and generated SQL
- Edit — `genexus_edit` applies a full replacement, a patch or semantic operations, `genexus_create_object` makes new ones, `genexus_format` formats, `genexus_properties` reads and sets properties
- Data model and structure — `genexus_structure` reads and updates the visual and logical structure of a transaction, including its indexes
- Analyse — `genexus_analyze` covers impact and dependency analysis, linting and UI checks; `genexus_summarize` explains what an object does; `genexus_inject_context` feeds the KB back to the model
- Build and test — `genexus_lifecycle` runs build, KB and validation actions including a fast compile check; `genexus_test` runs the native GXtest tests
- Refactor and history — `genexus_refactor` renames an attribute, variable or object across the KB or extracts a procedure; `genexus_history` lists, reads, saves and restores earlier source
- Resources the client can browse: `genexus://kb/index-status`, `genexus://kb/health`, `genexus://objects`, plus agent and LLM playbooks
Windows, because GeneXus is Windows-only, with GeneXus 18 installed and the Knowledge Base opened at least once in the IDE so it is initialised. Node.js 18+ — nothing is cloned or installed globally, `npx` handles it. Run `npx genexus-mcp@latest init --kb "C:\KBs\YourKB" --gx "C:\Program Files (x86)\GeneXus\GeneXus18"`, or `--interactive` for the wizard; it verifies both paths, registers every AI client it detects, and prints the JSON snippet as a fallback. Then fully close and reopen the client — for Claude Desktop that means quitting from the system tray, not closing the window. The gateway binds to `127.0.0.1` by default with a configurable origin allowlist.
One command — npx genexus-mcp@latest init --kb "C:\\KBs\\YourKB" --gx "C:\\Program Files (x86)\\GeneXus\\GeneXus18"