search_issues and search_events tools fail with parsing error #776

Bug Description

The search_issues and search_events tools consistently fail with a parsing error when using natural language queries, while other tools like find_projects and get_issue_details work correctly.

Error Message

Error: It looks like there was a problem communicating with the Sentry API.

Event ID: [various IDs]

No object generated: could not parse the response.

Steps to Reproduce

1. Configure the Sentry MCP server with valid credentials and SENTRY_HOST=us.sentry.io
2. Call search_issues with any natural language query:

   search_issues(
     organizationSlug='dave-energy',
     naturalLanguageQuery='recent unresolved issues',
     regionUrl='https://us.sentry.io',
     limit=5
   )

3. Observe parsing error

Expected Behavior

The tool should return a list of issues matching the query, similar to how the direct Sentry REST API works.

Actual Behavior

The tool fails with "No object generated: could not parse the response."

What Works

• ✅ find_organizations() - works correctly
• ✅ find_projects() - works correctly
• ✅ get_issue_details() - works correctly with issue IDs
• ✅ Direct Sentry REST API calls (e.g., curl https://us.sentry.io/api/0/organizations/dave-energy/issues/) - work correctly

What Doesn't Work

• ❌ search_issues() with any natural language query - parsing error
• ❌ search_events() with any natural language query - parsing error

Environment

• MCP Server Version: @sentry/mcp-server@0.29.0 (latest as of 2026-02-05)
• Sentry Region: US region (us.sentry.io)
• Organization: dave-energy
• Install Method: npx --yes @sentry/mcp-server@latest

Additional Context

The issue appears to be specific to the natural language query translation feature used by search_issues and search_events. Direct API calls work fine, suggesting the problem is in how the MCP server parses/transforms the Sentry API response for these specific tools.

We've verified:

• SENTRY_HOST is correctly set to us.sentry.io (not sentry.io)
• API credentials are valid (other tools work)
• The Sentry API returns valid responses (verified with curl)
• Using @latest version still produces the error

This suggests a bug in the response parsing logic for the natural language search tools.