MCP

Remote MCP endpoint, transport, auth, and dependency notes for HeadlessX.

by @saifyxpro

Endpoint

MethodPathPurpose
ALL/mcpremote MCP endpoint over HTTP

Auth

MCP clients must use:

MCP does not accept:

  • DASHBOARD_INTERNAL_API_KEY

Transport

HeadlessX exposes MCP as a remote HTTP endpoint rather than as an SSE-specific API route.

Notes

  • use normal API keys created from the dashboard
  • tool availability depends on the same backend services as the underlying HTTP routes
  • queue-backed MCP tools still depend on Redis and the worker
  • YouTube MCP tools depend on YT_ENGINE_URL
  • MCP tool naming follows the operator model even though the transport endpoint remains /mcp