create_post
Create a new post in the esa team. Requires a title and optionally accepts content, tags, category, WIP status, and other metadata. Returns the created post information including the assigned post number and URL.
LABSCO SUMMARY
The delete tools carry no guard rail — delete_post and delete_comment both state the removal is permanent and cannot be recovered.
That is worth an approval step before handing this to an agent whose job is tidying. Elsewhere it maps esa's model cleanly: wip is a first-class parameter on create_post and update_post so a draft stays a draft, and update_post takes a message so the revision history stays legible to whoever reads it next. One shape to know before wiring a search loop: get_posts truncates body_md, so get_post is the call that actually returns a post's full text.
What it is
An esa client covering posts and their comment threads: search, read, create, update and delete posts, and add, edit or remove the comments on them.
What you get
- Post search that carries its metadata: get_posts takes a q query with sort, order and pagination and returns title, content, tags, categories, author and engagement metrics including comments, stars and watches, with an include parameter that pulls comments and stargazers and supports nested inclusion such as 'comments,comments.stargazers'.
- A complete read by number: get_post returns a post's markdown body, tags, category, author, revision history and engagement metrics for a post_number.
- Writing in esa's own model: create_post takes name, body_md, category, tags, a wip flag, a change message and an optional template_post_id, returning the assigned post number and URL; update_post writes the same fields against an existing post_number.
- Comment threads as their own surface: get_post_comments pages through a post's comments with author, timestamps and stars, create_post_comment adds one in Markdown, update_comment rewrites one by comment_id, and delete_comment removes it.
- get_tags returns every tag in use with the number of posts attached, sorted by post count descending, and delete_post removes a post by its number.
Requirements
An esa team and a token that can act on it: ESA_TEAM names the team, ESA_ACCESS_TOKEN authorises the calls.
Setup effort
One command plus a key — npx -y @koki-develop/esa-mcp-server@latest, then supply credentials
USE CASES
01
Writing up what you just worked out
Create the post from the session you are already in, tag it so it lands in the right category, and edit it as the picture firms up.
02
Finding the post someone half-remembers
Search the team's posts and open the one that matches, without leaving the client.
03
Answering in a thread without opening the browser
Read the comments on a post, reply to them, and correct your own reply if you got it wrong.
10 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_post_comment
Create a new comment on an existing post in the esa team. Requires a post number and comment content in Markdown format. Returns the created comment information including ID, content, timestamps, and author details.
delete_comment
Delete an existing comment from the esa team. Requires a comment ID. The comment will be permanently deleted and cannot be recovered.
delete_post
Delete an existing post from the esa team. Requires a post number. The post will be permanently deleted and cannot be recovered.
get_post
Retrieve a specific post from the esa team by post number. Returns complete post details including title, content (markdown), tags, category, author information, revision history, and engagement metrics. Optionally includes comments and stargazers. Supports nested inclusion like 'comments,comments.stargazers'.
get_post_comments
Retrieve a list of comments for a specific post from the esa team. Requires a post number and supports pagination. Returns comment metadata including content, author information, timestamps, and engagement metrics (stars).
get_posts
Retrieve a list of posts from the esa team. Supports search queries, filtering, sorting, and pagination. Returns post metadata including title, content, tags, categories, author information, and engagement metrics (comments, stars, watches). Optionally includes comments and stargazers with the include parameter. Supports nested inclusion like 'comments,comments.stargazers'. Note: body_md is truncated to 300 characters with body_truncated field indicating if truncation occurred.
get_tags
Get a list of all tags used in the esa team. Returns tags with their names and the number of posts they are attached to, sorted by post count in descending order. Supports pagination.
update_comment
Update an existing comment on a post in the esa team. Requires a comment ID and new content in Markdown format. Returns the updated comment information including content, timestamps, and author details.
update_post
Update an existing post in the esa team. Requires a post number and optionally accepts updated content, tags, category, WIP status, and other metadata. Returns the updated post information.
BEFORE YOU INSTALL
What to know first
Tools you get
10 tools when we connected. With --readonly only get_posts, get_post, get_tags and get_post_comments remain. delete_post and delete_comment delete permanently.
Requires
- npx on PATH
- ESA_TEAM in your environment
- ESA_ACCESS_TOKEN in your environment
Where it runs
All 4 documented setups run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 10 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @koki-develop/esa-mcp-server@latestMCP Clients
Any MCP client — npx
ANY MCP CLIENT — NPX · JSON
{
"mcpServers": {
"esa": {
"command": "npx",
"args": [
"-y",
"@koki-develop/esa-mcp-server@latest"
],
"env": {
"ESA_TEAM": "<YOUR_ESA_TEAM>",
"ESA_ACCESS_TOKEN": "<YOUR_ESA_ACCESS_TOKEN>"
}
}
}
}Any MCP client — Docker
ANY MCP CLIENT — DOCKER · JSON
{
"mcpServers": {
"esa": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"ESA_TEAM",
"-e",
"ESA_ACCESS_TOKEN",
"ghcr.io/koki-develop/esa-mcp-server:latest"
],
"env": {
"ESA_TEAM": "<YOUR_ESA_TEAM>",
"ESA_ACCESS_TOKEN": "<YOUR_ESA_ACCESS_TOKEN>"
}
}
}
}Any MCP client — npx, read-only
ANY MCP CLIENT — NPX, READ-ONLY · JSON
{
"mcpServers": {
"esa": {
"command": "npx",
"args": [
"-y",
"@koki-develop/esa-mcp-server@latest",
"--readonly"
],
"env": {
"ESA_TEAM": "<YOUR_ESA_TEAM>",
"ESA_ACCESS_TOKEN": "<YOUR_ESA_ACCESS_TOKEN>"
}
}
}
}Any MCP client — Docker, read-only
ANY MCP CLIENT — DOCKER, READ-ONLY · JSON
{
"mcpServers": {
"esa": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"ESA_TEAM",
"-e",
"ESA_ACCESS_TOKEN",
"ghcr.io/koki-develop/esa-mcp-server:latest",
"--readonly"
],
"env": {
"ESA_TEAM": "<YOUR_ESA_TEAM>",
"ESA_ACCESS_TOKEN": "<YOUR_ESA_ACCESS_TOKEN>"
}
}
}
}
