esa MCP Server

Created By
kajirita2002a year ago
MCP server for interacting with esa API
Overview

What is esa MCP Server?

The esa MCP Server is an interface that utilizes the Model Context Protocol (MCP) to enable Claude AI to interact with the esa API, allowing for efficient document management operations.

How to use esa MCP Server?

To use the esa MCP Server, install it via npm, set the required environment variables for the esa API access token and team name, and start the server. You can then use Claude AI to perform various operations on esa documents.

Key features of esa MCP Server?

  • Integration with Claude AI for document management.
  • Tools for listing, creating, updating, and retrieving posts and comments.
  • Easy setup with Node.js and environment variable configuration.

Use cases of esa MCP Server?

  1. Automating document creation and updates in esa.
  2. Facilitating team collaboration through comments and post management.
  3. Streamlining workflows by integrating AI capabilities with document management.

FAQ from esa MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol that allows AI models to interact with external APIs in a structured manner.

  • Do I need an esa API access token?

Yes, an access token is required to authenticate and interact with the esa API.

  • Is there a specific Node.js version required?

Yes, Node.js version 18 or higher is required to run the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kajirita2002
Star
3
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago