Total CMS MCPB
Connects Claude to Total CMS sites, enabling search, browsing, and management of content via the site's built-in MCP server. Supports both public and authenticated access using an API key stored securely.
README
Total CMS Desktop Extension (MCPB)
A Claude Desktop extension that connects Claude to any Total CMS site's built-in MCP server. Install once, and Claude can search docs, browse content, and (with an API key) manage your Total CMS site directly.
This is a local bridge, not a hosted connector: it runs as a small Node
process on your machine and proxies MCP traffic to your site's /mcp
endpoint over HTTPS. That's what lets it attach a custom X-API-Key header
for authenticated access - something Claude Desktop's built-in remote
connectors can't do for servers that advertise optional auth.
Privacy Policy
This extension does not collect, transmit, or store any data of its own. It
opens an HTTPS connection directly from your machine to the Total CMS MCP
endpoint you configure (default: https://totalcms.co/mcp, the official
Total CMS docs site) and relays MCP protocol messages between Claude Desktop
and that endpoint. Your optional API key is stored in your OS's secure
credential store (via Claude Desktop's sensitive: true config handling) and
is sent only as an X-API-Key request header to the site you configured -
never logged, never sent anywhere else.
For the privacy policy of the Total CMS product and totalcms.co itself, see https://totalcms.co/privacy.
Setup
Zero-config: ask about Total CMS itself
Just install the extension. It defaults to https://totalcms.co/mcp, the
official Total CMS documentation server, so Claude can immediately answer
questions like "how do I set up webhooks in Total CMS?" or "what schema
fields does Total CMS support?" with no configuration.
Connect to your own site
- In your Total CMS admin, go to Settings -> MCP and copy your site's
MCP endpoint URL (it will look like
https://yoursite.com/mcp, or include a subpath if you installed Total CMS in one). - In Claude Desktop's extension settings for Total CMS, paste that URL into Total CMS MCP endpoint.
- Reinstall/reconnect. Claude can now browse and search your site's public collections.
Authenticated (admin) access
- Generate a Total CMS API key for your site (Settings -> API Keys, or your preferred key-issuing flow).
- Paste it into the API key (optional) field in the extension settings. It's stored in your OS keychain, not in plain text.
- Claude now has admin-level access to your site's MCP tools (schema management, templates, site info, cache clearing, etc.) in addition to public content. Leave this field empty to keep Claude limited to public, anonymous access.
How it works
server/index.js is a small stdio MCP server that Claude Desktop spawns
directly (no Node install required - MCPB bundles include their own
runtime handling). It opens a
streamable HTTP
connection to the MCP_URL you configured and forwards every JSON-RPC
message in both directions verbatim: initialize, tools/list,
tools/call, resources/*, prompts/*, and all notifications. When
API_KEY is set, every outbound HTTP request carries an X-API-Key header.
It refuses to start unless MCP_URL is https:// - plaintext credentials on
the wire are not acceptable, even for local testing.
Why not mcp-remote?
We spiked it first (see BUILD-REPORT.md for the full writeup). Short
version: mcp-remote unconditionally runs OAuth discovery on startup and,
on any HTTP 401 response, launches a browser-based OAuth authorization flow
with no flag to disable it. Total CMS uses a plain API-key header, not OAuth
- a bad key needs to surface as a clean 401 error to the MCP client, not
hang behind a browser popup trying to OAuth against a server that doesn't
implement it. So this bundle ships a small hand-rolled proxy built directly
on
@modelcontextprotocol/sdk'sStreamableHTTPClientTransportandStdioServerTransportinstead.
Development
npm install
npm run build # typecheck -> esbuild bundle -> mcpb validate -> mcpb pack
Produces dist/totalcms.mcpb. Install by dragging that file onto Claude
Desktop.
npm run typecheck and npm run validate are available standalone.
Security notes
- Zero filesystem access, zero subprocess spawns, outbound HTTPS to exactly
one host (whatever
MCP_URLpoints at). - The API key is read from the
API_KEYenvironment variable (set by Claude Desktop from your keychain-stored config) and is never written to stdout, stderr, or any log. MCP_URLmust behttps://or the process refuses to start.
License
Source code is MIT licensed. The Total CMS name, flame logo, and
the bundled icon.png are trademarks and are not covered by that grant — you
may fork the code, but a redistributed version must not present itself as
published or endorsed by Total CMS.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。