mcp-api-key-auth
Installation
SKILL.md
Purpose
Enable external MCP clients (Claude Code, Cursor, etc.) to authenticate with the stock data service using independent API keys, and track per-tool usage (table name, record count) for monitoring.
When to Use
- User wants to create or manage MCP API keys
- User wants to configure an external MCP client to connect to this service
- User wants to view MCP tool usage statistics (which tools called, which tables queried, how many records)
- User needs to troubleshoot MCP authentication errors (401, invalid key, expired key)
Architecture
- API Key management is on the HTTP server (port 8000), protected by JWT login
- MCP protocol is on the MCP server (port 8001), protected by API key in request headers
- Usage tracking records are stored in ClickHouse
mcp_tool_usage_logtable