All plugins

agentplaybooks-tools

Connect AgentPlaybooks skills and hosted MCP/OpenAPI tools to Hermes, with guided setup, profile selection, permission diagnostics and an authenticated MCP check. Requires Node.js 20+ and @agentplaybooks/cli@0.10.0; the CLI is installed separately. Disclosure — skill-only; the separately installed apb CLI does the work. `apb hermes setup --apply` restores complete skill trees into the chosen project and edits the selected Hermes profile's config.yaml to register those skills and a local stdio relay for the hosted playbook MCP endpoint. The relay is a child process that forwards actual requests, answers MCP pings locally and sends no idle HTTP keepalives; existing HTTP configurations need an explicit migration. Local writes require --apply; setup also probes MCP initialization and tool listing using a scoped key from the process environment, without invoking tools. `doctor` checks profile credential variable names without exposing their values. Hosted operations contact agentplaybooks.ai (or an explicitly configured service); skill restore uses `apb login`, and `apb push --apply` uploads project configuration (secret references, not values).

matebenyovszky11Toolsv0.2.1Updated 14 hours ago

About

Connect AgentPlaybooks skills and hosted MCP/OpenAPI tools to Hermes, with guided setup, profile selection, permission diagnostics and an authenticated MCP check. Requires Node.js 20+ and @agentplaybooks/cli@0.10.0; the CLI is installed separately. Disclosure — skill-only; the separately installed apb CLI does the work. `apb hermes setup --apply` restores complete skill trees into the chosen project and edits the selected Hermes profile's config.yaml to register those skills and a local stdio relay for the hosted playbook MCP endpoint. The relay is a child process that forwards actual requests, answers MCP pings locally and sends no idle HTTP keepalives; existing HTTP configurations need an explicit migration. Local writes require --apply; setup also probes MCP initialization and tool listing using a scoped key from the process environment, without invoking tools. `doctor` checks profile credential variable names without exposing their values. Hosted operations contact agentplaybooks.ai (or an explicitly configured service); skill restore uses `apb login`, and `apb push --apply` uploads project configuration (secret references, not values).

AgentPlaybooks Tools for Hermes

AgentPlaybooks Tools for Hermes

This Agent Plugins package installs the agentplaybooks-tools Hermes skill. It
guides setup of AgentPlaybooks skills, MCP servers, and federated OpenAPI tools
in the selected Hermes profile, including the authentication those connections
need.

The package itself does not copy credentials, edit configuration in the
background, or register tools. It guides you through the AgentPlaybooks CLI and
Hermes profile setup. Review each plan before applying it.

Install

hermes plugins install matebenyovszky/agentplaybooks/packages/hermes-portable/agentplaybooks-tools --no-enable
hermes plugins enable agentplaybooks-tools
npm install -g @agentplaybooks/cli@0.10.0
apb --version

Hermes needs Node.js 20 or newer to run the CLI. Install the CLI separately;
installing this skill does not install npm packages or require a hosted account.
For a remote Hermes gateway, Node.js and apb must be available on the gateway
host/container, and commands must target the profile that runs there. Installing
the skill into a remote profile does not install the CLI on your Mac or gateway.

Guided setup (CLI 0.8.0)

Run these commands on the gateway host/container, in the project directory.
--profile=work selects a named profile beneath the installation home;
--hermes-home=/path selects the installation home explicitly. Use the same
selection for setup, connect, memory setup and diagnostics.

apb login
apb hermes setup <playbook-guid> . --profile=work
apb hermes setup <playbook-guid> . --profile=work --apply
apb hermes doctor <playbook-guid> . --profile=work --check

The preview checks Node.js, Hermes, destination permissions and credential
presence, then lists the playbook files to restore and the profile config to
merge. Restore includes complete skill trees and their bundled resources. Hosted
MCP/OpenAPI definitions stay behind the playbook's single MCP endpoint. Existing conflicts
stop the whole setup. Hosted tools use a single playbook MCP connection; upstream
service keys remain in the AgentPlaybooks vault.

The default connection references APBKS_KEY_AGENTPLAYBOOKS. Configure a
playbook-scoped key in the selected profile's secret environment; apb login
separately authenticates skill downloads with your account key. --tools-only
skips file restoration and account login. Keys are never copied into config.

--apply verifies MCP initialization and tool listing using this process's
key environment, without invoking any tool. A missing/rejected key gives exit
code 2 even if the files were installed: configure the key, restart the gateway
and rerun doctor --check from that environment. A variable declared in the
profile's .env is reported separately; it does not prove the running gateway
loaded it. doctor without --check makes no network calls.

Connect playbook tools to Hermes

To let Hermes call a hosted playbook's MCP tools, including its federated
MCP/OpenAPI services, preview a playbook-scoped connection:

apb login
apb connect <playbook-guid> --target=hermes

After reviewing the plan, apply it:

apb connect <playbook-guid> --target=hermes --apply

The plan reports which key environment variable the connection expects. Set a
playbook-scoped API key in the selected Hermes profile's secret environment.
For an account-wide connection, use apb connect --account --target=hermes
instead and set AGENTPLAYBOOKS_API_KEY.

To install a private playbook's skills into the local project, separately preview
and apply apb pull <playbook-guid> . followed by
apb sync . --target=hermes. The pull restores the skills; sync registers them
in Hermes's profile. Public skills can also be installed directly from a
playbook's /.well-known/skills/ URL.

Authentication and secrets

  • apb login authenticates the CLI to AgentPlaybooks with a user API key. The
    key is stored in the CLI credential store, not in a skill or playbook file.
  • apb connect --account --target=hermes configures the account MCP connection.
    It refers to AGENTPLAYBOOKS_API_KEY; configure that secret in the environment
    used by the selected Hermes profile and restart Hermes if needed. An account
    key can reach account-wide tools, so prefer a scoped connection when it covers
    the required workflow.
  • apb connect <playbook-guid> --target=hermes configures a single playbook
    connection. Its plan shows the environment variable name (by default
    APBKS_KEY_AGENTPLAYBOOKS). Use a playbook-scoped key with only the
    permissions the connection needs, and set it in Hermes's profile secret store
    or environment, never in config.yaml, mcp.json, or the skill.
  • Federated MCP and OpenAPI credentials belong in the AgentPlaybooks vault.
    Hermes can call the playbook's tools without putting those upstream secret
    values in the Hermes configuration.

Use apb sync to register skills and merge MCP definitions already present in
the local playbook project into Hermes. Review its plan before applying it.

Safety

apb sync, apb pull, and apb connect show a plan and make no local changes
without --apply. apb pull --apply and apb sync --apply write to the
selected Hermes profile. apb push --apply uploads the reviewed project
configuration to AgentPlaybooks. Secret values are never included in that
upload.

See the CLI guide
and Hermes integration guide
for details.

MIT licensed; see LICENSE.

Hermes connections without idle HTTP traffic

CLI 0.8.1 creates Hermes connections through apb mcp stdio. Hermes communicates
with this local process over stdin/stdout; the relay contacts the AgentPlaybooks
JSON MCP endpoint only for actual requests. Local ping requests never reach
the hosted server. There is no network keepalive, polling or automatic retry.
Keys come from the selected profile's environment, never command arguments.

Existing direct HTTP entries are reported as conflicts, not silently replaced.
To migrate, back up the profile configuration and replace only the chosen entry
with the reviewed stdio definition from apb connect --target=hermes. Keep its
credential variable and endpoint. Restart the gateway/dashboard after migration.
Do not set HTTP keepalive_interval: 0: Hermes 0.22.5 clamps that to five seconds.

README from the reviewed commit b0b9bcc; it updates when the author re-pins.

More by matebenyovszky

2 plugins by matebenyovszky in the catalog.

matebenyovszkyagentplaybooks-memoryPrivate AgentPlaybooks memory for Hermes: explicit recall by default, optional bounded automatic recall, native memory-write mirroring, archive and history. Registration, initialization, unused prefetch and profile switching make no network requests. Disclosure — explicit searches and opted-in automatic recall send query keywords to the configured AgentPlaybooks service for your personal and configured team sources; explicit native memory writes are mirrored there. Automatic recall has acknowledgement filtering, brief repeated-query suppression, a request/time budget and per-source failure cooldown. Defaults to agentplaybooks.ai over HTTPS; localhost HTTP is supported, and remote intranet HTTP requires an explicit opt-in that sends the API key unencrypted. Team and shared playbooks are configured explicitly: the agent can write, archive and permanently delete entries in configured team playbooks (shared playbooks are read-only), and teammates' entries are recalled into context.Communitymemory11

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section