Copy, connect, capture

Framejet where the work already happens.

One HTTPS endpoint for agents, one image endpoint for applications and CI. Both use the same key and quota.

MCP

Claude and Claude Code

Add the remote endpoint, send the key as a bearer token, then ask the agent to capture or navigate to a public page.

https://framejet.dev/mcp
Authorization: Bearer YOUR_KEY

MCP

Cursor

Use the same hosted MCP endpoint. There is no local package and no Chromium process to keep alive.

{"mcpServers":{"framejet":{"url":"https://framejet.dev/mcp","headers":{"Authorization":"Bearer YOUR_KEY"}}}}

GitHub Actions

Store the API key as FRAMEJET_API_KEY and capture a deploy preview or a known public URL during a workflow.

- name: Capture deploy
  run: curl -f -H "X-Api-Key: ${{ secrets.FRAMEJET_API_KEY }}" -o shot.png "https://framejet.dev/v1/take?url=https://example.com"

REST

n8n, Make and HTTP clients

Send a GET request, add X-Api-Key, and treat the response as a binary PNG or JPEG — there is no JSON wrapper.

GET https://framejet.dev/v1/take?url=https://example.com
X-Api-Key: YOUR_KEY

Start with a real page. Get a free key, paste one of the snippets, and make the first capture in minutes. Get 200 free screenshots.