Issues with Custom Auth and Request Body in Clay's MCP Server Integration Setup
Hey everyone 👋 Running into a blocker with Clay's custom MCP server integration and hoping someone here has dealt with something similar. Setup: I've connected an Opus 4.6 AI column to a custom MCP server hosted behind an API gateway. The server is confirmed working (tested via curl — correct SSE responses, file reads returning properly). The two blockers:
- 1.
Custom auth header — the server requires auth via a custom header (not a standard Bearer token). Clay's MCP connector doesn't seem to have an option to configure a custom header name, which results in a 401.
- 2.
Custom request body — the server also needs a JSON body to define which tools to use (e.g. method: tools/list). Clay doesn't appear to expose a way to define this when setting up a custom MCP connection.
Has anyone managed to get a custom MCP server working with non-standard auth in Clay? Or is this currently just not supported?
