ZStudio EIS MCP server: data validation, DRT, equivalent-circuit fitting, and plotting.
Connect Runs on your machine
claude mcp add zstudio -e ZSTUDIO_LICENSE_KEY=<ZSTUDIO_LICENSE_KEY> -e ZSTUDIO_WORKDIR=<ZSTUDIO_WORKDIR> -e ZSTUDIO_AUTOSAVE=<ZSTUDIO_AUTOSAVE> -- dnx FieldCure.Mcp.ZStudio --yes
{
"mcpServers": {
"zstudio": {
"command": "dnx",
"args": [
"FieldCure.Mcp.ZStudio",
"--yes"
],
"env": {
"ZSTUDIO_LICENSE_KEY": "<ZSTUDIO_LICENSE_KEY>",
"ZSTUDIO_WORKDIR": "<ZSTUDIO_WORKDIR>",
"ZSTUDIO_AUTOSAVE": "<ZSTUDIO_AUTOSAVE>"
}
}
}
}
{
"mcpServers": {
"zstudio": {
"command": "dnx",
"args": [
"FieldCure.Mcp.ZStudio",
"--yes"
],
"env": {
"ZSTUDIO_LICENSE_KEY": "<ZSTUDIO_LICENSE_KEY>",
"ZSTUDIO_WORKDIR": "<ZSTUDIO_WORKDIR>",
"ZSTUDIO_AUTOSAVE": "<ZSTUDIO_AUTOSAVE>"
}
}
}
}
{
"servers": {
"zstudio": {
"type": "stdio",
"command": "dnx",
"args": [
"FieldCure.Mcp.ZStudio",
"--yes"
],
"env": {
"ZSTUDIO_LICENSE_KEY": "<ZSTUDIO_LICENSE_KEY>",
"ZSTUDIO_WORKDIR": "<ZSTUDIO_WORKDIR>",
"ZSTUDIO_AUTOSAVE": "<ZSTUDIO_AUTOSAVE>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
ZSTUDIO_LICENSE_KEYOptional | |
ZSTUDIO_WORKDIROptional | |
ZSTUDIO_AUTOSAVEOptional |
Details
| Package | [email protected] (NUGET, stdio) |
| First published | 15 Oct 2026 |
| Last updated | 15 Oct 2026 |
| Registry name | io.github.fieldcure/zstudio |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
