Skip to main content
Solved

Time off calendar access through MCP

  • Nov 10, 2026 9:44 PM UTC
  • 2 replies
  • 104 views
  • Translate All

One of our managers (and SCRUM Master) is trying to do capacity planning for the whole engineering team, and many of these people don’t report to her. She’s got permissions to view all time off in the time off calendar by navigating to Time > People’s Time Off, but is hitting a roadblock with Claude, where it says she doesn’t have permission to view time off for non direct reports.  She can get the “who’s out today” data though, which is managed under the same permissions section. 

Has anyone figured something like this out for company wide time off data? Perhaps the MCP doesn't access that time off calendar in the same way it accesses other data?

As an admin, the MCP seems to go through approved time off requests (which i have global admin access for) as opposed to just viewing the time off calendar, so I think this is where it’s stuck for her. I don’t want to give access to view and edit all requests though as it’s not really the right things to do. 

 

Is there a bobber who can confirm my time-off calendar vs. requests suspicion above? And can i change that?

Best answer by Jack Amerena

Hey Amanda - we pull company-wide time off through the API rather than the MCP, and it gets around this exact problem.

Here’s how we do it:

  • A dedicated service user that can view time off and nothing else. It has no rights to create, edit or approve requests, so nobody gets more access than they need.

  • One call to who’s out: GET /timeoff/whosout?from=...&to=.... One request returns everyone’s leave for the whole range, with no paging, and it handles months at a time.

  • The results go somewhere the team can see them, like a spreadsheet or a small script, so the capacity view doesn’t depend on any one person’s permissions in Bob.

A few settings we’ve found useful:

  • Private leave stays out unless you add includePrivate=true. For capacity planning we leave it out.

  • includeWorkingRequests=false drops things like working from home, so you only see people who are actually unavailable.

  • Hourly leave only shows up if you add includeHourly=true.

The one trade-off is that someone has to set it up and look after the service user’s token. Since then it’s been the cleanest way we’ve found to get a whole-team view without handing out request permissions.

The code, of course, is all written by Claude! Hope that helps!

View original

2 replies

Hey Amanda - we pull company-wide time off through the API rather than the MCP, and it gets around this exact problem.

Here’s how we do it:

  • A dedicated service user that can view time off and nothing else. It has no rights to create, edit or approve requests, so nobody gets more access than they need.

  • One call to who’s out: GET /timeoff/whosout?from=...&to=.... One request returns everyone’s leave for the whole range, with no paging, and it handles months at a time.

  • The results go somewhere the team can see them, like a spreadsheet or a small script, so the capacity view doesn’t depend on any one person’s permissions in Bob.

A few settings we’ve found useful:

  • Private leave stays out unless you add includePrivate=true. For capacity planning we leave it out.

  • includeWorkingRequests=false drops things like working from home, so you only see people who are actually unavailable.

  • Hourly leave only shows up if you add includeHourly=true.

The one trade-off is that someone has to set it up and look after the service user’s token. Since then it’s been the cleanest way we’ve found to get a whole-team view without handing out request permissions.

The code, of course, is all written by Claude! Hope that helps!

Translate

Jack, this is so helpful thank you so much! we’ve moved forward in this way, and are building it out now. Really appreciate your in depth answer here!!

Translate