FoxNose Knowledge
Hybrid search, schema introspection and record read/write over FoxNose collections
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http foxnose-knowledge 'https://mcp.foxnose.net/_mcp' --header 'Authorization: <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.>' --header 'x-foxnose-prefix: <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.>'{
"mcpServers": {
"foxnose-knowledge": {
"type": "http",
"url": "https://mcp.foxnose.net/_mcp",
"headers": {
"Authorization": "<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.>",
"x-foxnose-prefix": "<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.>"
}
}
}
}Frequently asked questions
What is FoxNose Knowledge?
Hybrid search, schema introspection and record read/write over FoxNose collections
How do I install FoxNose Knowledge?
It runs as a remote server. In Claude Code: claude mcp add --transport http foxnose-knowledge 'https://mcp.foxnose.net/_mcp' --header 'Authorization: <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.>' --header 'x-foxnose-prefix: <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.>'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does FoxNose Knowledge need an API key?
Yes. It expects Authorization, x-foxnose-prefix, which you set in its configuration.
Who maintains FoxNose Knowledge?
It is published by net.foxnose. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.