Explore the WildFly management model via natural language — from any AI agent that supports MCP and Agent Skills.
WildFly exposes its entire configuration and runtime state through a management model — a tree of resources, each with attributes, operations, and capabilities. This project lets you search, browse, and compare that model across WildFly versions and feature packs, powered by Neo4j graph databases and the CLI.
MCP server for querying the WildFly management model graph
The mgt CLI is bundled automatically with the MCP server via platform-specific npm packages — no separate installation needed.
Claude Code
From Marketplace
claude plugin marketplace add https://github.com/model-graph-tools/claude-plugin
claude plugin install mgt@model-graph-tools
The MCP server is fetched automatically from npm via npx — no build step required.
From Source
git clone https://github.com/model-graph-tools/claude-plugin.git
cd claude-plugin/mcp-server
npm install
npm run build
Then load the plugin locally:
claude --plugin-dir /path/to/claude-plugin
Other AI Agents
The MCP server and skill follow open standards (MCP and Agent Skills) and work with any compatible AI agent. Setup has two parts:
Configure the MCP server in your agent's settings
Install the skill by copying the skills/wildfly-model-graph/ directory from this repository into your agent's skills folder
For most agents, the universal skills directory is .agents/skills/ (project-level) or ~/.agents/skills/ (user-level). See the Agent Skills client list for all supported agents.
Gemini CLI
Add to ~/.gemini/settings.json (or project-level .gemini/settings.json):
For any agent that supports MCP over stdio, configure it to run:
npx --yes @model-graph-tools/mcp-server
Copy the skill directory to your agent's skills folder (typically .agents/skills/ or ~/.agents/skills/). See the Agent Skills specification for details.
Usage
Slash Command
[!NOTE]
Slash commands are a Claude Code feature. Other agents use the skill (which activates automatically based on context) and MCP tools directly — see Natural Language below.
Use /mgt:model followed by your question:
Model overview
/mgt:model Give me an overview of the WildFly 39 management model.
/mgt:model How many resources and attributes does WildFly 39 have?
Browse and search
/mgt:model How do I add a new datasource?
/mgt:model How does the logging subsystem work?
/mgt:model How is TLS configured?
/mgt:model What is an authentication context?
/mgt:model Tell me more about credential stores.
Stability levels
/mgt:model Are there any community features in WildFly 39?
/mgt:model Show me all preview resources.
/mgt:model What community stability attributes exist?
Capabilities and deprecation
/mgt:model How do capabilities work?
/mgt:model What capabilities does elytron provide?
/mgt:model What operations have been deprecated recently?
Compare versions
/mgt:model Compare WildFly 38 and 39.
/mgt:model What attributes changed between WildFly 38 and 39?
/mgt:model Compare the IO subsystem between WildFly 23 and the latest version.
Feature packs
/mgt:model What resources does the AI feature pack provide?
/mgt:model Compare the first and the latest version of the AI feature pack.
Natural Language
The skill also activates automatically when the agent detects WildFly management model context in your conversation — just ask about subsystems, resources, attributes, or operations naturally. So most of the questions above should also work without using the slash command.
Container Lifecycle
Each WildFly version or feature pack runs as a separate Neo4j container pulled from
quay.io/modelgraphtools/model. The MCP server manages these through mgt:
Images are pulled if not present locally
Containers are started on demand when you query a source
If a source isn't running, the agent will suggest starting it
Containers started during a session are automatically stopped when the MCP server shuts down
Containers started outside the session (e.g., via mgt start) persist and are not affected
Stop containers explicitly at any time: /mgt:model stop WildFly 39
git clone https://github.com/model-graph-tools/claude-plugin.git
cd claude-plugin/mcp-server
npm install
npm run dev # runs with tsx, no compile step needed
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Preguntas
¿Cómo instalo @model Graph Tools/?
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
¿@model Graph Tools/ necesita una clave de API?
Este registro no indica ninguna variable de entorno obligatoria.
¿Qué transporte usa @model Graph Tools/?
@model Graph Tools/ se ejecuta localmente por stdio.
¿Cuándo se comprobó @model Graph Tools/ por última vez?
Última comprobación: 2026-10-28. MCP server for querying the WildFly management model graph