Umbrella MCP Server

# Request Comparison Analysis ## UI Request (WORKING) ``` URL: https://api-front.umbrellacost.io/api/v1/invoices/caui?groupBy=none&groupBy=usagedate&startDate=2025-01-01&endDate=2025-09-27&periodGranLevel=month&costType=cost&costType=discount Method: GET Status: 200 OK ``` ### Key Characteristics: 1. **Subdomain**: `api-front.umbrellacost.io` (not `api.umbrellacost.io`) 2. **NO accountId parameter** in the URL 3. **Double groupBy**: `groupBy=none&groupBy=usagedate` 4. **NO isUnblended parameter** 5. **NO excludeFilters parameter** 6. **NO explicit apikey in URL** (likely in headers) ## MCP Request (NOT WORKING for MasterBilling) ``` URL: https://api.umbrellacost.io/api/v1/invoices/caui?startDate=2025-01-01&endDate=2025-09-30&accountId=Master-59f88c&groupBy=none&periodGranLevel=month&costType=cost&costType=discount&isUnblended=true&excludeFilters[chargetype][]=Tax API Key: 8bd39ae4-ebea-4426-bd22-07349dd8b962:21112:0 ``` ### Key Characteristics: 1. **Subdomain**: `api.umbrellacost.io` 2. **HAS accountId=Master-59f88c** in the URL 3. **Single groupBy**: `groupBy=none` 4. **HAS isUnblended=true** 5. **HAS excludeFilters[chargetype][]=Tax** ## Critical Differences: ### 1. API Endpoint - UI uses `api-front.umbrellacost.io` - MCP uses `api.umbrellacost.io` - These might be different services with different behaviors ### 2. Account Selection Method - UI: NO accountId in URL - relies on API key to determine account - MCP: Explicit accountId in URL - might conflict with API key ### 3. GroupBy Parameter - UI: Sends TWO groupBy values (`none` and `usagedate`) - MCP: Sends ONE groupBy value (`none`) ### 4. Default Parameters - MCP adds: `isUnblended=true`, `excludeFilters[chargetype][]=Tax` - UI doesn't send these ## Working Hypothesis: The issue might be: 1. **Account ID Conflict**: When using the API key format `base:accountKey:divisionId`, the backend might expect NO accountId in the URL 2. **API Endpoint**: `api-front` might handle GCP accounts differently than `api` 3. **GroupBy Requirements**: GCP accounts might require the double groupBy pattern ## Test Plan: 1. Remove accountId from URL when API key contains account info 2. Try api-front endpoint 3. Test double groupBy parameter