continuedev/continue · error · Error

MCP config with URL and no type specified failed both SSE an

Error message

MCP config with URL and no type specified failed both SSE and HTTP connection: ${e instanceof Error ? e.message : String(e)}

What it means

Post-processing fallback in the non-streaming chat response converter: the response was received successfully but its provider label doesn't match any known conversion case. In practice hard to hit because the same provider check gated the request; it guards future/unknown provider values.

Source

Thrown at core/context/mcp/MCPConnection.ts:276

                  );
                } else {
                  try {
                    const transport = this.constructHttpTransport({
                      ...this.options,
                      type: "streamable-http",
                    });
                    await this.client.connect(transport, {});
                    this.transport = transport;
                  } catch (e) {
                    try {
                      const transport = this.constructSseTransport({
                        ...this.options,
                        type: "sse",
                      });
                      await this.client.connect(transport, {});
                      this.transport = transport;
                    } catch (e) {
                      throw new Error(
                        `MCP config with URL and no type specified failed both SSE and HTTP connection: ${e instanceof Error ? e.message : String(e)}`,
                      );
                    }
                  }
                }
              }

              // TODO register server notification handlers
              // this.client.transport?.onmessage(msg => console.log())
              // this.client.setNotificationHandler(, notification => {
              //   console.log(notification)
              // })
              const capabilities = this.client.getServerCapabilities();

              // Resources <—> Context Provider
              if (capabilities?.resources) {
                try {
                  const { resources } = await this.client.listResources(

View on GitHub (pinned to 5522c6f44c)

Solutions

1. Ensure any custom provider added to determineVertexProvider also has a converter case in the switch
2. Update/align openai-adapters package versions so routing and conversion stay in sync
3. Report upstream if it occurs with an unmodified install

const isKnownProvider = (p: string): p is 'gemini' | 'anthropic' | 'mistral' => ['gemini','anthropic','mistral'].includes(p);

When it happens

Trigger: determineVertexProvider returns a value outside 'gemini'|'anthropic'|'mistral' after the request succeeded — e.g. a custom/extended provider map injected by a fork or future version.

Common situations: Forked or locally extended adapter where a provider is added to routing but not to response conversion; mismatched package versions between routing utilities and the adapter.

Related errors

• no url found
• URL is not defined in params
• Response body is null
• Profile ${profileId} not found
• No workspace directories found. Make sure you've opened a fo

AI-assisted analysis of continuedev/continue@5522c6f44c (2026-08-27). Data as JSON: /api/errors/bb26122be092a2ed. Report an issue: GitHub.