Cursor
Add Grabbit to Cursor with mcp.json
Cursor supports remote Streamable HTTP servers in mcp.json. Use a global file for yourself or a project file for the team, while keeping credentials outside the repository.
Prerequisites
From setup to the first capture
- Cursor with MCP support
- A Grabbit account or API key
- A deployed or public target URL
{
"mcpServers": {
"grabbit": { "url": "https://mcp.grabbit.live" }
}
}Bearer alternative
{
"mcpServers": {
"grabbit": {
"url": "https://mcp.grabbit.live",
"headers": {
"Authorization": "Bearer ${env:GRABBIT_API_KEY}"
}
}
}
}For project configuration, prefer OAuth or Cursor environment interpolation. Never commit a literal sk_ key.
A test key returns a placeholder for wiring. The visual check below requires a live key and available credits. Call get_usage before a run when the agent needs to avoid an HTTP 402 interruption.
Call grab and inspect the result
Capture the deployed preview, inspect the screenshot, fix the spacing issue, then capture it again to verify the change.Expected result
Cursor lists the Grabbit tools under Available Tools and attaches the returned screenshot or exposes its hosted URL.
Image handling
Cursor documents image content from MCP tools. The model can inspect supported images directly, while image_url stays available.
Troubleshooting
401 or authentication required
Complete the client OAuth flow, or check that the environment variable contains a current sk_ key.
The target URL is rejected
Use a public HTTP or HTTPS URL. Grabbit blocks localhost, private, link-local, and internal network targets.
The image is a placeholder
An sk_test_ key proves the integration without spending credits. Use an sk_live_ key when you need a real render.
402 credits_exhausted
Call get_usage, then add a separately purchased top-up or wait for the next annual subscription grant before retrying.
Security note
Cursor asks for tool approval by default. Team admins can allowlist remote URLs and restrict tool auto-run behavior.
Hosted screenshots without a browser in the agent runtime
A local headless browser means installing Chromium, keeping its dependencies current, bounding memory use, and handling timeouts. Grabbit runs the screenshot step on hosted rendering infrastructure and returns an image URL.
Local headless browser
- Needs Chromium installed in the agent's runtime
- Cookie and consent handling belongs to your automation
- You own the timeouts, retries, and scaling
- Breaks in CI, sandboxes, and remote runners with no browser
Grabbit
- One call, nothing to install or run
- Dismisses cookie and consent banners automatically
- Handles lazy-loaded, JavaScript-heavy, and full-page captures
- Runs from CI or sandboxes without a local browser install
Grabbit accepts public pages and supports cookie-banner handling, delayed JavaScript, selector targeting, and full-page output. Target sites can still reject automated traffic, and private or internal addresses are blocked.
Flat pricing, built for agents that loop
When an agent captures a page on every step, per-call metering turns into anxiety. Grabbit is one flat rate: $50 per year for 25,000 captures ($0.002 each). Annual subscription credits expire at term end; separately purchased top-ups do not expire while your account remains active. Test-environment keys render placeholders for integration checks. A real page capture needs a live key and available credits.
Cursor FAQ
- Should I use a global or project mcp.json?
- Use ~/.cursor/mcp.json for personal setup. Use .cursor/mcp.json for shared server definitions, with OAuth or environment-backed credentials.
- Can Cursor inspect the returned screenshot?
- Yes. Cursor documents image returns from MCP tools. Grabbit also returns image_url for explicit access.
Give Cursor eyes in two minutes
Free wiring test, one install, then your agent can screenshot public pages with a live key.