capa restart

Restart the CAPA server to apply configuration changes.

Usage

capa restart

Description

Stops the currently running CAPA server and starts it again. This is equivalent to running capa stop followed by capa start.

When to Use

  • After modifying the capabilities file
  • After adding or removing skills
  • When MCP servers are misbehaving
  • To reload environment variables or credentials
  • After system updates or configuration changes

What Happens During Restart

  1. All MCP server subprocesses are stopped
  2. Active sessions are terminated
  3. The CAPA server process is stopped
  4. A new CAPA server process is started
  5. The server reloads the capabilities file
  6. MCP servers are restarted on-demand as tools are requested

Notes

  • Your MCP client will briefly lose access to tools during the restart
  • You may need to reload or restart your MCP client to reconnect
  • The restart typically takes a few seconds

Alternative: capa install

If you've made significant changes to your capabilities file (adding new skills, servers, or tools), it's often better to use capa install instead, as it will:

  • Reinstall skills to client directories
  • Update MCP client configurations
  • Prompt for any new credentials
  • Restart the server with the new configuration

Related Commands