npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@adflz/planka-pms-mcp

v0.1.8

Published

GTD-inspired productivity system for AI agents — inbox capture, triage, scheduling, Pomodoro execution, and archival via Planka

Downloads

105

Readme

@adaofeliz/planka-pms-mcp

GTD-inspired MCP server for Planka boards. It gives AI agents a workflow-aware productivity layer: inbox capture, triage, scheduling, focused execution, stopwatch/Pomodoro tracking, done/archive handling, and overdue recovery suggestions.

This is intentionally semantic (workflow tools + board rules), not a raw Planka CRUD wrapper.

Prerequisites

  • Node.js 18+
  • npm
  • A running Planka instance with API key
  • A target board ID

Setup

npm install
cp .env.example .env

Fill .env values:

  • PLANKA_BASE_URL
  • PLANKA_API_KEY
  • PLANKA_BOARD_ID
  • optional: PLANKA_CONFIG_PATH (defaults to config/default.yaml)

Build once:

npm run build

Configuration

Main config is config/default.yaml.

  • connection: Planka URL/key/board ID (via ${ENV_VAR} interpolation)
  • board: list names, transitions, WIP limits, sort rules, due-date windows
  • labels / custom_fields: required triage metadata
  • tools.generate: dynamic workflow tools (e.g. triage_card, start_working)
  • cache: board skeleton TTL + optional startup preload

Running

MCP client configuration (npx)

Add to your MCP client config (Claude Desktop, Cursor, MCPHub, etc.):

{
  "mcpServers": {
    "planka-pms-mcp": {
      "command": "npx",
      "args": ["-y", "@adflz/[email protected]"],
      "env": {
        "PLANKA_BASE_URL": "https://your-planka-instance.com",
        "PLANKA_API_KEY": "your-api-key",
        "PLANKA_BOARD_ID": "your-board-id"
      }
    }
  }
}

stdio mode (default)

Use this for local development:

node dist/index.js

With MCP Inspector:

npx @modelcontextprotocol/inspector node dist/index.js

Streamable HTTP mode

node dist/index.js --http
node dist/index.js --http --port=8080

Endpoints:

  • MCP: http://localhost:<port>/mcp
  • Health: http://localhost:<port>/health

Available tools (18+ core)

Read

  • board_overview, list_cards, get_card, search_cards, daily_summary, overdue_check, search_archive

Write

  • create_card, update_card, move_card, complete_card, block_card, archive_card, manage_checklist, add_comment, sort_list

Workflow (generated from config)

  • triage_card, schedule_for_today, start_working, park_as_noise

Time tracking

  • stopwatch, pomodoro

Generated workflow tools

config/default.yaml drives generation of higher-level tools that compose core operations and enforce board semantics. Typical flow:

triage_cardschedule_for_todaystart_workingcomplete_cardarchive_card

Testing

  • Mocked/full suite (default):
npm test
  • Live smoke tests against a real Planka instance:
PLANKA_LIVE_TESTS=1 npm run test:live

Live tests are skipped unless PLANKA_LIVE_TESTS=1 is set.

License

MIT