Genexus

Name: Genexus
Author: lennix1337

by lennix1337version 2.0.4i★ –iRuns on your computer

Registry nameio.github.lennix1337/genexus

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "genexus": {
      "command": "npx",
      "args": [
        "-y",
        "genexus-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add genexus -- npx -y genexus-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "genexus": {
      "command": "npx",
      "args": [
        "-y",
        "genexus-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "genexus": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "genexus-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account lennix1337, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 18436 servers in this category
Published to the registry more recently than 7% of the other 18436 servers in this category
Basic checks equal to or better than 100% of the other 18436 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Genexus safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.0.4) reached the registry 6 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, MONS

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 3 days ago

Install

MONS

by tomis3

Build and adjust your clients' MONS training plans: programs, templates, exercises, sets, reps.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

GeneXus MCP Server — Multi-version GeneXus for Claude, Cursor, and AI Agents

¿Hablás español? → Guía de inicio en español

Fala português? → Guia de início em português

Stuck? → Troubleshooting guide

All docs → Documentation index

GeneXus MCP Server lets AI agents — Claude Desktop, Claude Code, Cursor, Antigravity, and any MCP-compatible client — read, edit, analyze, and refactor objects inside a Knowledge Base supported by the selected native SDK or legacy compatibility driver. Native SDK paths work with the real GeneXus SDK and legacy paths use explicit reflection/COM adapters; neither path relies on a parsed copy of the KB.

In practice: you point the MCP at your KB, then ask your AI assistant things like *"list all transactions with attribute CustomerId"*, *"add a rule to the Order transaction that validates the total"*, or *"refactor this procedure to use the new SDT"* — and it does it.

Supported SDK majors: GeneXus 16, GeneXus 17, GeneXus 18, GeneXus Evolution 3 (native SDK). Basic legacy compatibility: GeneXus Evolution 2, GeneXus Evolution 1, GeneXus 15, GeneXus 9.0, GeneXus 8.0 via com-gxpublic and dotnet-reflection (not the native SDK build). Primary SDK: GeneXus 18. Source of truth: config/gx-versions.json.

What you can do with it
Prerequisites · Quickstart · Corporate install
What can I ask the AI? · Supported AI clients · Troubleshooting
Multi-version GeneXus support
Tool Surface · WorkWithPlus pattern editing · AXI CLI
Advanced Configuration · Experimental gx-engine
Development & building from source · Contributing
Support the project · Acknowledgements · License

What you can do with it

A quick map of what the agent can do against your real KB through the 60 tools (details in Tool Surface; new installs expose a 20-tool standard profile by default, see Tool profiles):

Area	What the agent can do
🔎 Explore	Search & list objects, read any part (source, rules, events, structure, docs, pattern XML), inspect metadata & callers, regex-search source, view the navigation report
🧭 Orient & trace	Rank the objects a task touches, list direct and transitive callers, trace the shortest call path between two objects, check blast radius and safe-delete, follow one variable's data flow. Runs on exported sources through `genexus_wire` (read-only, token-budgeted); `pack_task` also works directly on the open native KB
✏️ Edit code	Edit any object part (`full`/`patch`/`ops` modes), variables CRUD, format, create & delete objects, scaffold a Procedure from a curl command, edit + rebuild callers in one shot
🗄️ Author the data model	Transaction structure (DSL), unique/non-unique indexes (create & drop), attribute formulas & subtypes, level Description/Image attributes, Domain enum values, folders & modules, table↔transaction relations & redundant-attribute detection, Data View–backed Business Components
🧩 Author other objects	External Object methods & properties, Menu options, REST API objects, WorkWithPlus / WorkWith patterns, K2B Designer (through the IDE bridge), typed .NET generator references
🎨 UI & WorkWithPlus	Full read/write of pattern XML (controls, actions, grids, orders, groups), theme classes & styling, native WebForm/layout edits, control catalog & design-system tokens/classes/images, headless-browser verification
🔬 Analyze	Impact/dependency analysis, complexity & code metrics, naming, KB activity/freshness, reorg/DDL impact preview, native security scan, schema-drift check, ER diagrams
🛠️ Build, test & deploy	Build (full or fast `compile_check`), validate, reorg, index, run native GXtest tests, deploy the application (targets + deploy)
🔀 Refactor & compare	Rename across the KB, extract procedure, compare & merge objects (IDE parity), compare two KB directories
🌿 Versioning, transfer & teams	KB model versions/branches, real XPZ export/import (dependency-aware), GXserver (Team Development) sync + CI pipelines, git-style history, multi-KB parallel work, disposable KB sandboxes
🔐 Security	GAM / integrated-security provisioning, KB security audit + native Security Scanner

Native SDK support works through the native GeneXus SDK — the same code paths the IDE uses — so edits are real and validated, not text hacks on KB files. Legacy support uses the reflection or COM driver listed in the catalog and degrades unsupported modern tools explicitly.

Prerequisites

Before you start, make sure you have:

✅ Windows (GeneXus is Windows-only)
✅ GeneXus 18, 17, or 16 installed locally for native SDK support (GeneXus 18 is the primary SDK), or a catalogued legacy installation for basic compatibility — see docs/generated/supported-versions.md
✅ A Knowledge Base created with a supported native or legacy GeneXus major and opened at least once in the IDE (so it's initialized)
✅ Node.js 22+ — check with node --version in a terminal; install from nodejs.org if missing
✅ An MCP-compatible AI client — Claude Desktop, Claude Code, Cursor, Antigravity, etc.

You do not need to clone this repo or install anything globally — npx handles it.

Never used a terminal before? Press Win+R, type powershell, hit Enter. That's your terminal.

Quickstart (3 steps, ~5 minutes)

Find your two paths first

Before running the installer, note these down:

GeneXus install folder — where GeneXus.exe lives. Usually C:\Program Files (x86)\GeneXus\GeneXus18.
Your KB folder — the root folder of your Knowledge Base (it contains the .gxw file and knowledgebase.connection).

Not sure where your KB lives? Open it in GeneXus and check the title bar, or look in File → Recent.

Step 1 — Run the installer

Open a terminal and run, replacing the paths with your KB folder and your GeneXus install:

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

Prefer the wizard? Run npx genexus-mcp@latest init --interactive and answer the prompts. Running init from inside a KB folder also works: the KB path is detected from the current directory.

What happens (takes ~30 seconds the first time, faster on re-runs):

npx downloads the package.
The installer checks that both paths exist and that the KB's GeneXus major (read from its .gxw) matches the selected installation and is supported. It stops before writing anything when they conflict.
It writes the MCP config.json.
It auto-detects which AI clients you have installed and registers the MCP in each one (pass --no-write-clients to skip, or --all-clients to write every known client).
It verifies the result with a short MCP smoke test and prints what to do next.

On Windows, Antigravity is registered with the gateway executable bundled in the current npm package when that artifact is available, so it skips the npx bootstrap chain on every MCP handshake. That path follows the package in the npx cache; after an upgrade, run npx genexus-mcp@latest clients add --clients antigravity again if genexus-mcp clients reports a stale launcher. Other clients keep the npx genexus-mcp@latest launcher unless you use the fixed-path installer below.

Step 2 — Check the client registration

Step 1 auto-registers every supported client it detects, including Claude Desktop, Claude Code, Cursor, Antigravity, Gemini CLI, OpenCode, Codex CLI, and VS Code. Run npx genexus-mcp clients to confirm. If yours wasn't detected, register it manually — see the client setup guide.

Step 3 — Restart your AI client, then test

This part trips most people: fully close your AI client and reopen it. Not just the window — the whole process.

Claude Desktop: right-click the system-tray icon → Quit. Then launch it again. (Closing the window is not enough.)
Claude Code: end the session and start a fresh one.
Cursor / Antigravity: close all windows and reopen.
OpenCode: fully quit and reopen it so it reloads opencode.json / opencode.jsonc.
Gemini CLI / Codex CLI: start a new process or session.

Then paste this prompt:

*"Using the GeneXus MCP, list the first 5 objects in my KB and show name + type."*

What should happen:

The AI invokes the genexus_list_objects tool (some UIs show "calling tool…").
A few seconds later, you get a list of objects from your KB.

If you get a list back — you're done. Skip to What can I ask the AI? for ideas.

If the AI says it doesn't have a GeneXus tool, or nothing happens, go to Troubleshooting — most issues are covered there.

🤖 Let your AI install it for you

If you'd rather not run anything in the terminal yourself, paste this into your AI chat:

Please configure the GeneXus MCP server. Run npx genexus-mcp@latest init --kb " " --gx " " in the terminal. If I haven't told you my GeneXus path and KB path yet, ask me first. Once it succeeds, run npx genexus-mcp clients to confirm my client is registered, and tell me when I should restart the client to start using GeneXus tools.

Replace the placeholders or let the AI ask you for them.

Corporate install (fixed path, ASR-friendly)

If your machine has Microsoft Defender ASR, SmartScreen, or another endpoint policy blocking unsigned binaries, the default npx flow is painful — npx caches the package under %LOCALAPPDATA%\npm-cache\_npx\ \..., and the changes per version, so IT can't whitelist a stable path without a wildcard over the whole npm cache (which is too broad).

Use the corporate installer instead. It extracts the binaries to a stable directory, creates a neutral runtime configuration (no hardcoded KB), and registers the AI clients to launch the gateway directly from there — npx is never on the runtime path.

# One-liner — installs latest release, registers AI clients

iex (irm https://raw.githubusercontent.com/lennix1337/Genexus18MCP/main/scripts/install.ps1)

With an explicit GeneXus installation

$s = irm https://raw.githubusercontent.com/lennix1337/Genexus18MCP/main/scripts/install.ps1 & ([scriptblock]::Create($s)) -Gx "C:\P

Only the beginning is shown; read the rest in the repo

Genexus

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

MONS

README from the maker

GeneXus MCP Server — Multi-version GeneXus for Claude, Cursor, and AI Agents

Contents

What you can do with it

Prerequisites

Quickstart (3 steps, ~5 minutes)

Find your two paths first

Step 1 — Run the installer

Step 2 — Check the client registration

Step 3 — Restart your AI client, then test

🤖 Let your AI install it for you

Corporate install (fixed path, ASR-friendly)

With an explicit GeneXus installation