MCP SERVER IMPLEMENTATION: ANALYTICS CONNECTOR

ARCHITECTURE
• Transport: stdio + optional HTTP
• SDK: TypeScript SDK
• Data source: Analytics platform API (env vars)

TOOL DEFINITIONS (3 tools)

Tool 1: query_events
Inputs: start_date (ISO8601), end_date, event_name, properties (object)
Output: Array of event objects with timestamp, user_id, event_name, properties
Validation: Zod schema enforces date format, property types

Tool 2: get_user_profile
Inputs: user_id (string)
Output: {user_id, created_at, total_events, last_active, custom_attributes}
Validation: User_id must be non-empty; return 404 if not found

Tool 3: list_funnels
Inputs: funnel_name, date_range (enum: 7d|30d|90d)
Output: {funnel_name, total_users, conversion_rate_by_step, avg_time_to_completion}
Validation: Funnel_name checked against approved list

SETUP STEPS
1. Install TypeScript SDK
2. Define Zod schemas for all inputs
3. Implement tool handlers (map inputs to API calls)
4. Set up error handling (rate limits, auth failures, timeouts)
5. Test with mock client
6. Deploy to stdio or HTTP endpoint

COMMON PITFALLS
• Rate limiting: Implement request deduplication and caching
• Auth expiry: Refresh tokens before expiration
• Timeout: Set 30-second handler timeout
• Schema drift: Version tool definitions; notify clients on changes