Skip to main content

Workforce MCP

In addition to the standard Fullstory MCP tools, the Workforce MCP server for Fullstory Workforce customers includes six tools for analyzing your workflows: the workflow instances your teams work on, the milestones each one reached, who worked on it, and how much active time it took across your apps.

Ask questions like:

  • "What's the average time from Opened to Resolved for tickets last week?"
  • "What happened in ticket 1234, and where did people get stuck?"
  • "Which cases had the most active time, and which apps was that time spent in?"
Don't connect both servers

Connect /mcp/workforce instead of /mcp/fullstory, not alongside it. The Workforce server already includes every standard tool, so connecting both gives your AI client two copies of each one. The duplicates take up room in the client's context and leave it choosing between two identical tools on every call.

Prerequisites​

  • Fullstory Workforce is enabled for your org. See Workforce Overview.
  • StoryAI and the Model Context Protocol (MCP) toggle are on for your org, the same as for the standard server. See the note below.
  • At least one workflow identifier is configured. The workforce tools find workflows through workflow identifiers. Without one, they return no workflows. See Workflow Intelligence: Workflow Identifiers.
StoryAI features must be enabled

Fullstory MCP requires StoryAI features to be enabled for your org. If your org has opted out of StoryAI, your MCP client will appear to connect successfully (OAuth completes, the server shows as "connected") but no tools will be available.

An account Admin can verify or change this at Settings > StoryAI Features in Fullstory. If you don't see that page, you don't have the role needed to change it. Ask an Admin in your org.

See FAQ & Troubleshooting if your client is connected but no tools appear.

Connect​

Use the same setup as the standard server, with /mcp/workforce at the end of the URL instead of /mcp/fullstory. Authentication works the same way: OAuth by default, or an API key passed as a Bearer token. See Authentication for both.

Add this block to your client's MCP configuration, adjusting the outer keys if your client uses a different schema (for example, "servers" instead of "mcpServers"):

{
"mcpServers": {
"fullstory-workforce": {
"type": "http",
"url": "https://api.fullstory.com/mcp/workforce"
}
}
}

The client setup guides show where each client keeps its configuration. Use the Workforce URL in place of the URL in those examples.

Claude Desktop users: add the Workforce URL as a custom connector. The Fullstory listing in the Claude connector directory is the standard server and doesn't include the workforce tools.

Regional URLs​

If your client reports that the protected resource does not match the expected URL, use the URL for your data center:

  • EU (app.eu1.fullstory.com): https://api.eu1.fullstory.com/mcp/workforce
  • US (app.fullstory.com): https://api.na1.fullstory.com/mcp/workforce

See the FAQ for details.

Workforce tools​

In addition to the Fullstory analytics tools, the Workforce MCP server includes the six tools below for analyzing your workflows.

A workflow is identified by a property on your pages, such as a ticket or case number. Each value of that property is one workflow instance, for example one ticket. Defined events mark the milestones an instance passes through, such as Opened or Resolved.

The tools build on each other. Your AI client usually calls discover_context first, lists instances, then fetches details for the ones it needs:

ToolDescription
discover_contextList the workflow identifiers and apps configured for your org. Call this first: the other tools take the property names, types, and app IDs it returns.
list_defined_eventsList your org's defined events, each with its ID, name, and description. Use it to turn milestone IDs from the other tools into names, or to look up a milestone's ID by name.
query_workflow_instancesList the instance IDs for a workflow within a time range. Defaults to the last 30 days. Optionally restrict the list to instances that reached one or more milestones. Returns IDs only; pass them to query_workflow_events for details.
query_workflow_eventsGet details for a set of instances: each milestone with its timestamp, cycle time from first to last milestone, the people involved, and related events from other apps. Covers each instance's full lifecycle, so it takes no time range. Accepts at most 100 instance IDs per call; sample or batch larger sets.
compute_workflow_instanceGet one instance's timeline for each person who worked on it: events in order, pages, apps, friction signals such as rage and dead clicks, active time, and any point where they switched to a different instance and back. Use it for questions about a single ticket or case.
get_aggregate_workflow_metricsGet total active, focus, and visible time and the number of distinct users for each instance, per app. Reads pre-aggregated cross-app time, so it takes no time range; the result says how far back the stored data goes. Returns permission-denied if cross-app active time isn't enabled for your org.

Bound to milestones​

compute_workflow_instance and get_aggregate_workflow_metrics accept optional start_event_id and end_event_id parameters, each a defined-event ID from list_defined_events. Use them to limit the analysis to a milestone range, such as from Opened to Resolved. Each bound is independent. Activity before the start milestone or after the end milestone is excluded, and anything where a requested milestone never happened is left out of the result. Without them, get_aggregate_workflow_metrics counts all stored activity, so in-progress and completed instances are counted the same way.

Analytics, session, and StoryAI tools​

Everything else on the Workforce MCP server is the same as the standard server: analytics (segments, metrics, funnels, journeys, dashboards), sessions, agentic session review, and StoryAI Opportunities. See the Tools Reference for those tools.

Server API​

There is no separate Server API for Workforce. Workforce orgs use the existing Server API.