MCP Server

screenshotbase ships a hosted Model Context Protocol (MCP) server, so AI agents and assistants can call the API as native tools — no SDK or glue code required.

https://api.screenshotbase.com/mcp

The endpoint speaks the streamable HTTP transport. Listing the available tools works without authentication; executing a tool requires your API key, sent as the apikey header. You can get a free API key here.

Connect

Using Claude Code:

claude mcp add --transport http screenshotbase https://api.screenshotbase.com/mcp --header "apikey: YOUR_API_KEY"

Or add the server to any MCP-capable client (Claude Desktop, Cursor, VS Code, ...):

{
  "mcpServers": {
    "screenshotbase": {
      "url": "https://api.screenshotbase.com/mcp",
      "headers": { "apikey": "YOUR_API_KEY" }
    }
  }
}

Available tools

The tools are generated from the same OpenAPI specification that describes the REST API, so they always match the documented endpoints, parameters and responses.

Quotas and errors

Tool calls are metered exactly like REST requests: they consume your plan quota and return the same status codes and error responses (401, 422, 429, ...). If a call fails, the tool result contains the API's error message including hints on how to proceed.