Esa Mcp Server
Read and manage esa.io team notes and documentation from your agent using team name and personal access token.
Overview
esa MCP Server is a MCP server for the Build phase that lets agents interact with your esa.io team knowledge base via stdio.
What is this MCP server?
- Official-style MCP bridge for esa.io knowledge base
- npm package @koki-develop/esa-mcp-server v0.3.2 stdio
- Requires ESA_TEAM and ESA_ACCESS_TOKEN environment variables
- Personal access token marked secret in server metadata
- GitHub-hosted server for koki-develop/esa-mcp-server
- Server version 0.3.2 per published schema
- Two required env vars: ESA_TEAM and ESA_ACCESS_TOKEN
- npm identifier @koki-develop/esa-mcp-server
Community signal: 2 GitHub stars.
What problem does it solve?
Your specs live on esa.io but your agent cannot see them unless you manually dump pages into every prompt.
Who is it for?
Solo or two-person teams already on esa.io who want Claude Code or Cursor to reference and update team docs during build.
Skip if: Builders on other wikis only, or teams that cannot issue esa personal access tokens.
What do I get? / Deliverables
Agents pull and work against esa.io content in context so docs and code stay aligned without constant copy-paste.
- Agent-accessible esa.io pages and team-scoped knowledge operations
- Less context switching between wiki and IDE during implementation
- Document updates synchronized through MCP instead of manual paste
Recommended MCP Servers
Journey fit
While building, solo and tiny teams centralize specs and runbooks on esa.io—MCP access keeps docs in the same loop as code generation. Docs subphase is where wikis, ADRs, and handoff notes live; esa is explicitly a knowledge-base surface for that work.
How it compares
esa.io integration MCP, not a standalone note-taking skill or generic web scraper.
Common Questions / FAQ
Who is esa MCP Server for?
It is for developers using esa.io as a team wiki who want MCP agents to read and manage esa content with proper API credentials.
When should I use esa MCP Server?
Use it during build and docs upkeep when specs, runbooks, or meeting notes on esa should drive or receive agent edits alongside code.
How do I add esa MCP Server to my agent?
Install @koki-develop/esa-mcp-server, set ESA_TEAM and ESA_ACCESS_TOKEN in your MCP env, and register the stdio server in Claude Code, Cursor, or your client.