Claude connector

• A Claude account. On Pro and Max you add the connector yourself. On Claude Team or Enterprise an Owner adds it once for the organisation, and colleagues then enable it on their own account.
• A Friday4:30 login with an internal role: viewer, contributor, incident manager, admin or owner. External advisors and stakeholders cannot connect.
• An active Friday4:30 subscription on your organisation.

Sign in to Friday4:30 and open Settings, then API and connections. The Connect to Claude card shows your connector URL. Copy it.

In Claude

1. Open your connector settings, which is Settings, then Connectors, or Customize, then Connectors depending on your plan.
2. Choose Add custom connector and paste the URL.
3. Claude sends you to Friday4:30 to sign in and approve the connection. Once you approve, it appears in your connector list.

In Claude Code

Run the command shown on the same card, which is claude mcp add --transport http friday430 <your connector URL>.

Claude acts as you. It holds exactly the permissions your own login has, and every request goes through the same checks the app does, so a call can legitimately come back refused.

• Read incidents, tasks, awareness notices, suppliers and products.
• Read your readiness score and your First Light.
• Comment on an incident, create and update tasks, raise an awareness notice.
• Raise and update incidents, if your role allows it.

A viewer gets read access only. A contributor can comment and work tasks but cannot raise an incident. Deleting anything needs admin or owner, exactly as it does in the dashboard. Features your plan does not include stay unavailable.

• See any organisation other than your own.
• Do anything your own login cannot do.
• Create API keys or connections, which can only be managed while signed in.
• Reach the Friday4:30 staff admin console, which is blocked for every connection.

• "What incidents are open in Friday4:30?"
• "Summarise the listeria incident and what is still outstanding."
• "Add a task to chase the lab result, due tomorrow."
• "What is our readiness score, and what is dragging it down?"
• "Anything in today's First Light I should act on?"

Open Settings, then API and connections in Friday4:30 and choose Disconnect on the connection you want to end. Access stops immediately. You can connect again whenever you like. Removing the connector in Claude also ends it.

Nothing is sent anywhere until you connect, and only what a tool call asks for is read. When Claude calls a tool, the data it returns is processed by Anthropic under their terms as part of your conversation. Our own handling is covered in our Privacy Policy.

Something not working, or a tool doing the wrong thing? Email info@friday430.io and tell us what you asked Claude to do and what happened.