Skip to content

search_issues and search_events fail with "OPENAI_API_KEY required" when using Anthropic provider #747

Closed

Description

@le4ker

Environment

  • Package: @sentry/mcp-server (installed globally via npm at /opt/homebrew/lib/node_modules/@sentry/mcp-server)
  • Transport: stdio mode via Claude Desktop
  • OS: macOS (Apple Silicon)
  • Node: Homebrew Node.js (/opt/homebrew/bin/node)
  • Sentry: SaaS (sentry.io), organization panther-labs

Steps to Reproduce

  1. Configure MCP server with Anthropic as the LLM provider:
{
  "mcpServers": {
    "Sentry": {
      "command": "/opt/homebrew/bin/node",
      "args": [
        "/opt/homebrew/lib/node_modules/@sentry/mcp-server/dist/index.js"
      ],
      "env": {
        "SENTRY_ACCESS_TOKEN": "sntryu_xxx",
        "SENTRY_HOST": "HOST.sentry.io",
        "EMBEDDED_AGENT_PROVIDER": "anthropic",
        "ANTHROPIC_API_KEY": "sk-ant-api03-xxx"
      }
    }
  }
}
  1. Connect via Claude Desktop
  2. Call search_issues or search_events with any natural language query

Expected Result

Based on the README documentation stating EMBEDDED_AGENT_PROVIDER supports 'openai' or 'anthropic', the semantic search tools should use Anthropic for query translation when configured with EMBEDDED_AGENT_PROVIDER=anthropic and a valid ANTHROPIC_API_KEY.

Actual Result

Both search_issues and search_events immediately fail with:

Configuration Error
There appears to be a configuration issue with your setup.
OPENAI_API_KEY environment variable is required for semantic search
Please check your environment configuration and try again.

Other tools work correctly (find_organizations, find_projects, find_releases, get_issue_details), confirming the SENTRY_ACCESS_TOKEN and general MCP connectivity are fine.

Activity

  1. dcramer commented on Jan 30, 2026

    @dcramer
    Member

    Happen to know which version this was in?

  2. dcramer commented on Feb 7, 2026

    @dcramer
    Member

    Made a number of imrpovements around this now, but please reopen if its still happening.

  3. le4ker commented on Feb 8, 2026

    @le4ker
    Author

    Happen to know which version this was in?

    No. I’ll try again and reopen if it persists. Thank you!

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