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

@kitsy/coop-mcp

v2.3.0

Published

MCP server for COOP.

Readme

@kitsy/coop-mcp

MCP server for COOP.

This package exposes local COOP workspace state and operations to MCP-compatible clients over stdio.

Exposed Tools

  • coop_workspace_info()
  • coop_list_tasks(filters?)
  • coop_show_task(id)
  • coop_graph_next(track?)
  • coop_plan_delivery(name)
  • coop_transition_task(id, status)
  • coop_create_task(fields)

Exposed Resources

  • coop://workspace
  • coop://tasks
  • coop://tasks/{id}
  • coop://deliveries
  • coop://graph

Local Usage

From the repo root:

pnpm --filter @kitsy/coop-mcp build
node packages/mcp/dist/index.js --repo C:/path/to/your/repo

Or, after installation/build:

coop-mcp --repo C:/path/to/your/repo
coop-mcp --repo C:/path/to/your/repo --project webapp

If --repo is omitted, the server resolves the nearest parent directory containing .coop/. If the workspace contains multiple COOP projects, pass --project <id> or set the workspace current project first.

Claude Code Setup

Example MCP configuration:

{
  "mcpServers": {
    "coop": {
      "command": "node",
      "args": [
        "C:/Users/pkvsi/Wks/kitsy/coop/packages/mcp/dist/index.js",
        "--repo",
        "C:/path/to/your/workspace"
      ]
    }
  }
}

If you prefer pnpm during local development:

{
  "mcpServers": {
    "coop": {
      "command": "pnpm",
      "args": [
        "--dir",
        "C:/Users/pkvsi/Wks/kitsy/coop",
        "--filter",
        "@kitsy/coop-mcp",
        "exec",
        "coop-mcp",
        "--repo",
        "C:/path/to/your/workspace"
      ]
    }
  }
}

Other MCP-Compatible Tools

Any MCP client that supports stdio transports can launch this server with the same command/args pattern.

Notes

  • The server reads and writes the local .coop/ workspace directly.
  • Tool mutations go through shared core rules for task writing, planning, and state transitions.
  • Workspace identity is exposed from the active project's .coop/projects/<project.id>/config.yml -> project block for orchestrators and multi-repo agents.
  • This phase intentionally keeps transport simple: local stdio, no remote hosting, no auth layer.