Smart Me vs Thingsboard MCP
A side-by-side look at the Smart Me and Thingsboard MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
Smart MeIndustrial & IoTRead and manage smart-me meters, charging stations, load management and ZEV billing37FairAuth: not declaredVerdict: choose Smart Me for industrial & iot work; choose Thingsboard MCP for industrial & iot over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
SChoose Smart Me when
- You need dedicated capabilities in the Industrial & IoT domain.
Choose Thingsboard MCP when
- You need dedicated capabilities in the Industrial & IoT domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
THINGSBOARD_URL, THINGSBOARD_API_KEY, THINGSBOARD_USERNAME, THINGSBOARD_PASSWORD, THINGSBOARD_LOGIN_INTERVAL_SECONDS, HTTP_BIND_ADDRESS, HTTP_BIND_PORT, SPRING_AI_MCP_SERVER_STDIO.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Smart Me | |
|---|---|---|
| Category | Industrial & IoT | Industrial & IoT |
| Quality signal | 37/100 · Fair | 51/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | THINGSBOARD_URLTHINGSBOARD_API_KEYTHINGSBOARD_USERNAMETHINGSBOARD_PASSWORDTHINGSBOARD_LOGIN_INTERVAL_SECONDSHTTP_BIND_ADDRESSHTTP_BIND_PORTSPRING_AI_MCP_SERVER_STDIO |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 98 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Smart Me | View Thingsboard MCP |
Tools & capabilities
Smart Me tools
No tool names declared yet. Check the project README from the listing page.
Thingsboard MCP 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.
Smart Me
No confirmed install command for Smart Me yet — follow the setup steps linked from its listing page rather than a guessed package name.
Thingsboard MCP
{
"mcpServers": {
"thingsboard-thingsboard-mcp": {
"url": "http://localhost:8000/sse"
}
}
}
Frequently asked questions
Smart Me is categorized under Industrial & IoT and uses an install path we have not confirmed yet. Thingsboard MCP belongs to Industrial & IoT and uses a remote HTTP/SSE transport. Pick Smart Me for industrial & iot work and Thingsboard MCP 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 confirmed install command yet — follow its own setup instructions.
Smart Me has no declared pricing — check the project's own site. Thingsboard MCP is listed as free. Auth: api key required. 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 and thingsboard-thingsboard-mcp 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. Thingsboard MCP has 51/100 (Good) with 5 views, 0 installs and 98 GitHub stars.