Opentronsai Mcp Server
by opentronsco.huggingface.opentrons/opentronsai-mcp-server
OpentronsAI-MCP server
- Remote endpoint
- 3 tools
Uptime
Checked · every day
100%from 4 days of checks
Up without downtime on 4 of 4 days with data.
- No downtime
- Degraded
- Down over 5 minutes
- No data
- Not checked yet
Response time
Median 1047 ms, slowest 5% 1209 ms for the handshake and the tool list, over 30 days.
How far each check got
- Reached the address 100%
- Completed the handshake 100%
- Listed its tools 100%
3 tools at the last answer.
Every day
| Day | Result | Checks | Median |
|---|---|---|---|
| 3 Nov (today) | No downtime | 1 | 1149 ms |
| 2 Nov | No downtime | 1of 1 | 1059 ms |
| 1 Nov | No downtime | 1of 1 | 982 ms |
| 31 Oct | No downtime | 1 | 1117 ms |
A failure counts as down time only when a second check five minutes later fails too. How we check
Connect to the publisher's own endpoint
Paste into Settings › Connectors › Add custom connector:
https://opentrons-opentronsai-mcp-server.hf.space/gradio_api/mcp/sse Run in a terminal:
claude mcp add --transport sse opentronsai-mcp-server https://opentrons-opentronsai-mcp-server.hf.space/gradio_api/mcp/sse Add to ~/.cursor/mcp.json:
Add to ~/.config/devin/mcp_config.json:
Add to mcp.json (Program › Install › Edit mcp.json):
Add to ~/.gemini/settings.json:
Add to config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows):
Add to ~/.config/eca/config.json (global) or .eca/config.json in the project:
{
"mcpServers": {
"opentronsai-mcp-server": {
"url": "https://opentrons-opentronsai-mcp-server.hf.space/gradio_api/mcp/sse"
}
}
} Add to .vscode/mcp.json:
{
"servers": {
"opentronsai-mcp-server": {
"type": "sse",
"url": "https://opentrons-opentronsai-mcp-server.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.config/zed/settings.json:
{
"context_servers": {
"opentronsai-mcp-server": {
"url": "https://opentrons-opentronsai-mcp-server.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
Add to anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
Add to Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
{
"mcpServers": {
"opentronsai-mcp-server": {
"type": "sse",
"url": "https://opentrons-opentronsai-mcp-server.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.continue/config.yaml:
mcpServers:
- name: "opentronsai-mcp-server"
type: sse
url: "https://opentrons-opentronsai-mcp-server.hf.space/gradio_api/mcp/sse" Add to ~/.config/goose/config.yaml:
extensions:
"opentronsai-mcp-server":
type: streamable_http
name: "opentronsai-mcp-server"
enabled: true
uri: "https://opentrons-opentronsai-mcp-server.hf.space/gradio_api/mcp/sse"
headers: {}
env_keys: []
envs: {}
timeout: 300 This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Run in a terminal:
codex mcp add opentronsai-mcp-server --url https://opentrons-opentronsai-mcp-server.hf.space/gradio_api/mcp/sse This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.llm/config.json:
Add to resources/assets/config/mcp.json in the installed app:
Add to ~/.boltai/mcp.json:
Add to ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
{
"mcpServers": {
"opentronsai-mcp-server": {
"url": "https://opentrons-opentronsai-mcp-server.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/agenvoy/mcp.json:
{
"servers": {
"opentronsai-mcp-server": {
"url": "https://opentrons-opentronsai-mcp-server.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
{
"amp.mcpServers": {
"opentronsai-mcp-server": {
"url": "https://opentrons-opentronsai-mcp-server.hf.space/gradio_api/mcp/sse"
}
}
} For agents: the install prompt
Every step above as one Markdown text, for an assistant installing it for you.
# Install the MCP server Opentronsai Mcp Server (`co.huggingface.opentrons/opentronsai-mcp-server`)
Its page: https://plug.directory/servers/co.huggingface.opentrons/opentronsai-mcp-server
It runs on the publisher's servers; the client connects to its URL.
Use the section for the person's client.
## Claude Desktop
Paste into Settings › Connectors › Add custom connector:
```text
https://opentrons-opentronsai-mcp-server.hf.space/gradio_api/mcp/sse
```
## Claude Code
Run in a terminal:
```sh
claude mcp add --transport sse opentronsai-mcp-server https://opentrons-opentronsai-mcp-server.hf.space/gradio_api/mcp/sse
```
## Cursor, Devin Desktop, LM Studio, Gemini CLI, oterm, ECA
Merge into the place for the person's client:
- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
```json
{
"mcpServers": {
"opentronsai-mcp-server": {
"url": "https://opentrons-opentronsai-mcp-server.hf.space/gradio_api/mcp/sse"
}
}
}
```
## VS Code
Merge into .vscode/mcp.json:
```json
{
"servers": {
"opentronsai-mcp-server": {
"type": "sse",
"url": "https://opentrons-opentronsai-mcp-server.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Zed
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Cline, AnythingLLM, Augment Code
Merge into the place for the person's client:
- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
- Augment Code: Augment Settings Panel – MCP section – Import from JSON (VS Code extension)
```json
{
"mcpServers": {
"opentronsai-mcp-server": {
"type": "sse",
"url": "https://opentrons-opentronsai-mcp-server.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Continue
Merge into ~/.continue/config.yaml:
```yaml
mcpServers:
- name: "opentronsai-mcp-server"
type: sse
url: "https://opentrons-opentronsai-mcp-server.hf.space/gradio_api/mcp/sse"
```
## Goose
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Codex
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## mcp-client-cli, TUUI, BoltAI, Bob Shell, Kiro, Kiro CLI
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Agenvoy
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Amp
Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
```json
{
"amp.mcpServers": {
"opentronsai-mcp-server": {
"url": "https://opentrons-opentronsai-mcp-server.hf.space/gradio_api/mcp/sse"
}
}
}
```
Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.
Tools 3
opentronsai_mcp_server_generate_protocolGenerate Opentrons protocols using AI. This tool automatically retrieves relevant API documentation and generates validated protocols based on your requirements. Returns: Generated protocol code with explanationopentronsai_mcp_server_get_relevant_api_docsRetrieves relevant API documentation based on the user's query. Use this tool when you need specific Opentrons API information to help generate protocols or answer technical questions about protocol implementation. Returns: XML-formatted relevant documentation contentopentronsai_mcp_server_simulate_protocolSimulates the python protocol on user input. Returned value is text indicating if protocol is successful. Returns: Text indicating if protocol is successful or error details
From Hugging Face Spaces. Report a problem