b3nw/monarch-mcp-custom
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: disable goals queries in get_budgets to work around Monarch API errors
All checks were successful
Build and Push Monarch MCP Docker Image / build (push) Successful in 16s
Details

Browse Source 
The Monarch Money API returns errors for goals-related GraphQL fields
(lines 119-131 in query). Setting use_legacy_goals=False and use_v2_goals=False
skips these problematic fields while still returning budget data.
This commit is contained in:
Ben
2025-12-25 04:24:52 +00:00
parent a229537599
commit bb38e2441d
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/monarch_mcp_custom/server.py
View File

@@ -112,7 +112,9 @@ async def get_budgets(reason: Optional[str] = None) -> str:
client = await get_authenticated_client()
try:
budgets = await client.get_budgets()
# Disable both legacy and v2 goals to avoid API errors with goals fields
# The Monarch API appears to have issues with goals-related GraphQL fields
budgets = await client.get_budgets(use_legacy_goals=False, use_v2_goals=False)
except Exception as e:
error_msg = str(e)
# Check if this is a Monarch API error about budgets not being set up
@@ -120,7 +122,7 @@ async def get_budgets(reason: Optional[str] = None) -> str:
return serialize_json(
{
"error": "Budget data unavailable",
"detail": "The Monarch Money API returned an error. This may occur if budgets are not configured in your account.",
"detail": "The Monarch Money API returned an error. This may be a temporary API issue.",
"raw_error": error_msg,
}
)