Let Hermes act on live email evidence. Give each run only the authority it needs.
Connect Hermes to messages, flow runs, templates, contacts, and analytics through a shared MCP tool contract instead of a bespoke database integration.
✓Use an expiring, project-scoped credential for unattended runs.
Start with a read-only task
Operator prompt
Inspect the onboarding flow, explain where contacts stop, and show the evidence before proposing a change.
Connect
Remote MCP
Prompt
Inspect the live system
Boundary
Show before changing
[ 01 / 03 ]Task design
Ground each Hermes run in product-level evidence.
Gather the actual state
Read message timelines, enabled flows, recent run failures, and aggregate metrics before recommending a change.
Return a prepared artifact
Create a rendered template version or paused flow and return its identifier, not only prose advice.
Bound the unattended run
Scope and expiry live on the credential; consequential calls retain their own confirmation requirements.
[ 02 / 03 ]Connect
Start Hermes with a task you can verify.
Add the remote server to Hermes configuration, authorize the intended project, and begin with a bounded task whose evidence you can review.
Complete the OAuth handoff before delegating a write.
mcp_servers:
sendandretain:
url: https://sendandretain.com/api/mcp
auth: oauth[ 03 / 03 ]Related
Build around Hermes
Questions people ask us
Give Hermes a bounded task and evidence to return.
Start with one project and one read-only audit before allowing a prepared change.