Pinkroostermcp MCP Server

The first project management system built from scratch for AI coding agents — not a wrapper around Jira or Linear. That is what the pinkroostermcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The tools it exposes

The server publishes 14 tools. What each one is for:

• get_project_status — Compact status dashboard — counts, active/blocked items
• get_next_actions — Priority-ordered actionable items with enriched context (linked entity names, complexity)
• create_or_update_issue — Create or update issues with full field support
• create_or_update_feature_request — Create or update feature requests
• manage_user_stories — Add, update, or remove structured user stories on feature requests
• create_or_update_work_package — Create or update work packages
• scaffold_work_package — One-call creation of WP + phases + tasks + dependencies
• batch_update_task_states — Update multiple task states in one call with consolidated cascades
• verify_acceptance_criteria — Record verification results for phase acceptance criteria
• manage_dependency — Add/remove WP or task dependencies with auto-block (auto-detects from ID format)
• create_or_update_memory — Create or merge memory by name (append content, union tags)
• delete_memory — Permanently delete a project memory

What it needs from you

Configuration is passed through the environment: DATABASE_URL, MCP_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Docker and Docker Compose - Claude Code (recommended — make install auto-registers the MCP server) - .NET 9 SDK and Node.js 20+ (for local development only)

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

How it compares

Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Pinkroostermcp's toolset — get_project_status, get_next_actions, create_or_update_issue and 11 more — is a fair guide to whether it matches your workflow. It is maintained by pinkroosterai; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Pinkroostermcp's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Pinkroostermcp.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.