Dxpert.ai — industrial AI Readiness & UNS agents vs RoastPilot
A side-by-side look at the Dxpert.ai — industrial AI Readiness & UNS agents and RoastPilot MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Dxpert.ai — industrial AI Readiness & UNS agents for industrial & iot work as a local process; choose RoastPilot 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 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.
Choose RoastPilot when
- You need dedicated capabilities in the Industrial & IoT domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Industrial & IoT | Industrial & IoT |
| Quality signal | 55/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | 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 | 12 | Not listed |
| Full listing | View Dxpert.ai — industrial AI Readiness & UNS agents | View RoastPilot |
Tools & capabilities
Dxpert.ai — industrial AI Readiness & UNS agents tools 12
pro_allowance_exhaustedshift-reportoee-narratoralarm-triagemaintenance-copilotroot-causeoeefreeproproductcheckout_urlDXPERT_API_KEY
RoastPilot tools
No tool names declared yet. Check the project README from the listing page.
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.
Dxpert.ai — industrial AI Readiness & UNS agents
{
"mcpServers": {
"dxpert-ai-industrial-ai-readiness-uns-agents": {
"command": "npx",
"args": [
"-y",
"@dxpert/mcp"
]
}
}
}
RoastPilot
{
"mcpServers": {
"roastpilot": {
"command": "uvx",
"args": [
"coffee-roaster-mcp"
]
}
}
}
Frequently asked questions
Dxpert.ai — industrial AI Readiness & UNS agents is categorized under Industrial & IoT and uses a local stdio subprocess. RoastPilot belongs to Industrial & IoT and uses a local stdio subprocess. Pick Dxpert.ai — industrial AI Readiness & UNS agents for industrial & iot work and RoastPilot 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.
Dxpert.ai — industrial AI Readiness & UNS agents has no declared pricing — check the project's own site. RoastPilot 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 dxpert-ai-industrial-ai-readiness-uns-agents and roastpilot as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dxpert.ai — industrial AI Readiness & UNS agents has a quality signal of 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars. RoastPilot has 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.