Log inSubmit server
Genexus logo

Genexus

Manage GeneXus Knowledge Base objects through MCP with tools for reading, editing, analysis, refactoring, builds, and navigation.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Genexus

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "genexus": {
      "command": "npx",
      "args": [
        "-y",
        "genexus-mcp@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The genexus MCP server connects AI clients to GeneXus Knowledge Bases through the native SDK or version-specific legacy drivers. It exposes tools for inspecting, searching, editing, creating, building, comparing, merging, and refactoring KB objects, plus call-graph and health diagnostics. Use it when an agent needs to work with real KB content rather than a parsed copy. Native SDK support covers GeneXus 16, 17, and 18, while older versions use more limited compatibility paths.

Use cases

  • Inspect GeneXus objects and their callers
  • Search source across Procedures, DataProviders, WebPanels, and Transactions
  • Edit objects and rebuild affected callers
  • Create and refactor GeneXus KB components
  • Compare or merge object versions

Key features

  • Native SDK support for GeneXus 16, 17, and 18
  • Legacy drivers for older GeneXus versions
  • Object search, inspection, editing, and creation
  • Call-graph, dependency, impact, and code analysis
  • WorkWith and WorkWithPlus authoring
  • Compare, merge, refactor, and build workflows

Tools52

What Genexus lets your agent do. Expand a tool for its parameters.

Self-reported~1.6k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

6/6 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9h ago via OSV.dev · genexus-mcp@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars39Stargazers on the source repository.
npm downloads6.1kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Tools exposed52Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Genexus works

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:

Terminal
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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Genexus

genexus is an MCP server that connects AI clients to GeneXus Knowledge Bases through native SDKs or legacy drivers. Its main tools read, search, create, edit, build, analyze, compare, merge, and refactor KB objects, while also providing health checks, navigation reports, and call-graph analysis.

Run the package with npx and initialize it against a KB and GeneXus installation. For example, use `npx genexus-mcp@latest init --kb "C:\KBs\MyGX18KB" --gx "C:\Program Files (x86)\GeneXus\GeneXus18"`, then restart the AI client.

Yes, genexus works with Cursor through its MCP configuration. The server also names Claude Desktop and Claude Code as supported clients, and the configuration must be reloaded after changing the selected KB or SDK.

Native SDK support covers GeneXus 16, 17, and 18. Basic legacy compatibility covers Evolution 1, Evolution 2, Evolution 3, GeneXus 15, GeneXus 9.0, and GeneXus 8.0 through separate reflection or GXPublic drivers.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGenexus AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/genexus?style=directory)](https://allmcps.com/mcp/genexus)
HTML Embed
<a href="https://allmcps.com/mcp/genexus"><img src="https://allmcps.com/api/badge/genexus?style=directory" alt="Genexus on AllMCPs" /></a>