continuedev/continue · error · Error
Error getting prompt: MCP Connection ${serverName} not found
Error message
Error getting prompt: MCP Connection ${serverName} not found What it means
The anthropic-on-Vertex streaming branch received a non-2xx response; the response body is JSON-stringified into the message. Represents an upstream HTTP failure during a streaming chat request.
Source
Thrown at core/context/mcp/MCPManagerSingleton.ts:195
getStatuses(): (MCPServerStatus & { client: Client })[] {
return Array.from(this.connections.values()).map((connection) => ({
...connection.getStatus(),
client: connection.client,
}));
}
setStatus(serverId: string, status: MCPServerStatus["status"]) {
this.connections.get(serverId)!.status = status;
}
async getPrompt(
serverName: string,
promptName: string,
args: Record<string, string> = {},
) {
const connection = this.connections.get(serverName);
if (!connection) {
throw new Error(
`Error getting prompt: MCP Connection ${serverName} not found`,
);
}
return await connection.client.getPrompt({
name: promptName,
arguments: args,
});
}
}
View on GitHub (pinned to 5522c6f44c)
Solutions
- Parse the embedded JSON body for Google's specific error reason
- Enable the Anthropic model in Model Garden and grant the service account access
- Verify model id format claude-*@<version> and region
- Add retry with exponential backoff for 429/5xx around the stream start
Defensive patterns
Strategy: retry
Try / catch
try { for await (const c of api.chatCompletionStream(body, signal)) {} } catch (e) { const msg = (e as Error).message; if (/429|5\d\d/.test(msg)) await retryWithBackoff(); else throw e; } Prevention
- Enable publisher models in Model Garden before streaming
- Retry stream initiation (not mid-stream) on 429/5xx
- Log the embedded JSON body for postmortems
When it happens
Trigger: 401/403 auth or missing model access (anthropic model not enabled in Vertex Model Garden); 404 bad model id; 429 quota; 400 malformed converted payload.
Common situations: Claude model not subscribed/enabled in the GCP project; wrong region for the Anthropic endpoint; token expiry during long-lived streaming sessions; quota exhaustion under load.
Related errors
- Unsupported transport type: ${this.options.type}
- MCP Connection ${serverId} not found
- no query params found
- No MCP authorization code found for ${serverUrl}
- Failed to fetch messages: ${response.statusText}
AI-assisted analysis of continuedev/continue@5522c6f44c (2026-08-27).
Data as JSON: /api/errors/620e7819a8f12356.
Report an issue: GitHub.