AI / MCP

The VSIX exposes eve-iac tools to Copilot Agent, Cursor Agent, Claude Code, and Codex. You talk in natural language. The model calls tools. You should not type /eve_iac_status as a user command.

One owner window

Copilot and Cursor attach over stdio in the owner window. Do not create .vscode/mcp.json or .cursor/mcp.json.

Claude Code: command palette EVE IaC: Configure Claude Code. Codex: EVE IaC: Configure Codex. Those hosts write stdio config on demand. They do not store the EVE password.

The stdio process has no EVE credentials. Tools run in the owner VSIX, which already has Configure Connection.

If tools are missing

This IDE agent is not attached to the eve-iac MCP bridge. Use GitHub Copilot Agent or Cursor Agent with the eve-iac extension, or Configure Connection in the sidebar.

If a tool returns eve_iac_initializing, wait and retry. That is startup, not a missing password.

If it returns authentication_required, use Configure Connection.

If it returns tls_untrusted or tls_pin_mismatch, Trust the fingerprint in Configure Connection. Do not treat that as a missing password.

Safety the model must not skip

  • Destroy and prune need confirm=true and an explicit user request.
  • Wipe needs confirm=true unless Live config apply is on for that lab.
  • Never mutate source_lab.
  • Never invent interface names; the model must call the interfaces tool first.

Selecting a lab in the tree does not start or stop nodes.

What to ask

Ask for status, validate, plan, deploy, consoles, or “why is BGP down” after the lab is running. A new lab still needs you to Create or Import first.