myCobot MCP

Created By
neka-nata year ago
myCobot MCP(Model Context Protocol) server
Overview

what is myCobot MCP?

myCobot MCP (Model Context Protocol) is a server designed to facilitate communication with the myCobot robotic arm, allowing it to execute pick-and-place instructions based on image feedback.

how to use myCobot MCP?

To use myCobot MCP, set up the server by configuring the necessary settings in the settings.json file, connect the myCobot hardware, and ensure you have the required DDS API token for object detection.

key features of myCobot MCP?

  • Sends pick-and-place instructions to myCobot.
  • Requires image feedback for operation.
  • Configurable settings for hardware and camera integration.

use cases of myCobot MCP?

  1. Automating object manipulation tasks with myCobot.
  2. Integrating visual feedback for enhanced robotic operations.
  3. Customizing robotic behavior through configuration settings.

FAQ from myCobot MCP?

  • What hardware is required to run myCobot MCP?

You need a myCobot robotic arm, a suction pump, and a camera flange for proper operation.

  • How do I obtain the DDS API token?

You can register and issue an API key at the DDS cloud platform.

  • Is there a specific operating system required?

The project can be run on Ubuntu with the installation of Claude-Desktop.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
neka-nat
Star
3
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

8 hours ago
Alloy

2 days ago