Limits

What the MCP surface does not do yet. This is current state, not a roadmap.

Protocol version

FoxNose serves MCP Streamable HTTP 2025-03-26. See the MCP Server reference → Transport for the wire-level details.

No OAuth

OAuth is not implemented. Authentication is by Flux API key — Simple, Secure, or a Bearer fxk_ token — and that is the only way to authenticate to the MCP endpoint today.

An unauthenticated request is answered with a 401 and a challenge naming the key-based schemes:

WWW-Authenticate: Simple realm="flux-api", Secure realm="flux-api"

There is no OAuth discovery in that challenge — no protected-resource metadata to follow, and no authorization server to negotiate with. A client that expects the MCP authorization flow will not find one; it needs a key. See Flux API Authentication → WWW-Authenticate.

Not in the connector directories

FoxNose is not currently listed in the Anthropic or OpenAI connector directories. Both require OAuth for directory listing, and FoxNose does not implement it yet — see No OAuth above. This does not block direct integration: connecting via a self-configured MCP client, a hosted connector with a bearer token, or the OpenAI Responses API all work today, as covered in Connect Claude and Connect ChatGPT and OpenAI. It only means an end user can't discover and add a FoxNose connector by browsing a directory inside Claude or ChatGPT — someone has to configure the connection.