Commercial only. These commands use the MCP executable supplied for your Commercial deployment. The Community installer includes its own local MCP server, ELNCommunityMCP.exe; its local notebook setup is not the Commercial registry/server workflow. See AI Integration for edition boundaries and contact APS for Commercial deployment.
Cursor supports MCP and lets you use the ELN server with GPT, Gemini, Claude, or any other model offered in its Agent mode. The tools behave identically across models — pick the model from Cursor’s Agent dropdown without changing anything in the MCP setup.
Prerequisites
- Cursor installed
- E-Lab Notebook installed; see the MCP server overview for the location of
ELNMCPServer.exe
Registering the Server
Create or edit mcp.json in one of two locations:
- Global:
%USERPROFILE%\.cursor\mcp.json— available in every project - Project:
.cursor\mcp.jsonin the repository root — overrides the global entry of the same name
Add an eln entry under mcpServers:
{
"mcpServers": {
"eln": {
"type": "stdio",
"command": "C:\\Program Files (x86)\\E-LabNotebook3\\ELNMCPServer.exe"
}
}
}
Verifying Registration
Open Settings (Ctrl+Shift+J) → Features → Model Context Protocol. The eln server should appear in the list with its tools enumerated; toggle it on if it isn’t already. If the server fails to start, open the Output panel (Ctrl+Shift+U) and select MCP Logs from the dropdown to see startup errors.
See Also
- AI Integration (MCP Server) — overview and full tool reference
- Connecting from Claude Code