DME 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., "@DME MCP Serverlist all LUNs on the SAN storage"
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.
DME MCP Server
MCP Server for DME storage O&M
Exposes 16 action modules (427 actions) from dme-python-sdk as MCP V1 tools
MCP V1 (
mcp>=1.28,<2, FastMCP)Endpoint: a single root MCP Server at
<endpoint>/mcp/v1(e.g.http://127.0.0.1:8000/mcp/v1) — all module tools are registered on this one server, no per-module mountsTool naming: dot-separated
<topic>.<action_key>(e.g.san.lun_list)Annotation: every tool carries
annotations.topic(e.g.san),annotations.subtopic(e.g.lun) andannotations.action(e.g.list) — extension fieldsDocstring parsing: action function docstrings are parsed into the tool's
description/inputSchema(parameter descriptions) /outputSchema(Returns fields); supports both the Chinese (default branch) and English (main-enbranch) docstrings ofdme-python-sdkBlacklist: modeled after
cli.py;~/.config/pydme/blacklist.jsontakes precedence. Every blacklisted tool gets an extra optionalaccept_riskparameter (default from--accept-risk/DME_ACCEPT_RISK); calling it withoutaccept_risk=trueis rejected with aRISK_BLOCKEDresponse telling the caller to set it explicitly
Installation
# Install dependency (Chinese)
pip install git+https://github.com/agentic-data-ops/dme-python-sdk.git
# Or install dependency (English)
pip install git+https://github.com/agentic-data-ops/dme-python-sdk.git@main-en
# Install the MCP Server
pip install git+https://github.com/agentic-data-ops/dme-mcp-server.gitRelated MCP server: devops-mcp-server
Usage
# streamable-http (default); DME connection params match the pydme CLI.
# Listens on 127.0.0.1:8000 unless --mcp-server or DME_MCP_SERVER is set.
dme-mcp-server --mcp-server 0.0.0.0:8000 \
--endpoint https://192.168.1.100:26335 --user admin --password xxx
# Or use environment variables (omitting --mcp-server uses the 127.0.0.1:8000 default)
export DME_API_ENDPOINT=https://192.168.1.100:26335
export DME_API_USERNAME=admin
export DME_API_PASSWORD=xxx
dme-mcp-server
# stdio mode (--mcp-server is just a startup switch)
dme-mcp-server --mcp-server x --mcp-transport stdio \
--endpoint ... --user ... --password ...Connecting
All module tools live on a single root MCP server. Point your MCP client at:
http://<host>:<port>/mcp/v1— e.g.http://127.0.0.1:8000/mcp/v1
tools/list returns every action from all modules; each tool is named <topic>.<action_key>, so clients can group/filter by module on the <topic> prefix. Every tool also carries annotations.topic / annotations.subtopic / annotations.action (non-standard extension fields, for reference).
Options
Option | Environment variable | Description |
|
| DME API address |
|
| Username |
|
| Password |
|
| Auth token (optional; skips login when provided) |
| — | Request timeout (default 90) |
| — | Disable token caching |
|
| Default |
|
| Listen address |
| — |
|
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
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.
Related MCP Connectors
MCP server for Product Management
Scans remote MCP servers for protocol, security, and TLS issues; exposes scan tools via MCP.
MCP server for AI access to Swagger by SmartBear.
Governed data discovery, exact queries, decisions, simulations, and runtime utilities over MCP.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to discover and execute tools via a secure MCP server with JWT authentication, RBAC, rate limiting, and audit logging.1MIT
- FlicenseNot gradedqualityCmaintenanceExposes DevOps/SRE operations like Kubernetes pod status, Prometheus metrics queries, and deploy history as tools for MCP-compatible clients.-
- AlicenseNot gradedqualityBmaintenanceEnables aggregation, filtering, transformation, and composition of tools from multiple MCP servers through a single proxy with tool views.5AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable clients to query the tool registry, check install status, get tool recommendations for CTF or bug-bounty work, and run installed security tools through a governed execution path.47MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/agentic-data-ops/dme-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server