ESA MCP Server

What is ESA MCP Server?

ESA MCP Server is a Model Context Protocol server that provides access to the esa API. It enables AI assistants to interact with esa, a Japanese team documentation and wiki service, by offering tools to manage posts, comments, members, tags, and other team data.

How to use ESA MCP Server?

Install dependencies with bundle install. Obtain an esa personal access token from the user settings page. Set the access token and team name as environment variables, then configure the server in your MCP client’s settings file (e.g., claude_desktop_config.json or cline_mcp_settings.json) with the command ruby /path/to/esa_mcp_server.rb.

Key features of ESA MCP Server

• Retrieve team information
• List, get, create, and update posts
• List and create comments
• Get team statistics
• List members and tags
• Get authenticated user info
• Access category information as a resource

Use cases of ESA MCP Server

• Automate posting or updating documentation in esa from an AI assistant
• Search and retrieve specific articles using queries, categories, or tags
• Monitor team statistics and member lists programmatically
• Manage comments on esa posts without using the web interface

FAQ from ESA MCP Server

What dependencies are required?

Ruby and the gems installed via bundle install are required.

How do I get an esa access token?

Log in to esa, go to the user settings page (https://[team].esa.io/user/applications), create a personal access token with read/write scope, and copy the generated token.

Where should I configure the MCP server?

In your Cline MCP configuration file: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS), %APPDATA%\Claude\claude_desktop_config.json (Windows), ~/.config/Claude/claude_desktop_config.json (Linux), or the VSCode extension path.

What authentication method does it use?

It uses a personal access token set as an environment variable along with the team name.

What transport protocol does the server use?

The README does not specify the transport protocol explicitly; it relies on standard MCP configuration through command and args.