MCP server for MonkeyPlanner, a project planning and issue tracking application with board management, issue lifecycle workflows, and real-time collaboration features
MonkeyPlanner has 13 well-named tools with clear verb-noun patterns (get_, list_, create_, approve_, claim_, submit_, complete_, reject_, add_, update_, search_). All tools have descriptions (10 - 200 chars, within baseline 194 avg). Input schemas are present and typed for all tools. However, parameter descriptions are minimal or missing for several tools, and output schemas are not documented. Error handling is basic, no recovery guidance or actionable error messages visible in the code. The server follows a consistent naming convention and covers a coherent workflow (issue lifecycle), but lacks depth in parameter documentation and output structure guidance.
Add a comment to an issue
Approve a pending issue (moves from Pending to Approved)
Claim an approved issue and move it to InProgress
Complete a QA-reviewed issue (moves from QA to Done). Optionally add a completion summary as a comment.
Create a new issue on a board
Get full issue detail including instructions, criteria, and comments
Get the MCP server version. Use this to check if the server needs a restart after an update.
Output schemas not documented. Tools return JSON responses but LLMs cannot infer field structure, types, or required fields. Forces agents to guess at response shape and risks extraction errors.
Parameter descriptions are minimal or generic. 'Filter by status' lacks enum values; 'Issue ID' lacks format guidance. LLMs cannot validate inputs without explicit constraints.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 65 | 2026-07-28+ | v2 |
List all boards
List issues. Filter by boardId and/or status (Pending, Approved, InProgress, QA, Done, Rejected)
Reject a QA issue back to InProgress with a required reason (moves from QA to InProgress)
Search issues by title (case-insensitive substring match)
Submit an in-progress issue for QA review (moves from InProgress to QA)
Check or uncheck a success criterion on an issue
No error recovery guidance. Code shows basic error returns (e.g., 'issueId and body are required') but no actionable next steps for LLMs. Missing pattern: recovery-guide.
list_boards and list_issues lack pagination parameters (limit, offset, cursor). Large result sets will blow context windows. No documented result limits.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Agents cannot distinguish safe reads from destructive writes without reading descriptions.