Troubleshooting the Eggplant Virtual Assistant
This issue only applies to Eggplant Studio extensions with the Eggplant Virtual Assistant enabled. The Eggplant Virtual Assistant uses Model Context Protocol (MCP) to interact with third-party AI assistants. See Using The Eggplant Virtual Assistant for information about the Eggplant Virtual Assistant, including how to enable it.
Connection Service MCP Tools are Unavailable
If the Eggplant Studio Connection Service Model Context Protocol (MCP) tools do not appear or are not usable to the Eggplant Virtual Assistant (or the third party AI assistant you installed for the Eggplant Studio Virtual Assistant):
-
Check if AI Assistance for Connections is enabled in VS Code Settings (
eggplantStudio.enableAIAssistanceForConnections) -
Verify you have a valid Eggplant license: The Eggplant Virtual Assistant requires an active Developer license. Expired or missing licenses block tool availability. If you see an error message about licensing, add or renew your license. See Licensing Eggplant Studio for information about obtaining licenses.
-
Confirm your organization allows MCP access: Some organizations disable MCP via VS Code policy (
chat.mcp.access = none). If you see an error about organizational policy, contact your IT administrator to request access. -
Update VS Code if needed: Older VS Code builds do not expose the MCP provider registration API. If you see an error about API availability, update to the latest VS Code version. See Downloading and Installing VS Code for more information about installing and updating VS Code.
-
Check if PCS is running: Eggplant Gateway Persistent Connection Service (PCS) must be running for the Eggplant Virtual Assistant connection-related tools to function. If PCS fails to start, connection-related MCP tools will not be available. Check the Eggplant Studio output channel for error messages.
If none of these steps resolve the issue, contact your system administrator or Product Support for Keysight Eggplant Software for additional assistance.