esa.io (BYOK) — connector documentation
- MCP endpoint:
https://byok-esa.connectorbay.com/mcp - REST API:
POST https://byok-esa.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-esa.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own esa.io esa personal access token (read scope is enough), sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-esa.connectorbay.com/health· Tool schemas:https://byok-esa.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-esa · agent@connectorbay.com
What esa.io (BYOK) is for
esa.io (BYOK) lets an AI assistant read your own esa.io data through the esa.io API with a key you supply (esa personal access token (read scope is enough)). Read-only: 10 tools (list_teams, get_team, get_team_stats, list_members, list_posts, get_post, list_post_comments, list_team_comments, list_tags, get_authenticated_user). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.esa.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by esa.io. esa.io and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
- "Which esa teams am I in?"
- "What is the esa team 'docs' about?"
- "How many posts and active users does the esa team 'docs' have?"
- "Who are the most active writers in the esa team 'docs'?"
- "Which esa posts in the 'docs' team were updated most recently?"
- "Show esa post number 1 in the 'docs' team."
What it does
list_teams: List the esa.io teams the token's owner belongs to, optionally only those where the owner is a member or an owner.get_team: Get one team: name, privacy (open or closed), description and URL.get_team_stats: Get a team's counts of members, posts (total, wip, shipped), comments and stars, plus daily, weekly and monthly active users.list_members: List a team's members with role, number of posts, join date and last access time (email addresses are not returned).list_posts: List or search a team's posts with title, category, tags, WIP flag, authors, dates and comment and star counts (no body text).get_post: Get one post including its Markdown body, tags, category, authors, revision number and backlink count.list_post_comments: List the comments on one post, newest update first, with Markdown body, author and star count.list_team_comments: List comments across the whole team, newest first.list_tags: List a team's tags with the number of posts carrying each, most used first.get_authenticated_user: Show the esa account the token belongs to: id, name, screen name and creation date (email is not returned).
BYOK key
You bring your own esa.io esa personal access token (read scope is enough) (https://docs.esa.io/posts/102). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.esa.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Data sources
- https://docs.esa.io/posts/102 (the API this connector calls, with a BYOK key)
Live from the esa.io API (api.esa.io) with a BYOK key; documentation: https://docs.esa.io/posts/102. Endpoints checked against that documentation on 2026-10-16.
What it is not
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by esa.io. esa.io and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your esa.io account.
Built for: Japan. Languages: Japanese.