Give Claude context on how you actually work.
Claude can read the files and apps you connect. Larridin Work Context adds the rest: the projects you are on, the people involved and what is blocked, across every app on your desktop. Private by default, governed by your org.
What should I focus on today?
Claude
You have four meetings today. Your inbox has 12 unread messages.
Reads: calendar, inbox.
Claude + Work Context
The Acme renewal. You have been in the pricing sheet all week and the invoice is still unsent. Priya pinged you about it twice. That is blocking the Q4 forecast.
Reads: calendar, inbox, and how you actually worked this week.
Same Claude. Same question. Different answer.
Trusted by AI-forward enterprises
How it works
Your agent sees how you actually work.
The desktop sensor observes how work happens across every app, not just the ones with an API: the projects you are on, the people you are working with, the things that are blocked. All of it becomes context your agent reads over MCP, with privacy controls that put you in control.
Activity
Priya Shah: “Any update on the invoice?” · 2 h ago
Priya Shah: “Finance needs it before Thursday.” · yesterday
Dan Ortiz updated the pricing sheet · Monday
Work Context
Your work context
![]()
![]()
All of it, available to your agent
Step 1
Install and sign in
IT pushes the desktop sensor through Jamf, Intune or Kandji, or you download it. Sign in with Okta, Entra or Google.
Step 2
Choose what it observes
Org policy sets the allowed and denied apps. You opt in or out inside that boundary, see every memory, and switch context off any time.
Step 3
Connect your agent
Add the Larridin connector in Claude, sign in once with your work account, and every work question is answered in context.
Set up Claude
Connect Larridin to Claude.
Larridin is a remote MCP connector. It works in Claude on the web, desktop and mobile, and in Claude Code.
Step 1
Add the connector
In Claude, open Settings, then Connectors, and add Larridin with the URL your admin shares. On Team and Enterprise plans an owner adds it for everyone.
Step 2
Sign in with your work account
Sign in with Okta, Entra or Google. Claude reads your own work context only, and asks before it adds anything.
Step 3
Ask Claude about your work
Ask "What should I focus on today?" or "Prep me for my 2pm." Claude answers from your projects, people and blockers.
Using a different agent? See every agent Work Context supports.
Work Context · Admin policy
With whom
Built for the enterprise from day one
You decide what is captured, what is shared, and with whom.
SSO, SCIM and granular privacy controls. Org policy sets the boundary, each employee chooses inside it, and admins never see an individual’s context.
Agents authenticate as registered OAuth clients, so a random MCP client cannot claim to be one of yours. Every agent on the team gets smarter, on your terms.
Enterprise ready
Give your agent the context it needs to be your chief of staff.
Request access and we will set up Work Context with your identity provider and MDM. Your people keep the agent they already use.