Smart Me vs Dxpert.ai — industrial AI Readiness & UNS agents
A side-by-side look at the Smart Me and Dxpert.ai — industrial AI Readiness & UNS agents MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Smart Me for industrial & iot work over a hosted endpoint; choose Dxpert.ai — industrial AI Readiness & UNS agents for industrial & iot as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Smart Me when
- You need dedicated capabilities in the Industrial & IoT domain.
- You prefer a remote HTTP/SSE transport.
Choose Dxpert.ai — industrial AI Readiness & UNS agents when
- You need dedicated capabilities in the Industrial & IoT domain.
- You prefer a local stdio subprocess transport.
- You want tools like
pro_allowance_exhausted, shift-report, oee-narrator.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Industrial & IoT | Industrial & IoT |
| Quality signal | 37/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 12 |
| Full listing | View Smart Me | View Dxpert.ai — industrial AI Readiness & UNS agents |
Tools & capabilities
Smart Me tools
No tool names declared yet. Check the project README from the listing page.
Dxpert.ai — industrial AI Readiness & UNS agents tools 12
pro_allowance_exhaustedshift-reportoee-narratoralarm-triagemaintenance-copilotroot-causeoeefreeproproductcheckout_urlDXPERT_API_KEY
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Smart Me
{
"mcpServers": {
"smart-me-2": {
"url": "https://mcp.smart-me.com/mcp"
}
}
}
Dxpert.ai — industrial AI Readiness & UNS agents
{
"mcpServers": {
"dxpert-ai-industrial-ai-readiness-uns-agents": {
"command": "npx",
"args": [
"-y",
"@dxpert/mcp"
]
}
}
}
Frequently asked questions
Smart Me is categorized under Industrial & IoT and uses a remote HTTP/SSE transport. Dxpert.ai — industrial AI Readiness & UNS agents belongs to Industrial & IoT and uses a local stdio subprocess. Pick Smart Me for industrial & iot work and Dxpert.ai — industrial AI Readiness & UNS agents for industrial & iot.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Smart Me has no declared pricing — check the project's own site. Dxpert.ai — industrial AI Readiness & UNS agents has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add smart-me-2 and dxpert-ai-industrial-ai-readiness-uns-agents as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Smart Me has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Dxpert.ai — industrial AI Readiness & UNS agents has 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars.