
Hybrid search, schema introspection and record read/write over FoxNose collections
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
FoxNose API key pair, created per environment in the dashboard under Flux API > Access, or through the Management API. Scopes follow the key: a collection the key cannot read over REST is not reachable over MCP either. The key also selects the environment, which is why no host or prefix appears in the URL. Hosted connectors that offer a single token field and always send Authorization: Bearer <token> cannot use this scheme at all; they need a bearer token instead - an opaque fxk_ credential bound to an existing key, issued through the Management API.
Which Flux API to expose - the delivery endpoint serving the collections connected to it. Only needed when the key can read more than one; with a single readable API it is selected automatically. Sending the wrong value returns 403, and omitting it where it is required returns 400 listing the key's own options.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
We haven't seen a tool list from this server yet.
https://mcp.foxnose.net/_mcpclaude mcp add --transport http knowledge https://mcp.foxnose.net/_mcpHeaders: Authorization (required), x-foxnose-prefix