myCobot MCP(Model Context Protocol) server
myCobot MCP(Model Context Protocol) server. Exposed over MCP by the mycobot mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
This MCP can send simple pick-and-place instructions to myCobot.
Everything the assistant can do here goes through one of these:
Hardware — The Hardware tool exposed by this serverParameters — Create a settings.json file to configure the myCobot hardware and the camera. The sample isSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
You will need one environment variable: DDS_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MyCobot MCP's toolset — Hardware, Parameters — is a fair guide to whether it matches your workflow. It is maintained by neka-nat; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Hardware | The Hardware tool exposed by this server. |
| Parameters | Create a settings.json file to configure the myCobot hardware and the camera. The sample is [here](https://github.com/neka-nat/mycobot-mcp/blob/master/data/sample_settings.json). |
{
"mcpServers": {
"mycobot": {
"command": "uvx",
"args": [
"mycobot-mcp",
"--settings-path",
"/path/to/settings.json"
],
"env": {
"DDS_API_TOKEN": "your-api-token"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DDS_API_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.