wls-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WLS_BASE_URL | No | The base URL of the Oracle WebLogic Server REST management API (e.g., http://localhost:7001). | |
| WLS_PASSWORD | Yes | WebLogic password for the dedicated least-privilege service account used to authenticate. | |
| WLS_USERNAME | Yes | WebLogic username for the dedicated least-privilege service account used to authenticate. | |
| WLS_AUDIT_LOG | No | File path to write JSON Lines audit records in addition to stderr. | |
| WLS_READ_ONLY | No | Set to true to disable control_server outright. | |
| WLS_ALLOWED_SERVERS | No | Restricts which servers are addressable at all. Unset means the whole domain. | |
| WLS_ALLOW_ADMIN_SHUTDOWN | No | Set to false to forbid stopping the AdminServer entirely. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_serversA | List every configured server in the WebLogic domain with its current lifecycle state (RUNNING, SHUTDOWN, STARTING, FAILED_NOT_RESTARTABLE, ...), listen port and assigned machine. This is the only view that includes stopped servers. |
| get_server_healthA | Report the health of one WebLogic server: overall health state (ok, warn, critical, failed, overloaded), the subsystem at fault if any, and reported symptoms. A server that is not RUNNING has no health data; its lifecycle state is returned instead. |
| get_jvm_statsA | Return JVM heap and runtime statistics for one RUNNING WebLogic server: current and maximum heap, free heap and free percentage, uptime, and the Java version in use. Byte values are also given in MB for readability. |
| control_serverA | Start or stop a WebLogic server through Node Manager. action is one of: 'start', 'shutdown' (graceful), 'force_shutdown' (immediate, use to clear a wedged server). Stopping the Administration Server also stops the REST API this tool depends on, so it requires confirm=true and cannot be undone through this tool. If this server is configured with a break-glass token, every action additionally requires that token, which only a human operator can provide - never guess it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The four tools target distinct facets—inventory, health, JVM metrics, and lifecycle control—so selection is generally clear. The only minor overlap is lifecycle state information appearing in both list_servers and get_server_health for non-running servers, but descriptions clarify when to use each.
All names use snake_case with a verb-first pattern (list_*, get_*, control_*), and the two get_* tools are parallel. No camelCase or inconsistent verb styles.
Four tools is a tight, focused surface for a WebLogic server-management MCP; each tool covers a distinct need (list, health, JVM stats, control). This sits comfortably in the well-scoped 3–15 range.
Core server lifecycle and observability are covered: inventory, health, JVM, and start/stop. Minor gaps exist—no dedicated restart, logs, thread dumps, or configuration inspection—but these are not fatal for the stated server-control purpose.