概要
What is ESA MCP Server?
ESA MCP Server is a Model Context Protocol (MCP) server that integrates with the esa.io API, built using Deno and published on JSR. It allows AI assistants to perform basic esa.io operations as MCP tools.
How to use ESA MCP Server?
Set environment variables ESA_TEAM_NAME and ESA_TOKEN in a .env file, then run deno run --allow-env --allow-net=api.esa.io --allow-read jsr:@masseater/esa-mcp-server. The server can also be configured as an MCP server in Cursor via .cursor/mcp.json.
Key features of ESA MCP Server
- Fetch user information from esa.io
- List, get, create, update, and delete articles
- Runs directly from JSR without cloning the repository
- Uses Deno runtime with explicit network permissions
Use cases of ESA MCP Server
- AI assistant reading and writing esa.io articles during a conversation
- Automating document management tasks via an MCP-compatible client like Cursor
- Integrating esa.io data into agent workflows without manual API calls
FAQ from ESA MCP Server
What are the runtime requirements?
Deno v2.0 or later and an internet connection are required.
How do I obtain an esa.io API token?
Go to your esa.io team page, click your avatar → Settings → Applications → Personal access tokens, generate a token with read, write, and read_user scopes.
What transport does the server use?
The server communicates over standard input/output (Stdio), outputting JSON-RPC ping messages while waiting for client connections.
Can I run the server locally for development?
Yes, clone the repository, copy .env.example to .env with your credentials, and run deno run --allow-env --allow-net --allow-read main.ts.
What permissions are required to run the server?
The command needs --allow-env for environment variables, --allow-net=api.esa.io for the esa.io API, and --allow-read for file/cache access.
