Configuring MCP that works in GitHub Copilot to Continue

[foongzy]

Hi all I am trying to connect my mcp to continue. It works on GitHub copilot with the following configs:

{"servers":
    {"MCP":
        {
            "type": "http",
            "url": "https://...",
            "headers": {
                "Authorization": "Token ...",
                "x-azure-org": "org name",
                "x-azure-project": "proj name"
            }
        }
    }
}

How do I configure this in continue? I tried a few methods with type as streamable-http, then also used requestOptions: headers: and placed those headers too but it didn't work. The error just says connection failed. The documentation on mcp didn't help either: https://docs.continue.dev/customize/deep-dives/mcp

Some configs I tried:

mcpServers:
  - name: MCP
    type: streamable-http
    url: https://....
    env:
        AUTHORIZATION: "Token ..."
        X-AZURE-ORG: "org name"
        X-AZURE-PROJECT: "proj name"

mcpServers:
  - name: MCP
    type: streamable-http
    url: https://....
    requestOptions:
        headers:
            AUTHORIZATION: "Token ..."
            X-AZURE-ORG: "org name"
            X-AZURE-PROJECT: "proj name"

I also tried creating a new folder .continue/mcpServers and creating a mcp.json file with the following configs but in this case, continue didn't even pick up the mcp unlike what other posts mentioned it should:

{"servers":
    {"MCP":
        {
            "type": "http",
            "url": "https://...",
            "headers": {
                "Authorization": "Token ...",
                "x-azure-org": "org name",
                "x-azure-project": "proj name"
            }
        }
    }
}

Please help, I am at a lost.

[bdougie]

We don't recommend json and instead recommend YAMl. We do outline how to use JSON here in the docs. https://docs.continue.dev/customize/deep-dives/mcp#using-json-mcp-format-from-claude,-cursor,-cline,-etc

[foongzy]

Hi @bdougie , I tried both and followed the docs but I keep getting connection closed and that's the only error I get. The MCP is definitely up and running. So reaching out on how to fix it.

[bdougie]

We have had Azure MCPs issues that have come up previously #8412. Unfortunately not enough that we've been able to prioritize a fix.

@uinstinct might be able to take a look, but we'd a strong user signal to prioritize this.

[foongzy]

@bdougie , that issue is after connecting. Mine I can't even connect it