Loading...
×Let Hermes Agent remember a server's earlier notices and rules, draft clear maintenance announcements through Tareno and flag contradictions, with every post approved in Tareno.
Yes. Hermes Agent keeps your server's rules and earlier notices in memory, drafts a maintenance announcement with times and affected services, flags anything that contradicts a previous notice and saves a draft for your Mastodon account through Tareno. It cannot read member replies, and scheduling stays pending until you approve it.
Last reviewed 2026-10-24 · Markdown version for AI agents
Running a Mastodon server means answering for it. Members want to know when the instance will be down, why uploads were slow on Tuesday and whether the rule on automated accounts has changed. Admins are volunteers, and the notices they post tend to be short, written at night and inconsistent with each other. Hermes Agent keeps context between sessions, which is what consistent notices need: it remembers what was announced, what the rules say and how the server speaks to its members. This page follows the admin of a small regional server through a maintenance window, with the time-zone discipline that prevents the most common mistake and the note that the admin remains the voice.
Imagine an admin who tells Hermes: database upgrade Saturday, about 40 minutes of downtime, starting at 22:00 server time. Hermes remembers that the previous notice, in March, promised that maintenance would never start after 21:00 and flags the conflict. She decides the exception is justified and asks Hermes to say so. Hermes drafts a post of 410 characters that gives the start in UTC and Berlin time, the affected services, the expected duration and the reason for the exception. It saves the draft with create_drafts for the server's account, and she approves a Thursday request.
Tell it the server's rules, how it speaks to members and the promises made in earlier notices. Hermes keeps this between sessions and updates it with each notice.
Send what is happening, when and for how long. Include the time zone, because ambiguity about it is the most common cause of confused members.
Hermes compares the plan with earlier promises and rules and lists contradictions. Decide whether to change the plan or to explain the exception.
Request a post that gives the start in UTC and in the members' main time zone, the services affected, the duration and where to follow progress. Count against your server's limit; Mastodon sets limits per server.
Hermes confirms the account with list_accounts and saves the draft through create_drafts. A server account is a shared voice, so check who has access.
Mastodon's documentation requires scheduled posts to be at least 5 minutes ahead. Give a day, a time and an IANA time zone, and approve the request in the Tareno dashboard.
Remember these server rules and promises: [rules, past maintenance promises]. Also remember that notices must state times in UTC and in Berlin time. Tell me what you have stored, and list any rule that conflicts with another.Maintenance plan: database upgrade this Saturday, about 40 minutes of downtime from 22:00 server time. Compare it with your stored promises and rules, list every conflict with the earlier notice it comes from, and suggest wording if I decide to make an exception.Write a Mastodon notice of up to 450 characters for Tareno announcing the upgrade: start in UTC and Berlin time, duration, affected services, the reason for the exception and where members can follow progress. Avoid jargon, and use one hashtag in capitalized words.Use Tareno to confirm the server account [@admin@server] and save the approved notice as a draft. After I confirm, ask for [Thursday 18:00] in the [Europe/Berlin] time zone and return the draft ID and the pending action ID.As configured in Tareno on 2026-10-24. The live rules for your own account come from the get_platform_schema tool.
Source: Mastodon documentation: statuses and instance configuration, read on 2026-10-24. Platform rules change; check the page before you rely on a number.
https://tareno.co/api/mcpUse the same Tareno account across supported clients. Open the relevant setup guide for authentication, first use, reconnect, and revocation.
list_accountsChecked:
From what you told it. Tareno does not read posts on Mastodon, so give Hermes each notice as you send it, and ask it to list what it has stored before drafting a new one.
Because members live in different zones and because an unlabelled time is the commonest source of confusion. Hermes adds both by default if you tell it your members' main zone.
Mastodon's documentation requires scheduled posts to be at least 5 minutes ahead. Ask for the earliest allowed time and approve the request in the dashboard; plan for that lead rather than for instant posting.
Only what you tell it. Mastodon limits are set per server, with 500 as the documentation's example, so state yours and ask Hermes to count each notice against it.
Only people who will approve notices. A server account speaks for all admins, so keep a clear approval trail, which Tareno's pending actions provide for every scheduled post.
No. A scheduling request is a pending action in Tareno, and Mastodon receives the post only after you approve it in the dashboard. `get_action_status` shows what happened afterwards.