I want to connect the “Make AI Agents” (Beta) module to the official TomTom MCP server (https://mcp.tomtom.com/maps) to use the calculate_route and search_address tools within my agent logic.
What is the problem & what have you tried?
Problem: I am getting a persistent HTTP 401 Unauthorized error during the connection attempt.
Technical Analysis: The TomTom MCP server expects the API key in a specific header named tomtom-api-key. However, the Make MCP connection UI seems to send the token as a standard Authorization: Bearer header by default.
Error messages or input/output bundles
What I have tried:
Created a TomTom API key with all required products active (MCP Server, Routing API, Search API).
Standard connection setup in Make with the key in the “API Key / Access token” field.
Error messages or input/output bundles
{
“message”: “Attempted to connect to the MCP server with an access token but the server returned an error.”,
“suberrors”: [{
“message”: “Error POSTing to endpoint (HTTP 401): {"jsonrpc":"2.0","error":{"code":-32001,"message":"Missing or invalid tomtom-api-key header"},"id":null}, SSE error: Non-200 status code (405)”
}]
}
This is not a TomTom issue. The connection is failing because TomTom expects the key in a custom tomtom-api-key header, while Make’s MCP connection sends the token as an Authorization Bearer header.
So with the current Make MCP connection, that server will not authenticate correctly. If Make does not let you define custom headers for the MCP connection, then TomTom’s MCP server is not compatible with it in this setup.
Dr. Tanvi Sachar
Monday Certified Partner, Tuesday Wizard
What is your goal?
What is the problem & what have you tried?
Error messages or input/output bundles
Screenshots (scenario flow, module settings, errors)