MCP Server API Key Authentication

This skill explains how to authenticate with MCP servers that use API keys or custom headers instead of OAuth.

When to Use This Skill

Use this skill when an MCP server requires authentication but doesn't support OAuth. This typically manifests when a connection attempt returns a requirement for an "api-key" or specific headers.

Workflow

Step 1: Identify Required Header

Determine which header name the server expects for its API key. Common names include:

• x-api-key
• Authorization (typically used as Bearer <token>)
• api-key