The five prompts are what separate this from a thin API wrapper — a standup brief or a priority-task action plan is a defined output rather than something you have to describe every time. The resource URIs matter too: a client can populate a site or user list without spending a tool call. The README walks through a four-step connection check, which is a good sign for a setup that involves an API key and a self-hosted server.
An MCP server for Implem.Pleasanter that goes past CRUD: alongside issue management it ships analysis tools, browsable resources for sites, users, groups and departments, and server-side prompts that turn raw project data into a status report or a standup brief.
- Issues created, searched, updated and deleted — `pleasanter_create_issue`, `pleasanter_get_issues`, `pleasanter_update_issue`, `pleasanter_delete_issue` — with `pleasanter_bulk_create_issues` for a batch
- Complex filtered search and search across several projects at once — `pleasanter_advanced_search`, `pleasanter_multi_site_search`
- Project trend analysis and a status summary — `pleasanter_trend_analysis`, `pleasanter_status_summary`
- Resources you can browse without a tool call — `pleasanter://sites`, `pleasanter://users`, `pleasanter://groups`, `pleasanter://depts`, plus per-site `issues`, `summary` and `status`
- Five server-side prompts — `project_status_report`, `issue_analysis`, `team_productivity_report`, `priority_task_identification`, `weekly_standup_preparation`
A Pleasanter server and an API key generated in your account settings, with API access enabled for that user. Set `PLEASANTER_BASE_URL` and `PLEASANTER_API_KEY`; optional `PLEASANTER_TIMEOUT`, `PLEASANTER_RETRIES` and `LOG_LEVEL` (set it to `debug` for verbose output). Clone, `npm install`, `npm run build`, then point the client at `dist/index.js` with `node` — on Windows the README documents running it through WSL. The server honours Pleasanter's rate limits with exponential backoff. Package `pleasanter-mcp-server` 1.0.0; the README is in Japanese.
