search.ag-grid.com API returns 500 Internal Server Error - All MCP tools broken

[SimeonAleksandrov-Deltek]

Problem Description

The AG Grid MCP server stopped working around November 19-21, 2025. All API endpoints on https://search.ag-grid.com return HTTP
500 Internal Server Error.

Impact

All MCP tools that query the API are broken:

• ❌ search_docs → 500 Internal Server Error
• ❌ list_versions → 500 Internal Server Error
• ❌ ReadMcpResourceTool(ag-mcp://articles) → 500 Internal Server Error
• ❌ ReadMcpResourceTool(ag-mcp://examples) → 500 Internal Server Error
• ✅ detect_version → Works (doesn't use API, reads local package.json only)

Steps to Reproduce

1. Direct API Test (without MCP)

# Test versions endpoint
curl "https://search.ag-grid.com/versions"
# Result: "Internal Server Error"

# Test with full browser headers
curl -H "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36" \
     -H "Accept: application/json" \
     "https://search.ag-grid.com/versions"
# Result: "Internal Server Error"

# Test HTTP status code
curl -s -o /dev/null -w "%{http_code}" "https://search.ag-grid.com/versions"
# Result: 500

2. Via MCP in Claude Code

// This works
mcp__ag-mcp__detect_version()
// Returns: AG Grid v33.3.0, react, Enterprise

// These fail with 500 error
mcp__ag-mcp__search_docs({ query: "column sorting" })
// Error: API request failed: 500 Internal Server Error

mcp__ag-mcp__list_versions()
// Error: API request failed: 500 Internal Server Error

ReadMcpResourceTool({ server: "ag-mcp", uri: "ag-mcp://articles" })
// Error: Failed to fetch resource: 500 Internal Server Error

Timeline

• Before Nov 19, 2025: Everything worked perfectly
• Nov 19-21, 2025: API started returning 500 errors
• Nov 21, 2025: Confirmed still broken

Environment

• ag-mcp version: v1.0.0 (latest from npm)
• Installation: npx ag-mcp
• Client: Claude Code on Windows
• AG Grid version: v33.3.0
• Framework: React
• Edition: Enterprise
• Node.js: v23.10.0
• npm: 10.9.2

Configuration

claude_desktop_config.json:

{
  "mcpServers": {
    "ag-mcp": {
      "command": "npx",
      "args": ["-y", "ag-mcp"]
    }
  }
}

Additional Tests

Network Connectivity

# AG Grid main site is reachable
curl -s -o /dev/null -w "%{http_code}" "https://www.ag-grid.com/"
# Result: 200 OK

# Documentation pages work fine
curl -I "https://www.ag-grid.com/react-data-grid/column-definitions/"
# Result: HTTP/1.1 200 OK

Code Verification

I checked the source code in src/api/fetch.ts and confirmed:

• ✅ Browser headers are properly set (including User-Agent)
• ✅ getBrowserHeaders() function is implemented correctly
• ✅ All endpoints use proper header configuration

This is NOT a client-side issue - the backend API server search.ag-grid.com is returning 500 errors for all requests.

Workaround

Temporarily using WebFetch to access AG Grid documentation directly:

Read https://www.ag-grid.com/react-data-grid/[topic]/ and explain...

Request

Please investigate and fix the search.ag-grid.com backend infrastructure. The API was working fine until a few days ago.

Thank you!

[SimeonAleksandrov-Deltek]

@xiaofangluvyou Thank you for the quick response!

Before I install this update, could you please clarify a few things:

1. What does this ZIP file contain?

   • Is it a patched version of ag-mcp?
   • Which files were modified?
   • What specific issue does it fix?

2. How should I install it?

   • Should I extract it and run npm install locally?
   • Or is there a specific installation command?

3. Is this an official fix?

   • Are you part of the AG Grid team?
   • Will this be published to npm as an official release?

I'm hesitant to install files from unknown sources for security reasons. If this is a legitimate fix, could you:

• Share the source code changes as a GitHub commit/PR?
• Or explain what was changed so I can verify it?

Thank you for your understanding! 🙏

[aucyunjian]

I'm encountering the same issue. Is there any official plan to fix it?

[iw-tundo]

Same for me. It happens for a few days now.