[FEAT] Accept Headers in MCPServerConfig when type is HTTP

[wakeupmh]

I was trying to connect to an hf-mcp-server using the MCPServerConfig HTTPServerConfig as follows:

   const mcpConfig = new MCPConfiguration({
      servers: {
        "hf-mcp-server": {
          url: "https://huggingface.co/mcp",
          headers: {
            Authorization: "Bearer " + process.env.HF_TOKEN!,
          },
          type: "http",
        },
      },
    });

However I see the error below:

Describe alternatives you've considered

I overcame by doing a StudioServerConfig

const mcpConfig = new MCPConfiguration({
      servers: {
        "hf-mcp-server": {
          command: "npx",
          args: [
            "mcp-remote",
            "https://huggingface.co/mcp",
            "--header",
            "Authorization: Bearer " + process.env.HF_TOKEN!,
          ],
          type: "stdio",
        },
      },
    });

Should we accept headers when using http mcp connections?

[omeraplak]

Hey @wakeupmh,
Thanks for reporting the issue. We’ll take a look soon!

[wakeupmh]

I could work on this issue if you want @omeraplak

[omeraplak]

Hey, I just reviewed it again actually, you can send headers using requestInit. Is this a different use case?

const mcpConfig = new MCPConfiguration({
      servers: {
        "hf-mcp-server": {
          url: "https://huggingface.co/mcp",
          requestInit: {
             headers: { Authorization: "Bearer " + process.env.HF_TOKEN!, },
           },
          type: "http",
        },
      },
    });

[bondli]

i want to passport userId by request header add into requestInit, how to do it ?

my call agent code:

my mcp config code:

how to setting the userId from request's userContext

[wakeupmh]

@omeraplak I've tested and this works, sorry for missing it in the types :/

[omeraplak]

i want to passport userId by request header add into requestInit, how to do it ?

my call agent code:

my mcp config code:

how to setting the userId from request's userContext

Hey! You can actually initialize your MCP dynamically, there’s an example here that might help:
https://github.com/VoltAgent/voltagent/blob/main/examples/with-google-drive-mcp/server/src/index.ts#L167

Let me know if you run into any issues!

[bondli]

i want to passport userId by request header add into requestInit, how to do it ?
my call agent code:

my mcp config code:

how to setting the userId from request's userContext

Hey! You can actually initialize your MCP dynamically, there’s an example here that might help: https://github.com/VoltAgent/voltagent/blob/main/examples/with-google-drive-mcp/server/src/index.ts#L167

Let me know if you run into any issues!

This implementation is not elegant, and it can achieve the desired header transfer, but it is very ungraceful. I wonder if we can inject context to implement it when calling toolcall

[omeraplak]

Yep, I agree. it’s not very elegant.
Actually, tools can already access the context: https://voltagent.dev/docs/agents/context/.
What kind of implementation did you have in mind?
If you can share an example of the API you’re thinking of, I believe we can come up with a solution 💥

[bondli]

Yep, I agree. it’s not very elegant. Actually, tools can already access the context: https://voltagent.dev/docs/agents/context/. What kind of implementation did you have in mind? If you can share an example of the API you’re thinking of, I believe we can come up with a solution 💥

// getTools add context
const allTools = await mcpConfig.getTools({context});

// 1. when config can get the context
// 2. requestInit change to function，can get the context
const mcpConfig = new MCPConfiguration({
servers: {
// 新增本地HTTP类型的MCP server
'note-mcp': {
type: 'http',
url: ${process.env.MCP_BASE_URL}/note-mcp || http://localhost:9587/mcp/note-mcp,
requestInit: (context) => {
return you logic;
},
},
'fetch-mcp': {
type: 'http',
url: ${process.env.MCP_BASE_URL}/fetch-mcp || http://localhost:9587/mcp/fetch-mcp,
requestInit,
}
},
});

[omeraplak]

Thanks! Let’s see what we can do.