Hybrid search, schema introspection and record read/write over FoxNose collections
Connect Remote server
claude mcp add --transport http knowledge https://mcp.foxnose.net/_mcp --header "Authorization: Bearer <YOUR_API_KEY>" --header "x-foxnose-prefix: <X_FOXNOSE_PREFIX>"{
"mcpServers": {
"knowledge": {
"url": "https://mcp.foxnose.net/_mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>",
"x-foxnose-prefix": "<X_FOXNOSE_PREFIX>"
}
}
}
}{
"servers": {
"knowledge": {
"type": "http",
"url": "https://mcp.foxnose.net/_mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>",
"x-foxnose-prefix": "<X_FOXNOSE_PREFIX>"
}
}
}
}Settings > Connectors > Add custom connector
URL: https://mcp.foxnose.net/_mcpReplace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server asks for a key before it lists its tools. Connect it with your own key to see them.
Headers
| Name | Description |
|---|---|
AuthorizationRequired, secret | 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… |
x-foxnose-prefixOptional | 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… |
Details
| Endpoint | https://mcp.foxnose.net/_mcp (Streamable HTTP) |
| First published | 15 Sep 2026 |
| Last updated | 15 Sep 2026 |
| Registry name | net.foxnose/knowledge |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.