Watchpost for Cursor

A safety net for what your Cursor agent spends on.

When a Cursor workflow is about to buy cloud compute, API credits, or another service, it can call Watchpost first. Watchpost checks the merchant, scans the listing, and applies your spend caps. This is a cooperating-agent guardrail, not a payment interceptor.

Get WatchpostHow it works
One command
npx @watchpost/mcp install
The CLI confirms your account in the browser and writes the MCP entry into Cursor's settings (~/.cursor/mcp.json). After a Cursor restart, the agent has the verdict tools available.
Real verdicts

What it looks like with Cursor.

Approved09:08
fly.ioCompute credit top-up
$25.00

Trusted infrastructure provider. Within your daily cap for cloud_compute. Approved.

Review09:14
anthropic.comAPI credits — $250
$250.00

Above your ask-me threshold for AI credits. You get a push; the agent waits.

Blocked08:51
free-credits.exampleCompute bonus pack
$80.00

New domain, listing has prompt-injection text aimed at the AI. Watchpost blocks. Agent reports back and continues with a known provider.

Setup with Cursor

Five minutes, no surprises.

  1. 01
    Sign up

    Email and a password. No credit card to start.

  2. 02
    Set your rules

    Caps and ask-me thresholds. For Cursor users we recommend tighter daily caps on cloud_compute and ai_api_credits, since those are the categories the background agent spends on most.

  3. 03
    Run the installer

    On the machine running Cursor: npx @watchpost/mcp install. The CLI writes the MCP entry into Cursor's config.

  4. 04
    Restart Cursor

    Open Cursor's MCP settings to confirm Watchpost is listed. Your agent now has watchpost_check_purchase available.

  5. 05
    Watch the dashboard

    As your agent works, verdicts stream into your dashboard. Tweak your rules based on what you see.

Frequently asked

Specific to Cursor.

Does this slow my Cursor agent down?
About a second per purchase. The trust + listing + rules checks run in parallel. For a coding agent making compute or API purchases, this is well within the noise.
Can I bypass Watchpost for trusted vendors?
Add their domains to a custom rule that auto-approves below a cap (this is on the roadmap; today, the same per-purchase cap applies to every merchant). For now, raising the cap on a category like cloud_compute is the closest equivalent.
What about CI/CD agents that aren't Cursor?
Any agent that speaks Bearer-token API can call Watchpost directly. Generate a connection token from the dashboard and POST to /v1/verify with the same shape the MCP tools use. The whole API is documented in the changelog.

Switch it on for Cursor.

Free for 10 verdicts a month. Upgrade only when your agent gets busy.

Get WatchpostSee pricing