WLST MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@WLST MCP ServerShow me the health status of all servers"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
WLST MCP Server
A Model Context Protocol (MCP) server for Oracle WebLogic Server administration using WLST (WebLogic Scripting Tool).
Overview
This MCP server provides a comprehensive set of tools for managing Oracle WebLogic Server domains, including server lifecycle management, application deployment, monitoring, and diagnostics.
Related MCP server: OCI MCP Server
Project Structure
wlst-mcp/
├── src/
│ └── wlst_mcp.py # Main MCP server implementation
├── README.md # This file - main documentation
├── ARCHITECTURE.md # System architecture diagrams
├── INSTALLATION.md # Prerequisites and installation guide
├── INTEGRATION.md # Claude Desktop & Claude Code setup
├── EXAMPLES.md # Usage examples and custom scripts
├── requirements.txt # Python dependencies
├── LICENSE # Apache License 2.0
└── .gitignore # Git ignore patternsQuick Start
Install dependencies:
pip install -r requirements.txtSet environment variables:
export WLST_ADMIN_URL=t3://localhost:7001 export WLST_USERNAME=weblogic export WLST_PASSWORD=your_passwordRun the MCP server:
python src/wlst_mcp.pyIntegrate with Claude: See INTEGRATION.md for detailed setup instructions.
Documentation
Document | Description |
System architecture and component diagrams | |
Prerequisites, installation, security configuration | |
Claude Desktop & Claude Code integration | |
Usage examples and custom WLST scripts |
Features
Server Management: Start, stop, restart, and monitor WebLogic servers
Application Deployment: Deploy, undeploy, and list applications
Monitoring: Real-time metrics for JVM, threads, JDBC, and JMS
Diagnostics: Thread dumps and health checks
Resource Management: JDBC datasources and JMS resources
Custom Scripting: Execute custom WLST/Jython scripts
Available Tools
Connection & Discovery
Tool | Description |
| Test connectivity to a WebLogic Admin Server |
| List all servers in a WebLogic domain with their status |
Server Lifecycle
Tool | Description |
| Start a managed server |
| Stop a managed server (supports force option) |
| Restart a managed server |
Application Management
Tool | Description |
| Deploy an application (WAR, EAR, JAR) |
| Undeploy an application |
| List all deployed applications |
Monitoring & Metrics
Tool | Description |
| Get health status of WebLogic servers |
| Get detailed metrics (JVM, threads, JDBC, JMS) |
Resource Management
Tool | Description |
| List all JDBC datasources |
| List JMS servers, modules, queues, and topics |
Diagnostics
Tool | Description |
| Capture thread dump for debugging |
| Execute custom WLST/Jython scripts |
Tool Reference
wlst_test_connection
Test connectivity to a WebLogic Admin Server.
Parameters:
Parameter | Type | Required | Description |
| string | No | Admin Server URL (e.g., |
| string | No | WebLogic admin username. Uses |
| string | No | WebLogic admin password. Uses |
| integer | No | Connection timeout in seconds (10-600, default: 120) |
wlst_list_servers
List all servers in a WebLogic domain with their status.
Parameters:
Parameter | Type | Required | Description |
| string | No | Admin Server URL |
| string | No | WebLogic admin username |
| string | No | WebLogic admin password |
| string | No | Output format: |
wlst_start_server
Start a managed server in a WebLogic domain.
Parameters:
Parameter | Type | Required | Description |
| string | Yes | Name of the managed server to start |
| string | No | Admin Server URL |
| string | No | WebLogic admin username |
| string | No | WebLogic admin password |
| integer | No | Operation timeout in seconds (10-600, default: 120) |
wlst_stop_server
Stop a managed server in a WebLogic domain. Supports two shutdown modes:
Graceful shutdown (default): Waits for active sessions to complete before stopping. This is safer for production environments but takes longer.
Force shutdown: Stops the server immediately without waiting for sessions. Use when you need to stop quickly or the server is unresponsive.
Parameters:
Parameter | Type | Required | Description |
| string | Yes | Name of the managed server to stop |
| boolean | No | Force shutdown (immediate). If |
| string | No | Admin Server URL |
| string | No | WebLogic admin username |
| string | No | WebLogic admin password |
| integer | No | Operation timeout in seconds. Graceful shutdown may need longer timeout. (10-600, default: 300) |
Shutdown Modes Comparison:
Mode | Parameter | Behavior | Use Case |
Graceful |
| Waits for sessions to complete | Production, scheduled maintenance |
Force |
| Immediate stop, sessions terminated | Emergency, unresponsive server |
wlst_restart_server
Restart a managed server in a WebLogic domain. Performs a stop followed by a start.
Parameters:
Parameter | Type | Required | Description |
| string | Yes | Name of the managed server to restart |
| boolean | No | Force shutdown during restart. If |
| string | No | Admin Server URL |
| string | No | WebLogic admin username |
| string | No | WebLogic admin password |
| integer | No | Operation timeout in seconds. Graceful restart may need longer timeout. (10-600, default: 300) |
wlst_deploy
Deploy an application to WebLogic Server.
Parameters:
Parameter | Type | Required | Description |
| string | Yes | Application name |
| string | Yes | Path to the application archive (WAR, EAR, JAR) |
| string | No | Comma-separated list of target servers/clusters |
| string | No | Deployment stage mode: |
| string | No | Path to deployment plan XML |
| string | No | Admin Server URL |
| string | No | WebLogic admin username |
| string | No | WebLogic admin password |
wlst_undeploy
Undeploy an application from WebLogic Server.
Parameters:
Parameter | Type | Required | Description |
| string | Yes | Name of the application to undeploy |
| string | No | Comma-separated list of target servers/clusters |
| string | No | Admin Server URL |
| string | No | WebLogic admin username |
| string | No | WebLogic admin password |
| integer | No | Operation timeout (10-600, default: 120) |
wlst_list_applications
List all deployed applications in a WebLogic domain.
Parameters:
Parameter | Type | Required | Description |
| string | No | Admin Server URL |
| string | No | WebLogic admin username |
| string | No | WebLogic admin password |
| string | No | Output format: |
wlst_server_health
Get health status of WebLogic servers.
Parameters:
Parameter | Type | Required | Description |
| string | No | Specific server name (all servers if not specified) |
| string | No | Admin Server URL |
| string | No | WebLogic admin username |
| string | No | WebLogic admin password |
| string | No | Output format: |
wlst_server_metrics
Get detailed metrics for a WebLogic server.
Parameters:
Parameter | Type | Required | Description |
| string | Yes | Server name to get metrics for |
| string | No | Type of metrics: |
| string | No | Admin Server URL |
| string | No | WebLogic admin username |
| string | No | WebLogic admin password |
| string | No | Output format: |
wlst_list_datasources
List all JDBC datasources in a WebLogic domain.
Parameters:
Parameter | Type | Required | Description |
| string | No | Admin Server URL |
| string | No | WebLogic admin username |
| string | No | WebLogic admin password |
| string | No | Output format: |
wlst_list_jms_resources
List all JMS resources in a WebLogic domain.
Parameters:
Parameter | Type | Required | Description |
| string | No | Admin Server URL |
| string | No | WebLogic admin username |
| string | No | WebLogic admin password |
| string | No | Output format: |
wlst_thread_dump
Get a thread dump from a WebLogic server for debugging.
Parameters:
Parameter | Type | Required | Description |
| string | Yes | Server name to get thread dump from |
| string | No | Admin Server URL |
| string | No | WebLogic admin username |
| string | No | WebLogic admin password |
wlst_execute_script
Execute a custom WLST/Jython script.
Parameters:
Parameter | Type | Required | Description |
| string | Yes | WLST/Jython script to execute |
| string | No | Admin Server URL (optional for offline scripts) |
| string | No | WebLogic admin username |
| string | No | WebLogic admin password |
| integer | No | Script execution timeout (10-1800, default: 120) |
Configuration & Environment Variables
How Credentials Are Resolved
The MCP server uses a fallback mechanism to resolve connection parameters. For each parameter, it checks in the following order:
1. Tool parameter (if provided) → 2. Environment variable → 3. Error (if required)This means:
If you provide a parameter in the tool call, it will be used
If the parameter is not provided, the environment variable is used as default
If neither is available, an error is returned for required parameters
Environment Variables Reference
Variable | Description | Example |
| WebLogic Admin Server URL (protocol://host:port) |
|
| WebLogic admin username |
|
| WebLogic admin password |
|
URL Format
The WLST_ADMIN_URL must follow this format:
<protocol>://<host>:<port>Component | Description | Examples |
| Connection protocol |
|
| Admin Server hostname or IP |
|
| Admin Server listen port |
|
Examples:
# Local development (non-SSL)
WLST_ADMIN_URL=t3://localhost:7001
# Local development (SSL)
WLST_ADMIN_URL=t3s://localhost:7002
# Remote server
WLST_ADMIN_URL=t3s://weblogic-admin.example.com:7002
# Using IP address
WLST_ADMIN_URL=t3://192.168.1.100:7001Configuration Examples
Option 1: Environment Variables (Recommended)
Set environment variables before starting the MCP server:
Linux/macOS:
export WLST_ADMIN_URL=t3://localhost:7001
export WLST_USERNAME=weblogic
export WLST_PASSWORD=your_passwordWindows (Command Prompt):
set WLST_ADMIN_URL=t3://localhost:7001
set WLST_USERNAME=weblogic
set WLST_PASSWORD=your_passwordWindows (PowerShell):
$env:WLST_ADMIN_URL = "t3://localhost:7001"
$env:WLST_USERNAME = "weblogic"
$env:WLST_PASSWORD = "your_password"Once configured, you can call tools without specifying connection parameters:
{
"tool": "wlst_list_servers",
"params": {}
}Option 2: Tool Parameters (Override)
You can override environment variables by passing parameters directly:
{
"tool": "wlst_list_servers",
"params": {
"admin_url": "t3://production-server:7001",
"username": "admin_user",
"password": "admin_password"
}
}Option 3: Claude Desktop Configuration
Configure in claude_desktop_config.json:
{
"mcpServers": {
"wlst-mcp": {
"command": "python",
"args": ["/path/to/wlst-mcp/server.py"],
"env": {
"WLST_ADMIN_URL": "t3://localhost:7001",
"WLST_USERNAME": "weblogic",
"WLST_PASSWORD": "your_password"
}
}
}
}Parameter Priority Example
Given this configuration:
# Environment variables
export WLST_ADMIN_URL=t3://dev-server:7001
export WLST_USERNAME=dev_user
export WLST_PASSWORD=dev_passwordAnd this tool call:
{
"tool": "wlst_list_servers",
"params": {
"admin_url": "t3://prod-server:7001"
}
}The resolved values will be:
Parameter | Value | Source |
|
| Tool parameter (override) |
|
| Environment variable (fallback) |
|
| Environment variable (fallback) |
Response Formats
Most tools support two output formats:
markdown: Human-readable formatted output (default)
json: Machine-readable JSON output for programmatic use
License
Apache License 2.0 - See LICENSE for details.
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/SPS-Tech-is-now/weblogic-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server