MCP integration

wisp mcp exposes Wisps as tools over MCP stdio: create a sandbox, run commands, read and write files, manage sessions, and save checkpoints.

Have ready

• The wisp CLI from the public releases.
• Your API URL and a team API token. See authentication.

Steps

1. Configure your MCP client with command wisp, arguments ["mcp"], and credentials in its local secret configuration. A common configuration shape is:

   {
     "mcpServers": {
       "wisps": {
         "command": "wisp",
         "args": ["mcp"],
         "env": {
           "WISPS_URL": "https://api.example.com",
           "WISPS_TOKEN": "<YOUR_TEAM_API_TOKEN>"
         }
       }
     }
   }

2. Restart or reconnect your MCP client. Ask it to create a wisp, write a small script, run it, and delete the wisp.

Check

Your client lists create_wisp, run, read_file, and write_file among the available tools. The script’s output appears in the tool result.

Scope

The server creates ephemeral sandboxes by default. Keep credentials in local configuration outside version control. A shared pinned wisp is selected with --wisp NAME; use a separate wisp per agent when their files must stay separate.