GeneXus 18 MCP server — read, edit, and analyze GeneXus knowledge base objects (transactions, web panels, procedures, SDTs) directly from Claude
If you already use Genexus18mcp, the genexus18mcp mcp server is the piece that lets your assistant work with it directly. GeneXus 18 MCP server — read, edit, and analyze GeneXus knowledge base objects (transactions, web panels, procedures, SDTs) directly from Claude, Cursor, and other AI agents over the Model Context Protocol.
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.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Non — admin shell** → %LOCALAPPDATA%\Programs\GenexusMCP\genexus_whoami — KB context, version, worker/index/database health, self-update check, next-step hintsgenexus_doctor — connection + install + cache health checkgenexus_recipe — named playbooks / self-extending macrosgenexus_telemetry — observability (metrics, latency, errors)genexus_query — object search (prefixes name:, type:, usedby:, parent:, …)genexus_list_objects — paginated object listing with aggregatesgenexus_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 sourcegenexus_navigation — the IDE "View Navigation" reportgenexus_edit — edit any object part; modes full / patch / opsConfiguration is passed through the environment: MY_KB_PATH, MY_GENEXUS_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Before you start, make sure you have: - ✅ Windows (GeneXus is Windows-only) - ✅ GeneXus 18 installed locally (default path: C:\Program Files (x86)\GeneXus\GeneXus18) - ✅ A GeneXus 18 Knowledge Base opened at least once in the IDE (so it's initialized) - ✅ Node.js 18+ — check with node --version in a terminal; install from nodejs.org if missing - ✅ **An
Installation goes through your MCP client rather than a global install: point it at genexus-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Genexus18mcp's toolset — Non, genexus_whoami, genexus_doctor and 11 more — is a fair guide to whether it matches your workflow. It is maintained by lennix1337; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Non | admin shell** → %LOCALAPPDATA%\Programs\GenexusMCP\ |
| 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_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 |
{
"mcpServers": {
"genexus18mcp": {
"command": "npx",
"args": ["-y", "genexus-mcp"],
"env": {
"MY_KB_PATH": "your-value",
"MY_GENEXUS_PATH": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Before you start, make sure you have: - ✅ Windows (GeneXus is Windows-only) - ✅ GeneXus 18 installed locally (default path: C:\Program Files (x86)\GeneXus\GeneXus18) - ✅ A GeneXus 18 Knowledge Base opened at least once in the IDE (so it's initialized) - ✅ Node.js 18+ — check with node --version in a terminal; install from nodejs.org if missing - ✅ **An
| Variable | Description | Required |
|---|---|---|
| MY_KB_PATH | Filesystem location the server is allowed to use. | Optional |
| MY_GENEXUS_PATH | Filesystem location the server is allowed to use. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.