Integrations guides

A practical guide to github operations in a verified Hermes/Rocky workflow.

A practical guide to google workspace in a verified Hermes/Rocky workflow.

A practical guide to discord collaboration patterns in a verified Hermes/Rocky workflow.

A practical guide to shopify operations boundaries in a verified Hermes/Rocky workflow.

How to add Model Context Protocol servers to Rocky with scoped tools, tests, and rollback notes.

Plan Model Context Protocol server adoption with safe tool discovery, scoped credentials, testing, and rollback.

Install and configure MCP servers with reviewed sources, narrow tool filters, explicit transport trust, and real authenticated tool-call verification.

Expose a tool-equipped Hermes profile to approved local clients through an authenticated OpenAI-compatible API with deliberate session and network boundaries.

Run Hermes as an Agent Client Protocol server for editor-native coding with curated tools, stdio transport, visible approvals, and provider reuse.

Let local OpenAI-compatible applications use a Hermes-managed OAuth subscription for raw model inference without exposing the full agent toolset.

Choose between ACP, the TUI gateway, and the OpenAI-compatible API server when embedding Hermes in an IDE, custom host, or web client.

Use AIAgent inside Python services and pipelines with explicit tool allowlists, isolated instances, quiet output, and bounded authority.

Receive Microsoft Graph notifications through Hermes with clientState validation, HTTPS termination, minimal responses, and subscription lifecycle checks.

Trace how Hermes adapts synchronous agent runs into ACP editor sessions with workspace binding, streamed events, cancellation, and fail-closed approvals.

Choose stdio or HTTP MCP transport, preserve certificate verification, configure mTLS or OAuth, and fail fast on unsafe connection settings.

Enable Spotify tools, complete PKCE OAuth, understand Free versus Premium actions, and verify playback on an active Connect device.

Choose among Buzz Desktop, the ACP relay bridge, and Hermes’s native Buzz gateway while keeping identities and transports isolated.

Create a single-tenant Entra application for app-only Teams transcript access, grant least-privilege permissions, scope users, and rotate secrets safely.

Choose native configuration, plugins, or MCP by matching each integration to the boundary it actually needs.

A staged MCP adoption plan that starts with one bounded server, allowlists only necessary tools, and verifies the visible capability surface after every change.

Choose the right Hermes coordination boundary by matching A2A, in-process delegation, and durable Kanban work to the topology and lifetime of the job.

Enable only the A2A direction a workflow needs, separating the outbound toolset from the inbound gateway service and testing each surface independently.

Decide when an A2A peer deserves a named, reviewed configuration and when a one-off direct endpoint is acceptable for controlled discovery and testing.

Use A2A context identifiers deliberately so remote one-shot tasks and multi-turn peer conversations remain separate, traceable, and reviewable.

Choose one explicit A2A peer or fan a task out by advertised capability, with clear privacy, cost, and result-verification boundaries.

Select synchronous replies, SSE streaming, task polling, cancellation, or signed push notifications according to task duration and delivery reliability.