Skip to content

search_issues and search_events fail on hosted MCP server (mcp.sentry.dev) - Incorrect API key provided #779

Closed

Description

@MHDAndrew

Environment

  • Server: Hosted remote MCP server at https://mcp.sentry.dev/mcp
  • Client: Claude Code (OAuth authentication)
  • Organization: mobility-help-desk (region: us.sentry.io)

Affected Tools

  • search_issues
  • search_events
  • search_issue_events

Working Tools

  • whoami
  • find_organizations
  • find_projects
  • get_issue_details

Steps to Reproduce

  1. Connect to the hosted Sentry MCP server at https://mcp.sentry.dev/mcp via OAuth
  2. Call search_issues or search_events with any natural language query (e.g., "all unresolved issues")
  3. The call fails immediately

Expected Result

The search tools should translate the natural language query and return matching issues/events.

Actual Result

All tools that depend on AI-powered query translation fail with:

AI Provider Error

The AI provider service is not available for this request.

The AI provider returned an error: Incorrect API key provided: sk-svcac***...pIIA.
You can find your API key at https://platform.openai.com/account/api-keys.

This is a service availability issue that cannot be resolved by retrying.

Notes

  • The error indicates the server-side OpenAI API key used for natural language query translation is misconfigured or expired.
  • This only affects the hosted MCP server (mcp.sentry.dev), not self-hosted installations.
  • Tools that don't require AI translation (e.g., whoami, find_organizations, find_projects, get_issue_details) work correctly, confirming OAuth authentication and Sentry API access are fine.
  • Possibly related to search_issues and search_events fail with "OPENAI_API_KEY required" when using Anthropic provider #747, which reports a similar issue for self-hosted setups with the Anthropic provider.

Activity

  1. Yingjie-Zhao commented on Feb 6, 2026

    @Yingjie-Zhao

    I can confirm this issue as well. I'm using the hosted MCP server at mcp.sentry.dev with Claude Code via OAuth authentication.

    Reproduction: Calling search_issues with any natural language query immediately fails with the exact same error:

    AI Provider Error
    
    The AI provider returned an error: Incorrect API key provided: sk-svcac***...pIIA.
    

    Working tools: whoami, find_organizations, find_projects, get_issue_details — all function correctly, confirming OAuth and Sentry API access are fine.

    Broken tools: search_issues, search_events, search_issue_events — anything that relies on server-side AI query translation.

    Looking forward to a fix!

  2. swingerman commented on Feb 6, 2026

    @swingerman

    Same here. Since yesterday

  3. saschagehlich commented on Feb 6, 2026

    @saschagehlich

    Okay wow, just wanted to try Sentry MCP today and encountered this error - searched the whole web and asked all LLMs about this issue and tried to find a way to enter my OpenAI api key. Apparently it's just sentry's OpenAI API Key being invalid, lol.

  4. HPODEV commented on Feb 6, 2026

    @HPODEV

    +1, i have same issue (mcp.sentry.dev)

  5. 0xRaduan commented on Feb 6, 2026

    @0xRaduan

    same issue!

  6. miliberlin commented on Feb 6, 2026

    @miliberlin

    I just tried to use the Sentry MCP server via the Claude Code CLI and running into the same issue. It's quite a frustrating first experience. Please update your OpenAI API key 🙏

  7. 0xRaduan commented on Feb 6, 2026

    @0xRaduan
  8. dcramer commented on Feb 6, 2026

    @dcramer
    Member

    Sorry yall - looks like we might have invalidated a key!

    A couple of follow-ups we'll resolve here

  9. dcramer commented on Feb 6, 2026

    @dcramer
    Member

    should be fully resolved and shouldn't be possible to slip through in the future due to #781

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions