Add FullStory API Integration to MCP Server - Session Data and Events Access

Problem

The current FullStory MCP server at https://mcp.pipedream.com/app/fullstory shows "no tools available" and appears non-functional. This prevents AI assistants from accessing FullStory session data for analysis and workflow optimization.

Requested MCP Tools

Please implement these core FullStory API integrations as MCP tools:

1. List User Sessions

• Tool name: fullstory_list_sessions
• API endpoint: GET /sessions/v2?email={email}&limit={limit}
• Parameters: email (required), limit (optional, default 20)
• Returns: Array of session objects with userId, sessionId, createdTime, fsUrl

2. Get Session Events (Detailed Timeline)

• Tool name: fullstory_get_session_events
• API endpoint: GET /v2/sessions/{session_id}/events
• Parameters: session_id (format: userId:sessionId URL-encoded)
• Returns: Detailed event stream with timestamps, event types, element selectors

3. Get Session Context (AI-Optimized)

• Tool name: fullstory_get_session_context
• API endpoint: POST /v2/sessions/{session_id}/context
• Parameters: session_id, event_limit (optional), exclude_types (optional)
• Returns: Clean, AI-friendly event descriptions with timestamps

4. Generate Session Summary

• Tool name: fullstory_generate_summary
• API endpoint: GET /v2/sessions/{session_id}/summary
• Parameters: session_id, config_profile (optional)
• Returns: AI-generated session summary

Authentication

• Uses FullStory API key with Basic authentication
• Requires Admin/Architect permissions for data access
• Auto-routes to EU/NA endpoints based on account region

Use Cases

• AI Session Analysis: Extract user interaction patterns for UI optimization
• Business Intelligence: Generate insights from user session behavior
• Customer Support: Quickly understand user journey issues
• A/B Testing: Analyze session data for conversion optimization

Sample Implementation

// Example tool usage const sessions = await fullstory_list_sessions({ email: "user@domain.com", limit: 5 });

const events = await fullstory_get_session_events({ session_id: sessions[0].userId + ":" + sessions[0].sessionId });

const context = await fullstory_get_session_context({ session_id: sessions[0].userId + ":" + sessions[0].sessionId, event_limit: 100 });

Expected Output Format

Tools should return structured JSON that AI assistants can easily process for:

• Timeline generation (timestamp | event_type | description | element)
• Session summaries for business analysis
• User journey mapping and bottleneck identification

Configuration Requirements

• FullStory API key (Basic auth header)
• Account region detection (automatic routing)
• Rate limiting compliance
• Error handling for quota limits and permissions

This would enable powerful AI-driven analysis of user sessions for UX optimization and business intelligence, making FullStory data accessible through natural language queries to AI assistants.

---

Priority: High - Many users need AI access to FullStory session data for workflow analysis and optimization.