Skip to content

Central QSR agent core (Hermes MCP client + service registry) #107

Description

@avinash-palleti

Description Stand up Hermes as the central agent: connect it to each service's MCP server, register the tool set, and answer operator questions over live + historical data. Establish the system prompt and the source-agnostic contract so real and simulated services are indistinguishable.

Acceptance Criteria

[ ] Hermes connects to ≥2 service MCP servers and lists their tools.
[ ] Agent answers a live question and a historical question drawn through tools.
[ ] Answers an unscripted question (no pre-written query).
[ ] Every read/action goes through a declared tool — no side channel.
[ ] Model runs on a local OVMS endpoint on the target Intel box; framework kept swappable (HTTP+MCP only).
[ ] Service list is configurable (resolves deck question 4: discovery vs. handed list).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions