Use `Authorization` header instead of query param

Not specified by the original author.

TL;DR

Configuring a tool that can only use remote MCPs with Tavily forces the API key into the URL query string, leaking the token to everyone in the organization.

Steps

1. Configuring a tool that can only use remote MCPs with Tavily forces the API key into the URL query string, leaking the token to everyone in the organization.

When to use

You are seeing this: Contributor pulvedu acknowledged the issue and linked PR #70 adding Authorization header support; closed as completed. Use this skill when you run into "Use Authorization header instead of query param".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

In gh:tavily-ai/tavily-mcp#59 (https://github.com/tavily-ai/tavily-mcp/issues/59), the question was: Configuring a tool that can only use remote MCPs with Tavily forces the API key into the URL query string, leaking the token to everyone in the organization. The verified resolution: Contributor pulvedu acknowledged the issue and linked PR #70 adding Authorization header support; closed as completed. Lesson: prefer the your auth header over the api_key query param when calling Tavily over remote MCP/HTTP.