Watchpost for Cursor

Check purchases made through your Cursor workflow.

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.

See supported connectionsHow it works
Connection path
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. Install Node.js with npm first; see /install for prerequisites.
Illustrative verdicts · sample outcomes

What it looks like with Cursor.

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

Sample approval: no risks flagged, with the amount within your account's purchase and daily limits.

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

Above your ask-me threshold for AI credits. Review it in your dashboard; alerts require setup. The integration must wait.

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

Your setup, step by step.

  1. 01
    Sign up

    Email and a password. No credit card to start.

  2. 02
    Set your rules

    Set purchase, daily and monthly limits for your account. Choose an amount above which you want to review a purchase. These limits apply across your connected agents; separate category budgets are not available.

  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

    Ask your agent to check a sample purchase without paying. Find the decision in your dashboard and confirm that the agent waits for review or stops on a block.

Frequently asked

Specific to Cursor.

Does this slow my Cursor agent down?
Each submitted purchase adds a check before payment. Timing depends on merchant lookups, listing analysis and cached data. A review also waits for your decision. Test the full path with your workflow before relying on it.
Can I bypass Watchpost for trusted vendors?
There is no merchant-specific bypass rule today. Your account's spending limits apply to all submitted purchases, and merchant and listing checks still run. Raising a limit changes it for every merchant, so it should not be used as a substitute for a vendor exception.
What about CI/CD agents that aren't Cursor?
Custom agents can call Watchpost's bearer-token API. Generate a connection token, submit to /v1/verify, and make the integration honor review and block decisions before paying. See /docs/api for the request format.

Check the setup for Cursor.

The free plan includes 10 purchase checks a month. Confirm the connection with a sample check before relying on it.

See supported connectionsSee pricing