@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.
Maintainers
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-mcpFor a system-wide install:
npm install -g @sensesinnovations/cms-mcp
senses-cms-mcp # then bound to your PATHRequires 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-mcpFor 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
