esa MCP Server

What is esa MCP Server?

This server is an interface that uses the Model Context Protocol (MCP) to enable Claude AI to interact with the esa API. It allows Claude AI to search, create, and update esa documents, streamlining document management for esa teams.

How to use esa MCP Server?

Install the server globally via npm install -g @kajirita2002/esa-mcp-server or run directly with npx @kajirita2002/esa-mcp-server. Set the environment variables ESA_ACCESS_TOKEN (your esa API access token) and ESA_TEAM (your team name), then start the server with npm start. Add the server to your mcp_config.json using the provided configuration example.

Key features of esa MCP Server

• List, get, create, and update esa posts
• List, get, and create comments on posts
• Retrieve team member information
• Supports search queries and filtering options
• Markdown body support for posts and comments
• WIP (Work In Progress) flag management

Use cases of esa MCP Server

• Create a new esa post with a title, body, tags, and category via Claude AI
• Search and retrieve existing esa posts using queries and filters
• Update or edit post content and metadata directly from a chat
• Manage comments on posts, including adding new comments or reading existing ones
• Look up team members and their details

FAQ from esa MCP Server

What are the prerequisites for esa MCP Server?

Node.js 18 or higher, an esa API access token, and your esa team name.

How do I install and configure esa MCP Server?

Install globally with npm or use npx. Set ESA_ACCESS_TOKEN and ESA_TEAM environment variables, then add the server configuration to your mcp_config.json file.

What tools does esa MCP Server provide?

It provides three groups of tools: post-related (list, get, create, update), comment-related (list, get, create), and member-related (get members, get a specific member). Each tool has configurable input parameters.

What should I do if I see a 401 or 403 error?

A 401 error means your access token may be invalid or expired—generate a new one from the esa settings. A 403 error means the token lacks required permissions—check its permissions and issue a new token if needed.