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

@sensesinnovations/cms-mcp

v0.1.0

Published

MCP server for the Senses Innovations CMS. Connects Claude Desktop / Claude Code to the SI CMS REST API.

Readme

@sensesinnovations/cms-mcp

An MCP server that exposes the Senses Innovations CMS REST API to Claude Desktop, Claude Code, and any other MCP-compatible client.

The server is a thin, stateless adapter. At startup it fetches its tool catalog from your CMS install via GET /api/v1/mcp/tools (filtered by the token's profile and cached for 10 minutes), then forwards every tools/call to POST /api/v1/mcp/<name>. It holds no state of its own — auth, scopes, rate limits, idempotency, and audit logging all live server-side in the CMS.

Install

Most users do not install this globally. Claude Desktop / Claude Code spawn the binary on demand via npx:

npx -y @sensesinnovations/cms-mcp

For a system-wide install:

npm install -g @sensesinnovations/cms-mcp
senses-cms-mcp   # then bound to your PATH

Requires Node.js >= 20.18.

Configuration

Two environment variables:

| Var | Required | Default | Notes | | ----------------- | -------- | ------------------------------------ | -------------------------------------------------------------------------------- | | SI_CMS_TOKEN | yes | — | API token, format sk_live_... or sk_test_.... | | SI_CMS_API_URL | no | https://www.sensesinnovations.com | Override for staging or self-hosted installs. No trailing slash required. | | SI_CMS_DEBUG | no | unset | Set any truthy value to include stack traces in error messages emitted to stderr. |

Quick start — Claude Desktop

Add the server to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "senses-cms": {
      "command": "npx",
      "args": ["-y", "@sensesinnovations/cms-mcp"],
      "env": {
        "SI_CMS_TOKEN": "sk_live_..."
      }
    }
  }
}

Restart Claude Desktop. The CMS tools appear under the hammer icon in any new chat.

Quick start — Claude Code

claude mcp add senses-cms \
  --env SI_CMS_TOKEN=sk_live_... \
  -- npx -y @sensesinnovations/cms-mcp

For staging or a self-hosted install, also pass --env SI_CMS_API_URL=....

Where to get a token

In your CMS admin: Integrations → Tokens → New token. The admin UI also produces a ready-to-paste mcp.json snippet and the equivalent claude mcp add command, so you can skip writing the config by hand.

Tokens carry a profile — a curated subset of tools tailored to a role. Pick the smallest profile that covers the work you intend to do; smaller profiles load faster and consume less context.

Token profiles

The admin UI lists the full per-profile tool inventory under Integrations → MCP → Tools reference. The high-level profiles:

| Profile | Use case | | ----------------------------- | ------------------------------------------------------------------------- | | content_editor | Default for daily writing — content CRUD, translations, media, briefs. | | seo_manager | SEO metadata, sitemap, hreflang, analytics. | | translation_pipeline | Dedicated transcreation: request translations, publish locales. | | devops | Deploys, cache invalidation, integrations, diagnostics. | | read_only_analyst | Research and reporting only — no writes, no destructive tools. | | ai_discoverability_manager | LLM citation optimization: llms.txt, bot policy, AI crawl stats. | | lead_management | Sales-side lead access; requires the leads:pii scope. | | full_admin | All tools, including DESTRUCTIVE ones; for human admins only. |

Custom profiles (allowlist / category include / exclude) are also supported and configured server-side in the same admin UI.

What this package is (and is not)

  • It is a Node binary exposing the CMS via MCP over stdio, plus a small JS client library (@sensesinnovations/cms-mcp/client) and the profile metadata used by the admin UI.
  • It is not a standalone CMS, a cache, or a credential store. Tokens flow through unchanged; nothing is logged client-side beyond a single startup line to stderr.
  • It does not ship tool implementations. The tool catalog is fetched at runtime from your CMS so the server stays in lockstep with the deployed API even when this package lags behind.

Source

packages/mcp in aaelfouly/si-web-app. File issues at the same repo.

License

MIT © Senses Innovations LLC