Obsbot MCP vs Picocalc MCP
A side-by-side look at the Obsbot MCP and Picocalc MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Obsbot MCP for embedded system work as a local process; choose Picocalc 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 Obsbot MCP when
- You need dedicated capabilities in the Embedded System domain.
- You prefer a local stdio subprocess transport.
- You want tools like
obsbot_devices, obsbot_wake, obsbot_sleep.
Choose Picocalc MCP when
- You need dedicated capabilities in the Embedded System domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Embedded System | Embedded System |
| Quality signal | 63/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 |
Tools & capabilities
Obsbot MCP tools 80
obsbot_devicesList attached OBSBOT-compatible cameras. Each entry is { serial?, locationId?, name, status, reason? }: serial is the value to pass as `camera` to any camera-addressing tool (present where obtainable — reading it requires briefly opening the camera); status is available (free to bind), bound (already opened by this process), or busy (could not be opened and identified, so it can't be targeted here — usually another process holds it, but it also covers a camera that opened yet would not answer). On a busy entry, `reason` carries the underlying error and distinguishes those cases.obsbot_wakeWake the camera/gimbal (sends "run"). This MOVES the camera: waking un-stows the gimbal and brings it back to level (pitch ~0). Most control commands also wake the camera implicitly as a side effect.obsbot_sleepSleep the camera/gimbal (sends "sleep"). This MOVES the camera: sleeping STOWS the gimbal, tilting it face-down to roughly pitch 84°, so obsbot_gimbal_position will read ~84 rather than the pose you left it in. obsbot_wake un-stows it.obsbot_gimbal_moveMove the gimbal to an absolute yaw/pitch angle (degrees); positive yaw pans to the camera's left, positive pitch tilts down. Yaw is clamped to [-130,130], pitch to [-90,90]. Absolute positioning (1:1 degrees), verified on hardware.obsbot_gimbal_recenterRecenter the gimbal — drives it back to yaw 0 / pitch 0 (level and facing forward). Returns as soon as the command is sent: the gimbal may still be moving, so poll obsbot_gimbal_position if you need to know it has arrived.obsbot_zoom_uvcStandard UVC zoom: set an absolute zoom ratio, clamped to [1.0, 2.0]. Snaps to the requested target exactly (unlike obsbot_zoom_vendor, whose ratio scale differs and may not land exactly where asked). Waits for the zoom to actually arrive and returns { settled }: the ramp is not instant (a full 1.0->2.0 sweep takes about 2.4s), and obsbot_aim_at_pixel and obsbot_zoom_to_fit both refuse while it is in flight, so this returning early would just move the failure downstream. settled:false means the zoom had not arrived within the timeout — the command was still sent.obsbot_ai_track
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.
Obsbot MCP
{
"mcpServers": {
"lxman-obsbot-mcp": {
"command": "npx",
"args": [
"-y",
"obsbot-mcp"
]
}
}
}
Picocalc MCP
{
"mcpServers": {
"picocalc-mcp": {
"command": "uvx",
"args": [
"picocalc-mcp"
]
}
}
}
Frequently asked questions
Obsbot MCP is categorized under Embedded System and uses a local stdio subprocess. Picocalc MCP belongs to Embedded System and uses a local stdio subprocess. Pick Obsbot MCP for embedded system work and Picocalc 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.
Obsbot MCP has no declared pricing — check the project's own site. Picocalc MCP 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 lxman-obsbot-mcp and picocalc-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Obsbot MCP has a quality signal of 63/100 (Good) with 2 views, 0 installs and 1 GitHub stars. Picocalc MCP has 40/100 (Fair) with 0 views, 0 installs and 80 GitHub stars.
