Picocalc MCP vs Ugs MCP
A side-by-side look at the Picocalc MCP and Ugs MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Picocalc MCP for embedded system work as a local process; choose Ugs MCP for embedded system as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Picocalc MCP when
- You need dedicated capabilities in the Embedded System domain.
- You prefer a local stdio subprocess transport.
Choose Ugs MCP when
- You need dedicated capabilities in the Embedded System domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
UGS_HOST, UGS_PORT, MACROS_DIR, RAPID_SPEED_MM_MIN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Embedded System | Embedded System |
| Quality signal | 40/100 · Fair | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | UGS_HOST |
Tools & capabilities
Picocalc MCP tools
No tool names declared yet. Check the project README from the listing page.
Ugs 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.
Picocalc MCP
{
"mcpServers": {
"picocalc-mcp": {
"command": "uvx",
"args": [
"picocalc-mcp"
]
}
}
}
Ugs MCP
{
"mcpServers": {
"zackpeters93-ugs-mcp": {
"command": "uvx",
"args": [
"ugs-mcp"
],
"env": {
"UGS_HOST": "YOUR_UGS_HOST_HERE",
"UGS_PORT": "YOUR_UGS_PORT_HERE",
"MACROS_DIR": "YOUR_MACROS_DIR_HERE",
"RAPID_SPEED_MM_MIN": "YOUR_RAPID_SPEED_MM_MIN_HERE"
}
}
}
}
Frequently asked questions
Picocalc MCP is categorized under Embedded System and uses a local stdio subprocess. Ugs MCP belongs to Embedded System and uses a local stdio subprocess. Pick Picocalc MCP for embedded system work and Ugs MCP for embedded system.
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.
Picocalc MCP has no declared pricing — check the project's own site. Ugs MCP is listed as free. Auth: no auth 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 picocalc-mcp and zackpeters93-ugs-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Picocalc MCP has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 80 GitHub stars. Ugs MCP has 48/100 (Fair) with 3 views, 0 installs and 6 GitHub stars.