New Idea
Expose AI Confidence Score in Staircase MCP Expansion Analyst Response
Current Behavior
- When querying expansion opportunities via the Staircase MCP, the expansion analyst returns a flat list of opportunity name strings with no nested structure. There is no additional metadata — such as AI confidence score, opportunity type, account context, or signal source — attached to each opportunity in the response payload.
Expected Behavior
- The MCP response for expansion opportunities should return a structured object per opportunity that includes, at minimum, the AI confidence score that is already visible in the Expansion Analyst UI. Ideally, each opportunity would be returned as a nested object with fields such as:
{
"opportunity_name": "string",
"ai_confidence": "High / Medium / Low",
"account_name": "string",
"signal_source": "string", // e.g. call transcript, email, sentiment
"identified_date": "date"
}Business Impact
- My customer is actively using Claude + Staircase MCP for AI-powered CS workflows, including executive presentations and account prioritization. Without the AI confidence score exposed via MCP, users cannot programmatically filter or prioritize expansion opportunities by quality — limiting the actionability of the data returned and requiring manual cross-referencing with the Staircase UI. This gap is particularly impactful for scaled/SMB motions where automation is key.