Connect Codex to Wachete
Set up in minutes
Choose where it runs
On your computer through your own Codex, or hosted in the cloud. The rest of setup adapts to your choice:
Pick what it can do in Wachete
A preset of real Wachete operations. Each one becomes a tool the agent can call, and it can't touch anything outside the list.
Connect Wachete
One sign-in. The agent acts through your account, scoped to the operations you picked.
Add your personal MCP link
The last step mints a private MCP URL for this agent and walks you through exactly this, with your real link filled in. The page flips to Connected the moment your Codex first calls in. Codex connects when a session starts — run codex, or restart a running one (in the Codex app, Restart).
Run this in your terminal. The Codex app shares its config, so it gets the server too
<your-link> is your personal server URL — setup mints it for you.
Tools Codex gets
Wachete
12 toolsRead root or selected folder contents, one page at a time.
Delete a folder and every nested folder and monitor.
Create a folder, or update it when a folder ID is supplied.
Move the selected monitors and folders to a destination folder.
Read a monitor's definition and latest data.
Delete a monitor and its monitoring configuration.
Search monitors; Wachete returns at most 500 results.
Read the pages belonging to a portal/crawler monitor.
Read one page of a monitor's content history.
Read triggered notifications, newest first, optionally for one monitor.
Read a notification's HTML content in its JSON response envelope.
Create or replace a monitor definition with one PUT; supply its ID to update. Updating sends the supplied definition, not a patch. Include all settings you want to retain, including alerts and notification endpoints.
About Codex
Frequently asked questions
More ways to connect
Open your Codex agent in one click.
NoClick runs Codex for you with Wachete wired in as tools. Connect your account and run.