← All integrations

Wachete MCP server

12 operations0 webhooks

Web change monitoring with Wachete - create and update monitors that watch a page or crawl a portal, read check history and diffs, list the notifications they triggered, and organise everything into folders.

Use Wachete in Claude, ChatGPT, Cursor or another MCP client

Connect Wachete once in Corsair, then add one MCP address to your agent.

Connect Wachete
Setup steps for Claude, ChatGPT, Cursor and Claude Code

Building your own app on the Corsair SDK? Get API keys

Try Wachete with your agent

Connect Wachete, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Wachete on my account, then run one read-only example and show me the result.

Runs once, when you ask

Wachete tools and triggers

Tools are what your agent can do in Wachete through Corsair's MCP server. Triggers are the Wachete events a routine can start from.

Tasks

  • DeleteDestructive

    Permanently delete a monitor and its history; this cannot be undone

    tasks.delete

  • GetRead-only

    Read one monitor with its settings, its last value and when that value changed

    tasks.get

  • PagesRead-only

    List the pages a Portal monitor is crawling

    tasks.pages

  • SearchRead-only

    Search monitors by name, returning at most 500 and no paging

    tasks.search

  • UpsertWrite

    Create a monitor, or update one by sending its id; sets the URL, the part of the page watched, how often to check and who to notify

    tasks.upsert

Folders

  • DeleteDestructive

    Delete a folder with every subfolder and monitor inside it; this cannot be undone

    folders.delete

  • ListRead-only

    List a folder subfolders and monitors, with the path to that folder

    folders.list

  • MoveWrite

    Move monitors and folders into another folder

    folders.move

  • UpsertWrite

    Create a folder, or rename and move one by sending its id

    folders.upsert

Notifications

  • GetRead-only

    Read one notification: the monitor name, URL, time and the HTML that was sent

    notifications.get

  • ListRead-only

    List triggered notifications newest first, filtered by monitor and date range

    notifications.list

Data

  • ListRead-only

    Read a monitor's check history, optionally as a diff per entry

    data.list

Connect Wachete to Claude, ChatGPT or Cursor

  1. 1

    Connect Wachete in Corsair

    Add your Wachete API key once in Corsair. Corsair stores the credential encrypted and makes the Wachete API calls for your agent, so it never goes into a prompt or a config file. Connect Wachete

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Wachete. On a ChatGPT personal plan, connect Wachete here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Wachete's read and write operations run right away and its 2 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/wachete, add the Wachete plugin, and connect with an API key. Then call methods like corsair.wachete.api.data.list() from your app. Corsair keeps each tenant isolated.

Yes. Wachete requires an API key from your Wachete account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Wachete, GitHub, Notion, Stripe, and the rest. Trigger Wachete from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for web change monitoring with Wachete - create and update monitors that watch a page or crawl a portal, read check history and diffs, list the notifications they triggered, and organise everything into folders. Common builds include sync jobs, admin tooling, and agents that call Wachete APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Wachete API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/wachete in the open repo. When Wachete ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Wachete data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Wachete data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Wachete on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 2 destructive Wachete operations. You can change a link's mode at hub.corsair.dev/me.