Skip to main content
Wipe.me runs as a local stdio MCP server. Your AI application starts wipeme mcp as a child process, so there is no MCP URL, account login, bearer token, or public server to configure.

​
Install the CLI first

The MCP server is included in the wipeme CLI beginning with the v0.3.0-alpha.3 prerelease. For the most common macOS installation:
Then verify the MCP command:

All CLI installation methods

See APT, DNF, direct archives, Go installation, architectures, checksums, and Windows/WSL notes.
Run command -v wipeme to find the absolute binary path. Desktop applications may not inherit your shell PATH, so an absolute path is often more reliable.

​
OpenAI: ChatGPT desktop

ChatGPT desktop, Codex CLI, and the Codex IDE extension share the same local MCP configuration.
  1. Open Settings.
  2. Select MCP servers.
  3. Select Add server.
  4. Enter wipeme as the name and choose STDIO.
  5. Set the command to the absolute path reported by command -v wipeme.
  6. Set the arguments to mcp.
  7. Save, then select Restart.
In the composer, use /mcp to confirm that Wipe.me is connected and inspect its available tools.
ChatGPT web does not read local MCP configuration. Use the desktop application for this local stdio server. Hosted ChatGPT plugins use a different, remote MCP model.

​
OpenAI: Codex CLI

Add Wipe.me from a terminal:
Verify the connection:
Inside the Codex terminal interface, use /mcp to see the active server and tools. Because Codex clients share ~/.codex/config.toml, this configuration is also available to ChatGPT desktop and the Codex IDE extension on the same machine. For an explicit absolute-path configuration:

​
OpenAI: Codex IDE extension

You can reuse the configuration created by ChatGPT desktop or Codex CLI. To add it through the extension instead:
  1. Open the gear menu and select MCP servers.
  2. Select Add server.
  3. Choose STDIO and provide the wipeme command with the mcp argument.
  4. Save and select Restart extension.

​
Anthropic: Claude Code

Add Wipe.me as a user-scoped local stdio server using Claude Code’s MCP configuration:
Check its status:
Inside Claude Code, /mcp shows the connected tools. If Claude Code cannot find wipeme, remove the entry and add it again using the absolute binary path.

​
Anthropic: Claude Desktop

Wipe.me is a local binary MCP server. Until it is packaged as a Claude Desktop extension, configure it as a local development server in claude_desktop_config.json:
Fully quit and reopen Claude Desktop after saving the configuration. Open Developer settings to check server status and logs, or select + in the chat composer and open Connectors to inspect connected tools. Local Wipe.me MCP is not available in claude.ai or Claude Cowork. Those surfaces use remote connectors; wipeme mcp intentionally supports local stdio only.

​
Choose an access policy

The default command starts host mode:
Host mode relies on the AI application’s approvals, sandbox, operating-system account, and filesystem permissions. It is the simplest choice for a trusted local desktop setup. Use restricted mode when Wipe.me should add its own path, environment-name, and process-profile allowlists:
For example, change a platform’s arguments from ["mcp"] to:
Restricted filesystem tools remain unavailable until Wipe.me configuration defines explicit read and write roots. Restricted process execution requires configured producer or consumer profiles. Inspect the effective non-secret policy at any time:
Restart the AI application after changing its launcher environment or the Wipe.me MCP configuration.

​
Test the connection safely

Ask the agent to generate a temporary password with a short expiry. A successful result contains a private link and non-secret metadata, never the generated value.
AI platform transcripts may retain returned private links. A private link is a bearer capability even when plaintext is absent. Limit transcript access, prefer short expiries for tests, and delete unused messages.

MCP workflows

Use generated passwords, environment files, protected folders, and direct process injection.

CLI installation

Review every supported operating-system installation method.