Add Fidelis optional MCP manifest

[roli-lpci]

Adds a version-pinned, local-first Fidelis MCP catalog entry.

The uvx --from fidelis-memory==0.1.0 fidelis mcp serve launch contract was verified against the released CLI, and Loki catalog tests pass. The post-install guidance makes the persistent local-service prerequisites and ingestion step explicit.

Requested in wundercorp/awesome-mcp#64 (comment).

[wunderships]

We are planning to deprecate direct MCP integration, we will keep this PR open for now. Please consider a plugin approach if this is feasible!

[roli-lpci]

Thanks for the heads-up. We’ll leave the direct-MCP PR unchanged and assess a plugin-native integration against Loki’s emerging plugin interface; we’ll follow up here only if there’s a concrete fit.

[roli-lpci]

Thanks for pointing us toward a plugin. I revisited Loki's current memory-provider API and contribution policy, and published Fidelis as a standalone native memory provider: https://github.com/hermes-labs-ai/loki-fidelis

It provides prompt-time recall of current local records plus explicit recall, verbatim storage, and correction tools. It uses Loki's MemoryProvider interface and the local Fidelis service, with no Loki core changes or direct MCP registration. I validated it against current Loki with the plugin validator, integration tests through real provider discovery, and a pinned Git install from the public repository into a fresh profile. Correction requires Fidelis Memory 0.3.0rc1 or newer; the README states that prerequisite.

I'm closing this older MCP manifest PR as superseded. Loki's plugin catalog requires a pinned release to be at least two weeks old, so a catalog entry for this new plugin is not eligible yet. The direct Git install works today, and the catalog path can follow once the pin meets that policy.