Claude Code
Add a screenshot tool to Claude Code with one MCP command
Claude Code recommends HTTP for remote MCP servers. Add the endpoint, authenticate from /mcp, and the grab tool is available in terminal and IDE sessions.
Prerequisites
From setup to the first capture
- Claude Code installed
- A public target URL
- A Grabbit account for OAuth or GRABBIT_API_KEY for Bearer auth
claude mcp add --transport http grabbit https://mcp.grabbit.live
claude mcp get grabbit
# Start Claude Code, run /mcp, then complete OAuth if prompted.OAuth keeps the key out of shell history. For CI, load a Bearer header from secret-managed environment state.
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
Screenshot the deployed preview at 1440×900, inspect the image, and report clipped text or off-screen controls.Expected result
Claude Code discovers grab, get_grab, list_grabs, get_usage, and get_pricing. The grab call returns a completed record and hosted image.
Image handling
Claude Code can inspect compatible MCP image content. image_url remains available for explicit read-back or artifacts.
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
Project-scoped MCP servers need workspace approval. Review the endpoint and tool list before approving a cloned project configuration.
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.
Claude Code FAQ
- Which transport should Claude Code use?
- Use remote HTTP. Anthropic documents HTTP as the recommended transport for cloud-hosted MCP servers.
- How do I verify the server connected?
- Run claude mcp get grabbit or claude mcp list. Then call grab to verify the actual tool result.
Give Claude Code eyes in two minutes
Free wiring test, one install, then your agent can screenshot public pages with a live key.