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

rhythmic-mcp

v0.5.0

Published

MCP server for Rhythmic — exposes your spatial project board to coding agents (Claude Code, Cursor, Claude Desktop) as typed tools.

Readme

rhythmic-mcp

An MCP server that exposes Rhythmic to coding agents (Claude Code, Cursor, Claude Desktop, …) as typed tools. It's a thin wrapper over the authenticated /api/v1 HTTP API — all auth, tenant-scoping, and validation live there.

Rhythmic is in free public beta.

Quick start

  1. In Rhythmic, open Settings → API keys and create a key (the secret is shown once).
  2. Register the server with your agent using npx — no install or build step needed.

The key can be passed as a --api-key flag (recommended for mcpServers JSON) or via the RHYTHMIC_API_KEY environment variable. A flag wins over the env var.

Claude Desktop / Cursor (mcpServers JSON)

{
  "mcpServers": {
    "rhythmic": {
      "command": "npx",
      "args": ["-y", "rhythmic-mcp", "--api-key", "rhy_xxxxx"]
    }
  }
}

Claude Code

claude mcp add rhythmic -- npx -y rhythmic-mcp --api-key rhy_xxxxx

Or keep the key out of the command with an env var:

claude mcp add rhythmic -e RHYTHMIC_API_KEY=rhy_xxxxx -- npx -y rhythmic-mcp

Configuration

| Flag | Env var | Default | | |------|---------|---------|--| | --api-key, -k | RHYTHMIC_API_KEY | — | API key from Settings → API keys (required) | | --url, --api-url | RHYTHMIC_API_URL | https://rhythmicapp.dev | Rhythmic base URL | | --help, -h | | | Print usage | | --version, -v | | | Print version |

Pointing at a local dev server? Use --url http://localhost:3000.

Local development

From the monorepo, run against src without building:

pnpm --filter rhythmic-mcp dev -- --api-key rhy_xxxxx --url http://localhost:3000

Or build and run the compiled output:

pnpm --filter rhythmic-mcp build
node packages/mcp/dist/index.js --api-key rhy_xxxxx --url http://localhost:3000

Tools

| Tool | Description | |------|-------------| | list_projects | List projects in the workspace | | get_project | Project (by key) + its cycles | | create_project | Create a project (key derived from the name) | | update_project | Update a project's name/color/context | | list_issues | Issues, filtered by project/status/assignee/cycle (paginated) | | get_issue | Full issue detail incl. comments + dependency edges | | create_issue | Create an issue | | update_issue | Update status/priority/title/description/assignee/cycle + tested/verified flags | | comment_issue | Comment on an issue (as the key's user) | | add_commit | Attach a git commit (branch/hash badge on the card) | | link_pr | Link a pull request (PR# badge on the card) | | set_work_status | Toggle the live "agent is working" spinner on an issue | | link_issues | Create a dependency (source blocks target) | | list_cycles | Cycles with progress | | create_cycle | Create a cycle (sprint) in a project | | update_cycle | Update a cycle's name/status/dates | | list_members | Workspace members (resolve assignees) |

Every tool acts as the user who created the API key, scoped to that user's workspace.

Publishing

The package is configured for public npm publishing (publishConfig.access: public, prepublishOnly builds dist). To release:

cd packages/mcp
npm publish