Connect Claude Code, Codex, and other AI assistants to capture websites and manage screenshot workflows

MCP server

Connect your AI assistant to Allscreenshots using the Model Context Protocol (MCP). Ask it to capture websites, retrieve images, process URLs in bulk, manage scheduled screenshots, search capture history, or check your usage.

Server URL:

https://mcp.allscreenshots.com/mcp/v1

The server uses Streamable HTTP. Connect directly from an MCP client with HTTP transport support; no local server or plugin installation is required.

Connect with your account

Enable MCP for your organisation

An organisation owner or admin opens API keys in the dashboard and selects Enable MCP in Connect your AI assistant.

This creates a dedicated MCP API key for usage tracking without displaying its secret. Organisation members can then connect with their own Allscreenshots accounts.

claude mcp add --transport http allscreenshots https://mcp.allscreenshots.com/mcp/v1

Open Claude Code, run /mcp, and authenticate the allscreenshots connection.

codex mcp add allscreenshots --url https://mcp.allscreenshots.com/mcp/v1
codex mcp login allscreenshots

Add an HTTP MCP server with the URL https://mcp.allscreenshots.com/mcp/v1 and use your client's OAuth sign-in flow. Clients that do not support OAuth can use the API-key setup below.

Sign in with your existing Allscreenshots account and choose an enabled organisation on the consent screen. The connection is bound to that organisation; reconnect to choose a different one.

Ask for a screenshot

Take a full-page screenshot of https://example.com and show me the result.

Your assistant calls the capture tool and receives a preview, an original download link, and capture metadata.

Existing credits, plan permissions, retention rules, and rate limits apply. OAuth captures appear under the dedicated MCP key in the dashboard's Usage page.

API keys for automation

Use an existing API key when connecting from an automated workflow or a client without OAuth support. Set ALLSCREENSHOTS_API_KEY in the environment where your client runs.

claude mcp add --transport http allscreenshots https://mcp.allscreenshots.com/mcp/v1 \
  --header "X-API-Key: ${ALLSCREENSHOTS_API_KEY}"

This command stores the expanded API key in Claude Code's local configuration. Keep that configuration private, or use account login above.

codex mcp add allscreenshots --url https://mcp.allscreenshots.com/mcp/v1 \
  --bearer-token-env-var ALLSCREENSHOTS_API_KEY

Ensure the environment variable is available when you start Codex.

Configure the server URL and one authentication header:

X-API-Key: YOUR_API_KEY

Or:

Authorization: Bearer YOUR_API_KEY

Send the header on each request. Credentials in URL query parameters are not accepted. Use one authentication method per connection.

API-key connections can access captures, bulk jobs, history, and schedules belonging to that key. Account login provides access within the organisation selected during consent. Usage and credit balances describe the organisation for both methods.

Available tools

Workflow	Tools	What you can do
Capture	`capture_screenshot`, `get_screenshot`, `get_screenshot_result`, `cancel_screenshot`	Capture a website, check its status, retrieve the result, or cancel a pending async capture
Bulk	`capture_screenshots_bulk`, `get_bulk_capture`, `list_bulk_captures`, `cancel_bulk_capture`	Submit up to 100 URLs, inspect progress, list batches, or cancel pending work
History and usage	`list_screenshots`, `get_usage`	Search captures and inspect credits, quota, and usage history
Schedules	`list_schedules`, `get_schedule`, `create_schedule`, `update_schedule`, `pause_schedule`, `resume_schedule`, `trigger_schedule`, `delete_schedule`, `get_schedule_history`	Manage recurring captures and view execution history

Example prompts

"Capture https://example.com at a 390 × 844 viewport without ads or cookie banners."
"Take a screenshot of https://example.com in dark mode and give me the original file."
"Capture these three URLs in bulk and show me the results when they finish."
"Create a schedule to capture https://example.com every day at 09:00 UTC."
"Pause the homepage monitoring schedule."
"Find my failed screenshots from yesterday."
"How many credits does this organisation have left?"

Capture options and results

capture_screenshot accepts the following arguments:

Argument	Description
`url`	Required HTTP or HTTPS URL to capture
`options`	Optional screenshot options, excluding `url` and `responseType`
`async`	Set to `true` to process in the background; defaults to `false`
`idempotencyKey`	Optional retry key: 1–100 letters, numbers, underscores, or hyphens

For example, these are the tool arguments for a full-page capture:

{
  "url": "https://example.com",
  "options": {
    "fullPage": true,
    "darkMode": true,
    "blockAds": true,
    "blockCookieBanners": true
  },
  "idempotencyKey": "example-dark-001"
}

For a long-running capture, set async to true. Use the returned id with get_screenshot until the status is COMPLETED, then call get_screenshot_result with the same id.

Image results include a JPEG preview with a longest edge of at most 1600 pixels and a size of at most 1 MiB. The original download is not resized. PDFs and extracted content include download links without an image preview. For multi-output captures, pass outputId to get_screenshot_result to retrieve a particular output.

Private download links expire within ten minutes and never outlive the capture's retention period. Retrieve the result again for a fresh link while the capture remains available. Existing public storage links keep their usual access rules.

Bulk captures, schedules, and history

capture_screenshots_bulk uses the bulk request fields, including urls, per-URL options, shared defaults, and optional webhook settings. It also accepts idempotencyKey.

create_schedule uses the schedule request fields, including name, url, schedule, timezone, and options. update_schedule requires the schedule's id plus only the fields to change. The other schedule actions take its id.

list_screenshots accepts page (starting at 0), size (1–100), query, status, source, and from/to date filters. Use UTC timestamps such as 2026-10-01T00:00:00Z; to is an exclusive boundary. Bulk and schedule lists accept limit (1–100, default 50). Schedule history also requires id.

Retries and troubleshooting

Reuse the same idempotencyKey and inputs when retrying a capture or bulk submission. Changing the inputs for the same key returns IDEMPOTENCY_CONFLICT. If a submission returns SUBMISSION_PENDING, inspect capture history before retrying. Schedule mutations do not automatically retry.

Problem	What to check
Organisation is missing during login	Ask an owner or admin to enable MCP for that organisation, and check that your account is a member
Connection stopped working	Sign in again; disabling MCP, revoking or regenerating its dedicated key, or removing your membership invalidates existing access
API-key authentication fails	Check that the key is valid, available to your client, and sent in exactly one supported header
A capture or schedule is missing	Check the selected organisation; API-key connections only see resources belonging to that key
Download link expired	Call `get_screenshot_result` again while the capture is still retained
Opening the server URL shows an error	The URL is an MCP endpoint for your client, not a webpage. It accepts POST requests; GET and DELETE return 405

Owners and admins can select Disable MCP on the API keys page to revoke the organisation's OAuth connections. After re-enabling MCP, members must authenticate again. Revoking or regenerating the dedicated MCP key also requires enabling MCP and reconnecting.

Agent plugins — install the local Allscreenshots plugin and screenshot skill
Screenshot API — capture options
Bulk screenshots — batch inputs and status
Scheduled screenshots — cron expressions, timezones, and delivery options

MCP Server