pleasanter

This Pleasanter MCP server exposes a set of tools to manage Pleasanter projects, issues, and analytics through the MCP interface. Core capabilities include creating, reading, updating, and deleting issues; performing advanced searches across projects; conducting trend analysis and project status summaries; and performing bulk operations on multiple issues. Resources available through the MCP layer cover Pleasanter sites, users, groups, departments, and real-time project and issue data. Prompts help generate automated project health reports, issue analyses with recommendations, team productivity insights, priority task identification with action plans, and weekly stand-up preparation. To use these tools, configure the MCP server as described in the installation steps, ensure your Pleasanter API key and base URL are set, and call the available commands (e.g., pleasanter_create_issue, pleasanter_get_issues, pleasanter_advanced_search, pleasanter_trend_analysis) as needed. Claude Desktop or other MCP clients can connect to the pleasanter:// style resources (sites, users, groups, depts, and site-specific endpoints).

Prerequisites:\n- Node.js 18.0.0 or higher (recommended 24.x LTS)\n- npm or yarn\n- Access and API key to a Pleasanter server\n\nInstallation steps:\n1) Clone or download the server code for Pleasanter MCP:\n git clone <repository-url> pleasanter-mcp-server\n cd pleasanter-mcp-server\n\n2) Install dependencies:\n npm install\n\n3) Build the server:\n npm run build\n\n4) Configure environment variables:\n cp .env.example .env\n Edit .env to set:\n - PLEASANTER_BASE_URL (Pleasanter server URL)\n - PLEASANTER_API_KEY (Pleasanter API key)\n Optional: adjust PLEASANTER_TIMEOUT, PLEASANTER_RETRIES, LOG_LEVEL.\n\n5) Run in development or production mode:\n npm run dev # for development with hot-reload\n npm run build && node dist/index.js # for production-like run\n\n6) Verify MCP is reachable and functioning via configured client (Claude Desktop, etc.).

Tips and common considerations:\n- Ensure PLEASANTER_BASE_URL uses the correct protocol (HTTPS in production) and is reachable from the MCP server.\n- Keep API keys secure and rotate regularly.\n- The MCP server supports environment-based configuration; use LOG_LEVEL=debug for troubleshooting.\n- If you connect via Claude Desktop, configure the mcpServers entry with the correct command and path to dist/index.js, and pass necessary environment variables.\n- When using Windows/WSL or WSL2, ensure the path to the Node.js runtime and the MCP dist/index.js is correctly referenced, and account for path escaping in JSON.\n- If you encounter authentication or rate-limit issues, double-check the Pleasanter API key validity and ensure you respect Pleasanter’s usage limits.\n- For production deployments, consider running behind a process manager (e.g., PM2) and enabling proper logging and error monitoring.