Expose Resource Availability Data Through the Workfront MCP Server

Summary

Our team uses Claude connected to the Workfront MCP server to answer resourcing questions in natural language. Planned Hours are fully and reliably queryable today. Remaining Available Hours — the metric the Resource Planner itself calculates (schedule capacity minus time off minus existing commitments) — is not exposed through any MCP tool, and cannot be reliably reconstructed from what is exposed. We're requesting this data be made queryable so a team's full capacity picture (Planned + Available) can be surfaced through natural-language requests, not only through the Resource Planner UI.

What Works Today

Planned Hours are cleanly queryable via the insights_find_workfront_data tool, using fields such as assignment.assignment_workRequired and task-level planned hours, grouped or filtered by user, project, or date range. This lets Claude answer questions like "how many planned hours does each person on this team have this month" accurately and immediately.

The Gap

• The Resource Planner's own Available Hours (AVL) value — schedule capacity minus time off minus hours already budgeted across all of a user's projects — is not exposed as a field through insights_search_fields or any other MCP tool we've found.
• The raw inputs needed to approximate it are also incomplete: user.user_workHoursPerDay and schedule.schedule_hasNonWorkDays are queryable, but time off is only exposed as a boolean flag (user.user_hasReservedTimes), not as actual date ranges or hours. There is no queryable list of a user's specific time-off periods or schedule exceptions.
• As a result, Claude cannot reliably reconstruct "remaining availability" even by combining multiple queries — any approximation would overstate availability for anyone with time off on the books, since those dates aren't visible to any tool.

What We're Requesting

• Preferred: expose the Resource Planner's calculated Available Hours (AVL) value itself as a queryable field — per user, role, or project, scoped by date range — mirroring what already displays in the Resource Planner UI.
• Minimum viable alternative: expose the underlying time-off / schedule exception data (specific dates and hours per user) as queryable fields, so Available Hours can be reliably approximated by combining it with the Planned Hours data that is already accessible.

Why This Matters

Capacity planning conversations need both halves of the picture — what's already committed, and what's actually left. Today, getting the Available Hours half requires manually opening the Resource Planner and checking user-by-user, project-by-project, which doesn't scale and can't be surfaced through natural-language tools like Claude. Closing this gap would let our team ask capacity questions the same way we already ask planned-hours questions — directly, without a manual UI detour.