Connect an agent.

Let an AI agent or your own script keep your listings up to date. It works as you, on your listings only, and it cannot publish anything: every offer still goes to a person who checks it against your site.

Your connected agents

With an MCP client

Claude Code, Claude Desktop, Cursor and other MCP clients. Add the server, then approve the client in your browser. There is no token or key to paste.

Claude Code

claude mcp add --transport http blackfriday-tools https://blackfriday.tools/mcp

Other MCP clients (JSON config)

{
  "mcpServers": {
    "blackfriday-tools": {
      "type": "http",
      "url": "https://blackfriday.tools/mcp"
    }
  }
}

1.Add the server. The first request it makes is turned away with a pointer to our sign-in; that is expected.
2.Your browser opens. Sign in with the account that owns your listings.
3.Check the client's name, where it sends you back, and what it asks to do — then choose Allow, or Deny.

With the REST API

For scripts and your own tools: the same operations as the MCP server, versioned under /api/v1. The OpenAPI document describes every endpoint, field and error.

API base: https://blackfriday.tools/api/v1
OpenAPI: https://blackfriday.tools/api/v1/openapi.json
Authorization server: https://blackfriday.tools/.well-known/oauth-authorization-server
Resource (RFC 8707): https://blackfriday.tools/mcp

1.Register your client once (RFC 7591): a public client with your redirect URI, at https://blackfriday.tools/api/auth/oauth2/register. No secret is issued.
2.Send yourself through the authorization endpoint with PKCE (S256) and only the scopes the script needs. You approve it in the browser.
3.Exchange the code for a token, naming the resource. A token without it is not issued.
4.Call the API with the access token as a Bearer header. It lasts 15 minutes; ask for offline_access to get a refresh token.

Exchange the code (step 3)

curl -X POST https://blackfriday.tools/api/auth/oauth2/token \
  -d grant_type=authorization_code \
  -d code="$CODE" \
  -d redirect_uri="$REDIRECT_URI" \
  -d client_id="$CLIENT_ID" \
  -d code_verifier="$CODE_VERIFIER" \
  -d resource=https://blackfriday.tools/mcp

List your listings (step 4)

curl -H "Authorization: Bearer $ACCESS_TOKEN" https://blackfriday.tools/api/v1/listings

Grant only what it needs

The client names its scopes when it asks, and the approval page lists them. An agent that only reports on your listings needs nothing but read.

listings:read: Read your listings, including drafts and their discount codes.
listings:write: Create, edit and delete your drafts, and claim a listing we drafted for you.
listings:submit: Send a finished draft to review. A person checks it before anything is published.
offline_access: Stay connected past the 15-minute access token, until you sign out or disconnect it.

What an agent can and cannot do

Create drafts, edit them, and delete them. A listing that came back with changes requested is editable again.
Send a finished draft to review. While it is in review it is locked; once it is live, changes go through us and are verified again.
Claim a listing we drafted for you, with the token from your claim link.
Discount codes come from you. An agent must never invent or guess one.
It never sees another founder's listings, and it cannot publish, approve, or upload images — upload those on the listing's page.

Taking access back

Disconnect an agent above and it loses access on its next request. Signing out of the browser session you approved it from ends its access too. Every call is checked, so nothing lingers until a token runs out.