# genexus [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/lennix1337/Genexus18MCP  
**GitHub Stars:** 39  
**npm Downloads (last month):** 6060  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/genexus

## Description
Read, edit, and analyze GeneXus 18 KB objects from Claude, Cursor, and AI agents.

## Tools
Capabilities this server exposes over MCP:

- **genexus_whoami** — KB context, version, worker/index/database health, self-update check, next-step hints
- **genexus_doctor** — connection + install + cache health check
- **genexus_recipe** — named playbooks / self-extending macros
- **genexus_telemetry** — observability (metrics, latency, errors)
- **genexus_wire** — read-only, token-budgeted call-graph engine (bundled `gxwire.exe`). Actions: `pack_task` (default; one-shot orientation bundle for a task), `for` (intent ranking with domain synonyms such as `fat` → `faturamento`), `status` (graph size and top hubs), `callers` (direct and transitive), `impact` (bla…
- **genexus_query** — object search (prefixes `name:`, `type:`, `usedby:`, `parent:`, …)
- **genexus_list_objects** — paginated object listing with aggregates
- **genexus_read** — read any part of an object (source, structure, rules, events, docs, pattern XML, …)
- **genexus_inspect** — one-shot object snapshot (metadata, variables, structure, signature, callers)
- **genexus_search_source** — regex/semantic search across Procedure/DataProvider/WebPanel/Transaction source
- **genexus_navigation** — the IDE "View Navigation" report
- **genexus_edit** — edit any object part; modes `full` / `patch` / `ops`
- **genexus_edit_and_build** — edit + optional specification + rebuild callers in one call, with compensating rollback on validation failure
- **genexus_edit_form** — semantic WebForm edits
- **genexus_variable** — Variables-part CRUD
- **genexus_create** — creation umbrella (Transaction, Procedure, Domain, SDT, API, Folder, Module, `curl_procedure` = scaffold a Procedure from a curl command, …); `object_atomic` authors definition + variables + Rules + properties + Source with preflight/read-back/rollback
- **genexus_data_view** — atomically create/inspect/update/delete a root-only Business Component Transaction mapped through a native Data View to an existing physical table; validates attributes/keys first, supports optimistic versions and true no-mutation dry-runs, requires `confirm=true` for destructive delete, and report…
- **genexus_delete_object** — delete an object by native SDK identity; use `dryRun=true` to inspect incoming references before `confirm=true`
- **genexus_format** — format a code snippet with the worker's rules
- **genexus_structure** — read/write the data model: `get_visual`/`get_logic`, `update_visual` (structure DSL), `create_index`/`drop_index` (unique/non-unique indexes — the GeneXus way to enforce uniqueness), `set_attribute` (Formula, subtype, Title/ColumnTitle, IsCollection, basedOnDomain), `set_level` (level Description/I…
- **genexus_authoring** — members of object types the structure DSL doesn't cover: `add_external_method`/`add_external_property` (External Objects), `add_menu_option` (Menus)
- **genexus_properties** — read/update object-level properties
- **genexus_generator_reference** — list/preview/add/remove native .NET generator references with managed-assembly validation, optimistic concurrency, save/re-read verification, and exact full-snapshot rollback; never runs lifecycle actions implicitly
- **genexus_refactor** — rename, extract procedure, WWP condition set
- **genexus_apply_pattern** — apply a GeneXus pattern (WorkWith, WorkWithPlus, …); `mode=actions` manages typed WorkWithPlus grid actions and Action Groups
- **genexus_wwp** — typed WorkWithPlus editing: Action Groups, atomic native `add_grid_attribute`, plus `add_tab`, `move_tab`, and `remove_tab` for WebPanel tabs and typed children
- **genexus_workwith** — typed authoring of standard WorkWith (WorkWith for Web) pattern actions on tabs (`General`, etc.), procedure calls, conditions, and parameters
- **genexus_compare** — IDE "Compare Objects" parity (`IComparerService`)
- **genexus_merge** — 2- or 3-way object merge (`IMergeService`)
- **genexus_analyze** — cross-object semantic analysis (impact, dependencies, complexity, naming, code_metrics, summary, `kb_stats` = KB activity/freshness, `table_relations` = table↔transaction relations + redundant attrs, …). `mode=explain` is compatibility-only: it preserves the legacy response envelope and returns `No…
- **genexus_dfd** — read-only ER diagram of a Transaction/Table (`extends`/`subordinates` edges + Mermaid `erDiagram`) built only from the SDK table relations
- **genexus_impact** — read-only affected set of an object over the caller graph: counts by type, a dependencies-first rebuild `order`, cycles and the cap that truncated it (no risk score)
- **genexus_object_context** — read-only identity + callers/callees (with coverage) + data model of one object; a name shared by several objects is refused with their guids and paths
- **genexus_doc** — generate wiki / dependency graphs / health reports
- **genexus_api** — introspect REST endpoints exposed by HTTP procedures
- **genexus_security** — audit KB security: `audit_gam` (env/GAM props), `scan_secrets` (regex over Source), `scan_native` (the SDK's own Security Scanner, `ISecurityScannerService`)
- **genexus_lifecycle** — directed `build` (incl. `compile_check`), incremental global `build_all`, forced global `rebuild`, validate, index, reorg, and poll status
- **genexus_test** — run native GXtest tests
- **genexus_db** — DB umbrella: schema-drift, `sql_ddl`/`sql_navigation`, static index advisor, `sample_data`, typed Transaction record query/insert/update with dry-run, optimistic versioning, reread and verified rollback, Domain/SDT type introspection, translation import, `reorg_impact`, and non-mutating `reorg_prev…
- **genexus_deploy** — deploy application (`IDeploymentService`): `list_targets` (read) / `deploy` (destructive, `confirm=true`)
- **genexus_layout** — SDK layout/WebForm ops (`get_tree`, `find_controls`, `set_property`, `add_printblock`, `get_preview`, `list_controls` = control/theme-class catalog, `design_system` = DSO tokens/classes/images, …)
- **genexus_kb** — multi-KB pool (`list`/`open`/`close`/`set_default`)
- **genexus_module** — Module Manager (`IModuleManagerService`)
- **genexus_kb_version** — model version/branch management (Create/Activate/Revert)
- **genexus_versioning** — versioning umbrella (git-style history over the KB)
- **genexus_gxserver** — GXserver / Team Development sync, incl. `pipeline_*` (CI pipelines via `IContinuousIntegrationService`)
- **genexus_transfer** — real XPZ export/import (`IKnowledgeManagerService`, dependency-aware): `export` / `inspect` / `import` (`import` previews by default: pass `dryRun:false` and `confirm:true` to actually import)
- **genexus_memory** — per-KB fact store for the agent
- **genexus_gam** — GAM / integrated-security provisioning (`IIntegratedSecurityService`)
- **genexus_io** — assets, part-text exchange, screenshots, OCR
- **genexus_sdk_probe** — dump the live SDK surface (types/methods/props) for capability discovery
- **genexus_worker_reload** — hot-swap the worker without restarting the client

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "genexus": {
    "command": "npx",
    "args": ["-y","genexus-mcp@latest"]
  }
}
```

## Documentation

## What genexus MCP server does

genexus MCP server gives MCP-compatible AI clients access to GeneXus Knowledge Base objects through the selected native SDK or a legacy compatibility driver. It can inspect object metadata and parts, search source, list and query objects, read navigation reports, and analyze dependencies, impact, complexity, naming, code metrics, KB activity, and table relationships.

Editing capabilities cover source, structure, rules, events, variables, properties, pattern XML, and other object parts. The server also supports object creation, deletion, refactoring, formatting, pattern application, WorkWith and WorkWithPlus authoring, comparison, merging, and edit-and-build workflows. Specialized operations include Business Component Transactions backed by native Data Views, generator references, external members, menu options, indexes, attributes, and levels.

## How it works

The MCP process is pointed at a Knowledge Base and a GeneXus installation. Native paths use the real GeneXus SDK; legacy paths use either runtime reflection or the classic GXPublic surface, depending on the configured version. The worker places version-sensitive SDK behavior behind compatibility adapters, allowing the tool names and client configuration format to remain consistent across supported native majors.

GeneXus 16, 17, and 18 use native SDK support. Evolution 1, Evolution 2, Evolution 3, GeneXus 15, GeneXus 9.0, and GeneXus 8.0 are handled through basic legacy drivers, with less feature parity than native SDK operation. Separate MCP configurations and ports can be used when different SDK majors must run at the same time.

The read-only `genexus_wire` tool provides token-budgeted call-graph operations, including task-oriented orientation bundles, intent ranking, graph status, callers, and impact analysis. `genexus_edit_and_build` can combine an edit with optional specification and caller rebuilding, using compensating rollback when validation fails. Destructive operations provide dry-run or confirmation controls where supported.

## Setup and configuration

Install or run the package through npm, then initialize a KB and GeneXus installation with `init`:

```bash
npx genexus-mcp@latest init --kb "C:\KBs\MyGX18KB" --gx "C:\Program Files (x86)\GeneXus\GeneXus18"
```

The initializer reads the KB and selected installation metadata, checks their major versions, and writes the MCP configuration only after compatibility can be verified. After changing the SDK or KB, restart the AI client so it reloads the MCP process and tool schemas. `genexus_whoami` reports the detected SDK, matched major, compatibility level, and version-match status; `genexus_doctor` checks connection, installation, and cache health.

Classic GX8 and GX9 KBs can be declared with a `com-gxpublic` driver, an installation path, and a major version. Their configuration uses legacy KB markers and the registered 32-bit GXPublic provider.

## Tools and capabilities

The tool set includes:

- Discover KB context, installation health, telemetry, recipes, and worker status.
- Search and inspect objects with prefixes, pagination, snapshots, source queries, and navigation reports.
- Read and modify object parts using full, patch, or operation-based edits.
- Create Transactions, Procedures, Domains, SDTs, APIs, folders, modules, and curl-derived procedure scaffolds.
- Manage data structures, indexes, attributes, levels, properties, variables, external members, and menu options.
- Apply WorkWith and WorkWithPlus patterns and edit their typed actions, groups, tabs, conditions, and parameters.
- Compare and merge objects, rename objects, extract procedures, and run semantic cross-object analysis.

## Limitations and notes

Legacy drivers are intended for core operations and do not provide the same source and editing parity as native SDK support. GX8 and GX9 use a metadata-oriented GXPublic surface. Modern tools that require newer GeneXus features can return structured unsupported-version errors.

The experimental `gx-engine` backend is a separate Rust SDK replacement project. It is used for selected build and query paths, while reads, edits, and other shapes can fall back to the SDK. Full SDK replacement is not established for arbitrary Knowledge Bases, so SDK-backed operation remains relevant for capabilities outside the engine's supported boundaries.

_Full upstream README: https://allmcps.com/mcp/genexus/readme_