esa_append_post and esa_prepend_post write a new revision from the content alone, which makes a daily log or a meeting record a single call rather than a fetch-modify-replace cycle, and esa_rollback_post_revision means a bad write is a revision number away from being undone. Two of the 28 tools return esa's own search and Markdown grammar, so a complex query is built from the documented syntax rather than guessed at.
An esa.io client of 28 tools covering teams and their statistics, posts and revisions, comments, categories and tags, and the search and Markdown references the model can consult before writing a query.
- The post lifecycle: create with tags, category and WIP status, update, ship by clearing WIP, archive into Archived/, duplicate into the same or another team, and roll back to a numbered revision
- Append and prepend Markdown to an existing post, each saved as a new revision, without fetching the current body first
- Search over a team's posts, plus a help tool that returns esa's query syntax for date ranges and the rest before the query is built
- Backlinks: the count carried on every post, and the list of posts referencing it, with archived and WIP posts excluded
- Comments read singly, listed per post or per team, and created, updated or deleted
- Category structure — top-level categories, one category path with its subcategories, and every path with post counts for cleanup or migration planning
- Team context: members with roles, tags with post counts, and statistics covering total, WIP and shipped posts, comments, stars, watches and active users
An esa access token and the team name that nearly every call takes. npx on your PATH.
One command plus a key — npx @esaio/esa-mcp-server, then supply credentials