MCP Tools not being discovered
# support
q
We didn't change anythign with our mcp and now they are not being discovered by your platform. They work everywhere else. Org: 35812337-6206-4ff8-a36e-6b61f02190d2 Working call: 019d936c-d268-7cc1-8930-1cd95918e657 (April 15) Failed call: 019d98bd-e901-7bb3-930f-f449bda98b14 (April 16) Message: "MCP tool discovery stopped working. Same tool config worked yesterday. Streamable HTTP server at https://develop-api.courtsapp.com/mcp is healthy. Sub-tools (courtsapp-*) no longer being injected into LLM requests."
v
Actionable next step: Test your MCP tool discovery directly in the Vapi dashboard by navigating to Tools > [Your MCP Tool] > Test and verify if the sub-tools are listed in the response. If they are missing, double-check that your
serverUrl
is correct and accessible, and review the tool execution logs for any errors. Example MCP tool config:
Copy code
json
{
  "type": "mcp",
  "server": { "url": "https://develop-api.courtsapp.com/mcp" }
}
If the issue persists, consult the [MCP integration documentation](https://docs.vapi.ai/tools/mcp) for further troubleshooting steps. Source: - [MCP integration documentation](https://docs.vapi.ai/tools/mcp)
q
says Streamable HTTP protocol is not supported in testing yet.
@Oshi Raghav any updates @Vapi @Vapi Support Bot
s
Hi, Thanks for the details - we've investigated the working and failed calls you shared. The MCP server itself isn't the issue. The calls are actually failing before MCP discovery even runs, which is why your server health doesn't reflect any problems.
What's happening is that your assistants are referencing tool IDs that no longer exist in your Vapi org. Specifically: Assistant 0f504f8e references tool dda69d57 - which is missing Assistant 9f384c74 references tool d5425722 - which is missing This causes calls to fail at startup with a resource validation error, before any tools are loaded.
To fix this, you have two options: Option A - Remove the missing tool references: Edit each assistant and remove the deleted tool IDs from their tool configuration.
Option B - Recreate the deleted tools: Recreate them in your Vapi dashboard and update the assistant references to point to the new IDs.