joelcodes
10/21/2025, 7:35 PM{
"error": "Error: Error retrieving tool list from MCP server: 'GoogleSheets'. Http status code: 405 (Method Not Allowed)"
}
I've reported this many times with no good answer. Why does this happen?joelcodes
10/21/2025, 7:36 PM{
"error": "Error: Error retrieving tool list from MCP server: 'Reddit'. Http status code: 424 (Failed Dependency)"
}joelcodes
10/21/2025, 7:36 PMAkram Boussanni
10/22/2025, 5:37 AMjoelcodes
10/23/2025, 1:42 AMAkram Boussanni
10/23/2025, 5:28 AMjoelcodes
10/24/2025, 1:14 PMabhishekpatil4
10/24/2025, 1:36 PM/mcp to your MCP server URL as mentioned in the [previous thread(https://discord.com/channels/1170785031560646836/1404830315427659948/1426165768353222768)? This fixes the issue in most cases.
If you've tried that and it still fails, please share:
1. A minimal code snippet to reproduce this
2. OpenAI AgentSDK version (preferably package.json)
About the logs: these are client-side errors, so they don't reach our servers. That's why we need the details above to troubleshoot.
We really want to fix this for you and unblock you ASAP!joelcodes
10/24/2025, 1:41 PM@openai/agents: 0.1.9
const serverUrl = `https://mcp.composio.dev/composio/server/${process.env.COMPOSIO_<INTEGRATION>_MCP_SERVER_ID}/mcp?connected_account_id=${integration.composioConnectionId}`
tools.push(
hostedMcpTool({
serverLabel: '<IntegrationName>',
serverUrl,
})
)abhishekpatil4
10/24/2025, 2:08 PMjoelcodes
10/28/2025, 1:15 PMabhishekpatil4
10/28/2025, 1:32 PMjoelcodes
10/28/2025, 2:27 PMabhishekpatil4
10/29/2025, 2:15 AMjoelcodes
10/30/2025, 1:27 PM{
"error": "Error: Error retrieving tool list from MCP server: 'GoogleSheets'. Http status code: 404 (Not Found)"
}joelcodes
10/30/2025, 1:28 PM{
"error": "Error: Error retrieving tool list from MCP server: 'Slack'. Http status code: 404 (Not Found)"
}Akram Boussanni
10/30/2025, 1:39 PMabhishekpatil4
12/03/2025, 4:02 PM405 issue you were experiencing and wanted to share what we found.
According to the [MCP specification](https://modelcontextprotocol.io/specification/2025-11-25/basic/transports#listening-for-messages-from-the-server), when a client sends an HTTP GET request to check if a server supports SSE streaming, the server should return either:
- Content-Type: text/event-stream if it supports SSE, or
- HTTP 405 Method Not Allowed if it doesn't
The 405 response you're seeing is actually the expected behavior from our server since we don't support SSE streaming. The issue appears to be on the client side - ideally this should be handled gracefully by the client. We're investigating the 424 issue and will get back soon.
Hope this is helpful, let me know if you need any clarification here.