The July 2026 customer office hours session was a live demonstration of the Fullcast Model Context Protocol (MCP) server — running territory, account, coverage, and commission work by typing what you want instead of navigating the user interface (UI). Use the section guide below to jump to the sections you wish to review.
Recording
Ashley Kim (Director of Customer Education and Engagement), Tyler Simons (Director of Product), and Bala Balabaskaran (Co-founder and Chief Technology Officer) hosted. The session runs about an hour, with questions taken throughout.
Note: The prompts demonstrated in this session, the skills worth building around them, and the recommended project instructions are written up separately.
Section guide
Each row links to that point in the recording.
Time | Section | Watch this if |
|---|---|---|
Introduction and MCP background | You want the two-year history, what changed in version 2, and which AI clients the MCP works with. | |
Setting up the MCP server | You have not connected yet. Covers the in-app toggle, the MCP URL, admin approval, and how role-based access control (RBAC) applies. | |
Analyzing unassigned accounts | You want to see how far a three-sentence prompt gets. The output identified the aggregate bookings potential sitting unassigned, the single field causing most of it, and a prioritized enrichment sequence. | |
Tracing account history with audit logs | You get asked why an account is where it is. The demo reconstructed a placement history and found that a rules rerun had overridden a manual move. | |
Analyzing corporate families and coverage | You manage large account families. Worth watching for the moment the analysis surfaced hierarchy problems nobody asked it to look for. | |
Moving accounts and managing coverage assignments | You want to see write actions before you try one. Covers a proposed account move, creating an assignment, ending coverage for a transfer, and the bulk options. | |
Territory and industry analysis | You are deciding where to add headcount. An open-ended prompt picked its own metrics and named an industry to focus on. | |
Commissions: deal explanation and auditing | You field questions about pay, or you audit credit before payroll. The longest and most detailed segment of the session. | |
Troubleshooting import and export jobs and audit logs | You own an integration. One question surfaced job failures nobody had gone looking for. | |
Getting started and first prompts | You want the hosts’ recommendations on where to begin and how to build trust with write actions. |
What was demonstrated
Short notes on each segment, focused on what came back rather than how to ask for it.
Background and setup
Version 1 of the MCP was read-only with a deliberately small surface area. The Fullcast Assistant was built on top of it, adding a conversational interface inside the app. Version 2, released about five weeks before the session, covers most read use cases across the plan-through-pay lifecycle plus a set of write operations, and works with any MCP-compatible client including Claude, ChatGPT, Gemini, and Cursor.
Setup is two steps: toggle the MCP on under Settings > Application Settings > AI Agents, then add the Fullcast MCP URL in your AI client and authenticate by logging in to Fullcast. Your admin may need to supply the URL. For the full procedure, refer to the MCP setup guide on the Fullcast support site.
One point from this segment is worth carrying into everything else: the MCP acts as you. If you cannot do something in the Fullcast UI, you cannot do it through the MCP.
Accounts and territories
Four analyses run back to back. The unassigned account review found that a large majority of unassigned accounts were missing one field, and turned that into a sequenced enrichment plan. The account history trace reconstructed a placement across several manual moves and a rules rerun, naming the rule and the account attribute that overrode the manual decision. The corporate family analysis flagged entities that did not roll up to the parent correctly, unprompted. The industry analysis chose its own metrics and recommended a segment to focus on, with a chart.
The write segment covers an account move proposed rather than committed, with the MCP reporting an uncommitted change already sitting on the account and asking before it committed; creating a coverage assignment with a future start date; and ending coverage for a transfer, where it recommended an end date that kept coverage continuous and then flagged that the vacated territory would have no account executive.
Commissions
Jump to 39:43.
The densest segment. Four workflows: explaining what a rep was paid on one deal down to the rate and attainment tier, ranking a rep’s top-earning deals and surfacing two with missing account identifiers, reviewing who receives credit on deals above a dollar threshold, and explaining a sales manager override calculation with attainment shown deal by deal.
Bala framed the underlying point directly: you pay for your data problems in the commissions environment, because that is where they finally show up.
Jobs and audit logs
Jump to 52:08.
Asking whether export jobs were working returned a set of failures with timestamps and error detail. The same segment covers querying the audit log for user activity, including when someone last signed in.
Getting started
Jump to 55:51.
The closing recommendations: start open-ended to learn the response patterns, confirm write actions in the Fullcast UI while you are building trust, get more specific as you learn what you want, then write it down as a skill and share it across the team. The specifics are covered in the two articles below.
Tip: If you are new to the MCP, work in that order: instructions first, then a few read-only prompts from the library, then skills once you know what you keep correcting.