pleasanter_create_issueLABSCO SUMMARY
Ships the reports, not just the data.
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.
What it is
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.
What you get
- Issues created, searched, updated and deleted —
pleasanter_create_issue,pleasanter_get_issues,pleasanter_update_issue,pleasanter_delete_issue— withpleasanter_bulk_create_issuesfor 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-siteissues,summaryandstatus - Five server-side prompts —
project_status_report,issue_analysis,team_productivity_report,priority_task_identification,weekly_standup_preparation
Requirements
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.
Setup effort
Build from source — git clone https://github.com/Takashi-Matsumura/pleasanter-mcp-server.git
USE CASES
Writing the weekly status update
Run the project status report prompt against the site and get a health report instead of assembling one from issue lists.
Finding what is urgent across several projects
Search across sites at once, then let the priority-task prompt turn the result into an action plan.
Loading a plan into the tracker
Create the issues in one bulk call rather than one request per item.
Seeing whether a project is drifting
Run trend analysis and the status summary together to get direction as well as a snapshot.
9 tools
Listed in project docs. Your client may show a different list.
pleasanter_get_issuespleasanter_update_issuepleasanter_delete_issuepleasanter_bulk_create_issuespleasanter_advanced_searchpleasanter_multi_site_searchpleasanter_trend_analysispleasanter_status_summaryBEFORE YOU INSTALL
What to know first
Tools you get
9 tools named in the project's documentation.
Requires
- Node.js 18.0.0 or later (24.x LTS recommended)
- PLEASANTER_API_KEY in your environment
Where it runs
Both documented setups run the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
git clone https://github.com/Takashi-Matsumura/pleasanter-mcp-server.git
cd pleasanter-mcp-server
npm install
npm run buildMCP Clients
Claude Desktop — macOS / Linux
{
"mcpServers": {
"pleasanter": {
"command": "node",
"args": [
"<YOUR_PATH_TO_PLEASANTER_MCP_SERVER>/dist/index.js"
],
"env": {
"PLEASANTER_BASE_URL": "<YOUR_PLEASANTER_BASE_URL>",
"PLEASANTER_API_KEY": "<YOUR_PLEASANTER_API_KEY>"
}
}
}
}Claude Desktop — WSL
{
"mcpServers": {
"pleasanter": {
"command": "wsl",
"args": [
"node",
"/home/ubuntu/github/Implem.Pleasanter/pleasanter-mcp-server/dist/index.js"
],
"env": {
"PLEASANTER_BASE_URL": "http://10.255.20.80:50001",
"PLEASANTER_API_KEY": "<YOUR_PLEASANTER_API_KEY>",
"PLEASANTER_TIMEOUT": "30000",
"PLEASANTER_RETRIES": "3",
"LOG_LEVEL": "info"
}
}
}
}The path and PLEASANTER_BASE_URL in this block are the author's own setup — a WSL checkout under /home/ubuntu/github/Implem.Pleasanter/ and an address on the author's network. Put the path of your own clone inside WSL and your own Pleasanter server URL.