photoproof developers: API and MCP server
Two ways to build with photoproof.io. A public read-only API that needs no key, and an MCP server that lets an AI app work with a photographer's galleries and client picks after they sign in and allow it.
Public API
REST, JSON, OpenAPI 3.1. Plans, pages, search, health. No key.
MCP server
Streamable HTTP with OAuth. Galleries, client picks, comments, deliveries.
Discovery files
llms.txt, server card, Agent Skills, ARD, OAuth metadata.
Open source and CLI
Connector configs on GitHub. CLI and typed client on npm.
Public read-only API
Base URL https://photoproof.io. No API key, no sign-up. Responses are JSON with CORS open to every origin, so you can call them from a browser too. They return public data only, never personal data.
Full description: /openapi.json (OpenAPI 3.1, typed parameters and responses). API index: /api/v1.
GET /api/v1/plans Plans and prices in euro, VAT included. Optional ?id= or ?kind= filter.
GET /api/v1/pages Every public page with title, description, section and its Markdown URL. Optional ?section=.
GET /api/v1/search?q= Keyword search over guides, comparisons, case studies and product pages. ?limit= 1 to 20.
GET /api/health Live check of database, storage and watermark service. 200 when healthy, 503 when not. Optional ?check=.
Examples
curl -s https://photoproof.io/api/v1/plans curl -s "https://photoproof.io/api/v1/plans?id=pro" curl -s "https://photoproof.io/api/v1/pages?section=guides" curl -s "https://photoproof.io/api/v1/search?q=lightroom%20selection&limit=3" curl -s https://photoproof.io/api/health Errors
Errors use one JSON shape with a machine-readable code:
{ "error": "bad_request", "message": "Pass a search query of at least 2 characters in ?q=.", "docs": "https://photoproof.io/openapi.json" } Testing
There's no separate sandbox or test mode. Here is how to test safely against the real service:
- Public API: every endpoint is read-only and needs no key, so you can call it as much as you like while you build. Nothing you send changes any data.
- MCP server: create a free account (2 GB, no card) and use it as your test account. The connector only ever sees the signed-in photographer's own galleries.
- Read-only access: request only the
galleries:readscope and the connection can't change anything.create_galleryis the only tool that writes, and it only adds a new, empty gallery. - Client view: the demo page shows what a client sees when they open a gallery.
photoproof MCP server
The AI connector works in Claude, ChatGPT, Cursor and any MCP client that supports remote servers with OAuth. It works on every plan, Free included.
https://photoproof.io/mcp - Transport: Streamable HTTP.
- Auth: OAuth 2.1 authorization code flow with PKCE (S256). Clients register themselves with dynamic client registration at
/oauth/register. There are no API keys. Details in auth.md. - Scopes:
galleries:read,galleries:write. - Unauthenticated calls get 401 with
WWW-Authenticatepointing to the protected resource metadata, so MCP clients start sign-in on their own. - Limits: 120 requests an hour and 20 new galleries a day per photographer.
Tools
get_account Your photoproof.io plan, storage used and limit, renewal date and gallery counts. (read-only)
list_galleries Your galleries, newest first: title, client link, photo count, expiry, settings and how many clients opened or confirmed. (read-only)
search_galleries Find your galleries whose title contains the given text. (read-only)
get_gallery One gallery: settings (watermark, password on/off, download lock), expiry, size, client visits and delivery links count. (read-only)
get_selections What each client picked in a gallery (photo codes for a Lightroom filename filter), rejects, client comments and whether they confirmed. (read-only)
recent_activity Galleries your clients opened and selections they confirmed in the last N days. (read-only)
list_deliveries Your final-photo delivery links: title, link, files, tracked downloads (Pro/Studio) and expiry. (read-only)
create_gallery Create a new, empty proofing gallery. Returns the client link and the dashboard link where the photographer uploads photos. (writes; needs galleries:write)
Connect
- Claude: Customize → Connectors → Add custom connector, then paste the server URL.
- ChatGPT: add a custom MCP server with the server URL and choose OAuth.
- Cursor: add this to
~/.cursor/mcp.json, then click Connect:
{
"mcpServers": {
"photoproof": { "url": "https://photoproof.io/mcp" }
}
} Step-by-step guide for each app: Set up the AI connector.
Discovery files
Machine-readable files for agents and crawlers. Any public page also has a Markdown version: add .md to its URL or send Accept: text/markdown.
Site index for language models
OpenAPI 3.1 description of the public API
API catalog (RFC 9727)
MCP server card: tools, transport, auth
Agent Skills index (SKILL.md files)
Agentic Resource Discovery catalog
OAuth authorization server metadata (RFC 8414)
Protected resource metadata for /mcp (RFC 9728)
How agents authenticate, step by step
This page as Markdown
Open source and CLI
Connector configs, the MCP Registry entry and install notes are on GitHub: github.com/mikemorakis/photoproof-mcp.
npm package: photoproof
A small CLI that writes the MCP config for Claude Desktop, Cursor, VS Code or Claude Code, plus a typed JavaScript client for the public API. MIT licensed, no dependencies, Node 18+. Source in the npm folder on GitHub.
npx photoproof setup # MCP config for every supported app
npx photoproof setup cursor --write # add photoproof to ~/.cursor/mcp.json
npx photoproof plans # plans and prices from the public API npm install photoproof
import { PhotoproofClient } from "photoproof";
const pp = new PhotoproofClient();
const { plans } = await pp.getPlans({ kind: "plan" }); Questions or ideas for the API? support@photoproof.io