Skip to content

External URL server with API key auth — gateway returns "Missing Authorization header" #711

@chicogonzales

Description

@chicogonzales

I published an external URL server (plith/plith) with x-api-key configured
as a required header parameter. The publish preview shows correct forwarding.

When calling the gateway directly, I get:

{"error":"invalid_token","error_description":"Missing Authorization header"}

I understand the gateway may require its own OAuth layer before proxying.
However, the OAuth connection flow also fails:

https://api.smithery.ai/connect/plith/plith/auth
→ "Connection failed - We couldn't authenticate with the upstream server."

So neither path works:

  1. Direct gateway call with x-api-key → rejected (expects OAuth)
  2. OAuth connect flow → fails to authenticate with upstream

Direct access to the server works fine with the x-api-key header.

Server: plith/plith
Listing: https://smithery.ai/servers/plith/plith
Gateway: https://plith--plith.run.tools
Direct: https://plith.ai/api/mcp

Is there a step I'm missing for external URL servers with API key auth?
Or is this a known limitation of the gateway?

Workaround: Users connect directly to the server URL.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions