Hi there, thanks for reaching out to support!
I can see how the current docs might not cover all the details you need. Here's what's happening behind the scenes: When you add a custom MCP server in Claygent, the system supports both Streamable HTTP and SSE (Server-Sent Events) transport types, and the "MCP API key" field is actually optional—if you provide one, Claygent automatically sends it as a Bearer token in the Authorization header (format: Authorization: Bearer {your-api-key}). This means even if your MCP server uses a different auth method (like a custom header or query parameter), you'll need to configure your server to accept the Bearer token format that Claygent sends. If your MCP server requires different authentication arguments or headers beyond a simple Bearer token, you may need to wrap it with a proxy that translates Claygent's authentication into what your server expects. The system doesn't currently expose additional configuration options for custom auth methods or transport-specific arguments in the UI, so the Bearer token approach is the standard path forward. If you need more specific help setting up your particular MCP server, feel free to share more details about which server you're trying to connect and what auth method it uses!
