Proposal: Integrate Hermes MCP to function as MCP protocol layer

### Background

This was proposed in the ash_ai Discord channel and I've been working up a proof of concept. Since it looks imminently doable, I'm creating a more formal Proposal issue here. It's too soon for a PR, so this can serve as a place for focused collaboration on this feature.

### Feature Description

Ultimately, the feature is to "not have to maintain and evolve a compliant MCP Server implementation".
Wrapped up with how we end up doing this, however, is the AshAi developer experience, so getting out of the gate on solid ground there is part of this proposal, even though I don't have a clear idea yet on what that can look like.

I'll share some progress, thoughts and questions shortly.

### Alternatives

- continuing to evolve the in house MCP Server already in the library
- other MCP protocol implementations (?)

No files, tests, or entry points are named. Start by reviewing the library's existing in-house MCP Server and the proof of concept mentioned in the issue, then clarify the integration design and AshAi developer experience with the project discussion. Done requires an agreed implementation approach and clear scope for replacing or wrapping the current MCP protocol layer.

Written by the indexing model from the issue text.