Server Activation

When you install a stdio-based MCP server, it enters a pending state until its requirements are verified. This ensures the server can actually run before routing traffic to it.

HTTP servers skip this step since they are already running.

The requirements checklist

The activation panel shows what the server needs:

• Runtime: the command to run the server must be available (like node, python, npx, or uvx). Green if found on your system, red if missing.
• Required environment variables: credentials and config that the server needs. Green if set (in the vault or environment), red if missing.
• Optional environment variables: nice-to-have config that is not strictly required. Amber if missing.

Activating

Once all required items are green, click Activate. The server moves from pending to active, and tool calls can flow through it.

If a requirement is missing, install the missing runtime or add the missing secret to the vault, then click Re-check to refresh the checklist.

Why activation exists

Activation prevents a common frustration: installing a server, trying to use it, and getting cryptic errors because a dependency is missing. The checklist catches these issues before you hit them in your AI workflow.