Calotype

Calotype for AI agents

Give your agent one tool, screenshot, that looks at any public web page from Calotype's browser. It is a remote MCP server: nothing to install, and nothing running inside your network.

1. Get a free key

100 screenshots a month, with no email, no name and no account. Use the button, or let your agent make its own:

curl -s -X POST https://calotype.dev/v1/keys

The answer's key field starts with cal_. It is shown once and cannot be shown again. Each address can make a few keys an hour.

Your key. This is the only time it is shown. Calotype keeps only a hash of it, so copy it now.

Keep the key out of shared files and chats. The examples below read it from an environment variable or a prompt where the client allows that.

2. Add the server: Claude Code

claude mcp add --transport http calotype https://calotype.dev/mcp \
  --header "Authorization: Bearer $CALOTYPE_KEY"

Add --scope user to use it in every project.

Cursor

In ~/.cursor/mcp.json, or .cursor/mcp.json in a project. Cursor fills ${env:CALOTYPE_KEY} from your environment:

{
  "mcpServers": {
    "calotype": {
      "url": "https://calotype.dev/mcp",
      "headers": {"Authorization": "Bearer ${env:CALOTYPE_KEY}"}
    }
  }
}

VS Code

In .vscode/mcp.json. VS Code asks for the key once and stores it for you:

{
  "inputs": [
    {"type": "promptString", "id": "calotype-key", "description": "Calotype API key", "password": true}
  ],
  "servers": {
    "calotype": {
      "type": "http",
      "url": "https://calotype.dev/mcp",
      "headers": {"Authorization": "Bearer ${input:calotype-key}"}
    }
  }
}

Codex

In ~/.codex/config.toml. Codex sends the variable's value as the bearer token:

[mcp_servers.calotype]
url = "https://calotype.dev/mcp"
bearer_token_env_var = "CALOTYPE_KEY"

n8n

In an AI Agent workflow, add the MCP Client Tool to the agent's tools. It needs n8n 1.104.0 or later, which added the streamable HTTP transport. Set:

n8n keeps the key in its encrypted credential store, not in the workflow.

Other clients

Any client that takes a server address and a custom header works. It needs three things:

Sign-in by OAuth is not offered yet, so clients that only support OAuth cannot connect.

3. Check it works

Ask your agent:

Take a dark-mode screenshot of https://calotype.dev/pricing and tell me the Starter price.

The price is on the rendered page, so a right answer means the agent saw it. That first screenshot counts as one of your 100.

What the tool does

The full reference, including the HTTP API, is in the docs. Plans and prices are on Pricing. Questions go to skewbald@agentmail.to, which Skewbald, the AI agent that runs Calotype, reads and answers.