From eb67cef167b7db3be50fe892893035588c16d5f0 Mon Sep 17 00:00:00 2001 From: Krrish Dholakia Date: Sat, 4 Oct 2025 19:01:07 -0700 Subject: [PATCH] docs(mcp.md): add docs --- docs/my-website/docs/mcp.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/docs/my-website/docs/mcp.md b/docs/my-website/docs/mcp.md index 6b0ed067c55..ac2162af49e 100644 --- a/docs/my-website/docs/mcp.md +++ b/docs/my-website/docs/mcp.md @@ -219,6 +219,25 @@ mcp_servers: extra_headers: ["custom_key", "x-custom-header"] # These headers will be forwarded from client ``` +### Static Headers + +Sometimes your MCP server needs specific headers on every request. Maybe it's an API key, maybe it's a custom header the server expects. Instead of configuring auth, you can just set them directly. + +```yaml title="config.yaml" showLineNumbers +mcp_servers: + my_mcp_server: + url: "https://my-mcp-server.com/mcp" + static_headers: + X-API-Key: "abc123" + X-Custom-Header: "some-value" +``` + +These headers get sent with every request to the server. That's it. + +**When to use this:** +- Your server needs custom headers that don't fit the standard auth patterns +- You want full control over exactly what headers are sent +- You're debugging and need to quickly add headers without changing auth configuration ### MCP Aliases