[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# ShootProof MCP server: Let your AI agent run your ShootProof studio admin.

> ShootProof has no MCP server and no ChatGPT or Claude app. Its OAuth API is free with an account, but a client ID comes only by emailing support with your app details (developer docs, checked 8 Nov 2026). Cotlet runs 10 ShootProof tools hosted, over MCP for agents and REST for scripts, in your own ShootProof login.

Your AI agent books sessions with a contract and invoice, creates and delivers galleries, tells you about new orders and lists galleries about to expire. Sign in to ShootProof once in your own Cloud Browser. No client ID, no OAuth app.

- Free 7-day trial, no card
- Unofficial, not affiliated with ShootProof
- Page: https://cotlet.dev/integrations/shootproof-api-mcp-server

## What can your AI agent do in ShootProof?

- Send contracts for new sessions
- Send invoices with a retainer
- Create and deliver client galleries
- Check new print orders
- Find galleries about to expire
- See who still owes a payment

## Does ShootProof have an MCP server or an API?

- The ShootProof API uses OAuth 2.0 with refresh tokens, so you build and host an app.
- It covers contacts, contracts, events, invoices, orders and price sheets for your developer.
- ShootProof has no connector in the ChatGPT apps directory or in Claude.

| What you need | ShootProof API | By hand | Cotlet |
|---|---|---|---|
| Galleries and orders | With a client ID | Yes, one by one | Yes |
| Send a contract or invoice | With a client ID | Yes, one by one | Yes, after your OK |
| Share a gallery | With a client ID | Yes | Yes, after your OK |
| Ask in ChatGPT or Claude | No | No | Yes |
| Developer needed | Yes | No | No |

Checked 8 Nov 2026. Sources: [ShootProof for Developers: Authorization](https://developer.shootproof.com/guide/authorization/), [ShootProof for Developers](https://developer.shootproof.com/), [ShootProof integrated partners](https://www.shootproof.com/integrated-partners/), [ShootProof plans](https://www.shootproof.com/plans/)

## How does the ShootProof MCP server work?

1. **Sign in to ShootProof.** Once, in a browser we host for you.
2. **Connect your AI agent.** One address in its settings.
3. **Hand it the busywork.** It drafts the work, you OK what customers get.

We never keep your ShootProof password, and no gallery, contract or invoice reaches a client until you approve it.

## How to connect ShootProof to your AI agent

1. **Sign in to ShootProof in a Cloud Browser.** Create a Cotlet account, open ShootProof in its Cloud Browser, sign in to your studio on studio.shootproof.com and press Enable for agents.
2. **Add the Cotlet address.** Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
3. **Let the agent in.** Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.

ShootProof shares the address `https://cotlet.dev/mcp/v1` with every other app you enable, so one connector covers them all. Turned ShootProof on after connecting? Refresh the connector and the 10 tools appear.

Claude:

```
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

ChatGPT:

```
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
```

Cursor:

```
// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}
```

Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

n8n:

```
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: shootproof_read
```

Make, Zapier:

```
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: shootproof_write
```

## All 10 ShootProof MCP tools

### Galleries and orders

New galleries start private. Sharing sets the gallery live and emails the client, after your OK. Orders are read only.

- **List galleries** (`list_galleries`, read): Client galleries with status, visits and expiry.
- **Get gallery** (`get_gallery`, read): One gallery with albums, settings and favorites.
- **Create gallery** (`create_gallery`, write): Creates a private gallery for a client.
- **Share gallery** (`share_gallery`, write, asks first): Makes a gallery public and emails the link to the client.
- **List orders** (`list_orders`, read): Print and download orders by status or gallery.

### Contacts, contracts and invoices

Search contacts before adding one. Contracts come from your templates; contracts and invoices go out only after your OK.

- **List contacts** (`list_contacts`, read): Contacts, searchable by name or email.
- **Create contact** (`create_contact`, write): Adds a contact.
- **Send contract** (`send_contract`, write, asks first): Sends a contract from a template for signature.
- **List invoices** (`list_invoices`, read): Invoices by status, with amounts due.
- **Send invoice** (`send_invoice`, write, asks first): Creates and emails an invoice to a contact.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/shootproof-api-mcp-server#tools

## Who can see my ShootProof session, and how do I revoke it?

- **What we store.** Your signed-in ShootProof profile, AES-256-GCM encrypted, in Finland. No password.
- **What your agent gets.** The 10 ShootProof tools, never the session cookie.
- **What the session sees.** What your studio sees: galleries, orders, contacts, contracts, invoices.
- **What no tool touches.** Uploads, deletes, payouts, price sheet edits, lab fulfillment.
- **If ShootProof signs you out.** You sign in again yourself, in the same Cloud Browser.
- **How to cut access.** Disable for agents, reset the browser, or change your ShootProof password.

Cotlet never types your password: you sign in yourself, and the agent only uses the session. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)).

## What happens when ShootProof changes?

- **12 h** between tests of the ShootProof reads
- **24 h** between tests of sends a customer would notice
- **$0** for a call to a ShootProof tool paused for repair

When ShootProof moves a button in the gallery settings or renames a contract status, we fix the tool and your agent calls it the same way. [status.cotlet.dev](https://status.cotlet.dev) checks the site, console and API every 3 minutes.

## Approvals, undo and mistakes

1. **Finds or adds the contact.** So a returning client is not duplicated.
2. **Fills your contract template.** With the session date.
3. **Builds the invoice.** With the retainer and the balance.
4. **Waits, then sends.** Both show up in your Cotlet console first.

| Action | Undo |
|---|---|
| Create a gallery | Yes, delete it in ShootProof |
| Create a contact | Yes, edit or delete it |
| Share a gallery | Make it private again; the email stays sent |
| Send a contract or invoice | Void it in ShootProof; the email stays sent |

3 of 10 tools ask first: share_gallery, send_contract, send_invoice. A new private gallery or a contact reach no customer, so they run at once. You can turn the wait off per tool once you trust a routine.

MCP call:

```
{
  "name": "send_contract",
  "arguments": {
    "contact_id": "7730502",
    "template": "Portrait session",
    "session_date": "2026-12-06"
  }
}
```

REST:

```
curl -X POST https://cotlet.dev/api/v1/shootproof/contacts/7730502/contracts \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"template":"Portrait session","session_date":"2026-12-06"}'
```

Response:

```
{
  "contract_id": "K-55120",
  "contact": "Sam Rivera",
  "template": "Portrait session",
  "status": "Sent"
}
```

A cron job or n8n flow can call the same tools over REST at `/api/v1/shootproof` with the same key and price, in JSON. Failed calls are free. Each tool row above shows its REST path.

## How much does the ShootProof MCP server cost?

**About $15 a month** for a photographer with about 10 sessions, 2,600 credits. Your ShootProof plan stays as it is.

| Job | Calls | Credits |
|---|---|---|
| Session booked: contact, contract, invoice | 4 × 10 | 400 |
| Gallery created and shared | 2 × 10 | 200 |
| New orders checked | 1 × 30 | 300 |
| Expiring galleries, weekly | 4 × 4 | 160 |
| Unpaid invoices, weekly | 1 × 4 | 40 |
| Cloud Browser, 30 days |  | 1,500 |
| Total |  | 2,600 |

- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Works on your current ShootProof plan

ShootProof publishes no usage counts, so the month is our example. Dollars at the $29 pack rate.

## ShootProof MCP server on GitHub, Zapier or hosted: which to use

| Option | What it does | Where it stops |
|---|---|---|
| ShootProof API | Contacts, contracts, events, invoices and orders for your own developer. | Client ID by email to support; you build and host an OAuth app. |
| [ShootProof integrated partners](https://www.shootproof.com/integrated-partners/) | Ready connections to other studio tools. | Each partner connects one tool for one job. |
| By hand | Every screen of ShootProof. | Your editing time. |

If your developer already has a ShootProof client ID, building on the API is cheaper for simple reads. To deliver galleries and send contracts by asking in ChatGPT or Claude, Cotlet works in the ShootProof account you already have.

### ShootProof MCP setup on GitHub and PyPI

Prefer code? Our public repo has a ready ShootProof MCP config for Claude Code, ChatGPT and Cursor, an agent skill and a small command-line tool. Add your Cotlet API key and your agent works in your own ShootProof account.

- MCP config for Claude Code, Cursor and Codex
- Agent skill and Cursor rules for ShootProof
- Clone it and run, Python standard library only
- Elastic License 2.0, free in your own business
- Code: https://github.com/cotlet-connect/shootproof-mcp

## Who runs Cotlet

Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), in business since 2019, led by its founders Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the ShootProof tools go to contact@cotlet.dev.

## ShootProof MCP server: questions

### How do I get access?

Sign up free at https://cotlet.dev, open ShootProof under Integrations in the console and sign in to ShootProof in its Cloud Browser. The trial starts with your first app and asks for no card.

### How do I connect ShootProof to ChatGPT or Claude?

Sign up at cotlet.dev, log in to ShootProof once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your ShootProof account through Cotlet, in their phone apps too.

### What can ChatGPT do in ShootProof?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in ShootProof: book a session with contract and invoice; create and deliver client galleries; check new print orders. You ask in plain words, and anything that reaches other people waits for your OK first.

### Is there an official ChatGPT or Claude app for ShootProof?

No. ShootProof has no ChatGPT or Claude connector of its own and ShootProof has no official MCP server (checked 8 Nov 2026). Cotlet is an independent one that works in ChatGPT, Claude, Cursor and any MCP client, on your signed-in account.

### Can ChatGPT create galleries in ShootProof?

Yes, with Cotlet. ChatGPT creates the gallery with your price sheet and expiry and sends it to the client after your OK.

### Can ChatGPT send contracts in ShootProof?

Yes, with Cotlet. ChatGPT fills your contract template for the session and sends it to the client to sign, after your OK.

### Can ChatGPT check orders in ShootProof?

Yes, with Cotlet. Ask what came in since yesterday and ChatGPT lists new print and download orders with their totals.

### Do I need a ShootProof client ID to use Cotlet?

No. Cotlet works through your own ShootProof sign-in, so you skip the support request and the OAuth app. It can do what your studio account can do.

### Can it upload photos?

No. Upload from Lightroom or the ShootProof uploader as you do today. The agent creates, shares and reads galleries that are already there.

### Is the MCP server different from the REST API?

Only in how it is called. Both carry the same 10 tools, inputs, answers, API key and price. Agents use MCP; scripts and HTTP steps use REST.

### Is Cotlet affiliated with ShootProof?

No. Cotlet is independent and not affiliated with ShootProof.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
