Stripe MCP
MCP server integrating with Stripe - tools for customers, products, payments, and more.
Hosted headless CMS with native commerce: pages, media, forms, products, orders, refunds, discounts.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 28/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 48/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Cmssy。按照 https://mcp.popnx.com/i/cmssy-io-cmssy-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(api.cmssy.io) · ✓ 命令已检查 2026年11月19日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Cmssyhttps://api.cmssy.io/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsCmssy
用 Cmssy 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Cmssy,或回答中出现 Cmssy 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Cmssyhttps://api.cmssy.io/mcp开启新聊天,输入前先从插件列表中选择 Cmssy
用 Cmssy 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Cmssy,或回答中出现 Cmssy 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user cmssy https://api.cmssy.io/mcp应能看到 Cmssy 在列表中并显示已连接
用 Cmssy 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Cmssy,或回答中出现 Cmssy 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Cmssy 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Cmssy,或回答中出现 Cmssy 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Cmssy 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Cmssy,或回答中出现 Cmssy 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://api.cmssy.io/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user cmssy https://api.cmssy.io/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"cmssy": {
"url": "https://api.cmssy.io/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"cmssy": {
"type": "http",
"url": "https://api.cmssy.io/mcp"
}
}
}Claude Code
claude mcp add --scope user cmssy --env CMSSY_API_TOKEN=your-value --env CMSSY_WORKSPACE_ID=your-value -- npx -y @cmssy/mcp-serverClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"cmssy": {
"command": "npx",
"args": [
"-y",
"@cmssy/mcp-server"
],
"env": {
"CMSSY_API_TOKEN": "your-value",
"CMSSY_WORKSPACE_ID": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"cmssy": {
"command": "npx",
"args": [
"-y",
"@cmssy/mcp-server"
],
"env": {
"CMSSY_API_TOKEN": "your-value",
"CMSSY_WORKSPACE_ID": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"cmssy": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@cmssy/mcp-server"
],
"env": {
"CMSSY_API_TOKEN": "your-value",
"CMSSY_WORKSPACE_ID": "your-value"
}
}
}
}CMSSY_API_TOKEN 机密 必填 envCMSSY_WORKSPACE_ID 必填 envCMSSY_API_URL env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 cmssy-io 验证,该账户拥有此仓库
代码最后更新于今天
使用 MIT
在 534 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
尚未检查
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/cmssy-io-cmssy-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:CMSSY_API_TOKEN
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于今天,最新版本(0.147.0)于今天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:Stripe MCP, flightclaw, Trade It, Marketplace Ad Pros: Amazon Ads & Seller Central, idealo MCP Server
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP server integrating with Stripe - tools for customers, products, payments, and more.
Search ~300 airlines and book flights with a checkout link. OAuth sign-in by email code.
Connect brokerage accounts to AI assistants: holdings, orders, asset lookup, and approved trading.
Amazon Ads, Seller Central, Vendor Central and AMC data for AI agents. Read-only by default.
Search products, compare prices and discover deals across 6 European markets with your AI assistant.
| 本项 Cmssy | Stripe MCP | flightclaw | Trade It | Marketplace Ad Pros: Amazon Ads & Seller Central | idealo MCP Server | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 5/5 | 4/4 | 4/4 |
| 许可证 | MIT | MIT | MIT | CC0-1.0 | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
MCP server for Cmssy, a hosted headless CMS with built-in commerce. Lets an AI agent work with pages, records, media, forms, products, orders, refunds and discounts in a Cmssy workspace.
https://api.cmssy.io/mcp serves the same tools over HTTP. Claude (web, desktop, Code) and Codex connect by signing in to cmssy. A client that asks for a server URL and an API key - v0, Lovable, Bolt or your own - sends a cs_ token instead:
URL: https://api.cmssy.io/mcp
Header: Authorization: Bearer cs_YOUR_TOKEN
A token scoped to one workspace reaches only that workspace; an unscoped token reaches every workspace you belong to. Every tool takes a workspace ( / ), and list_workspaces names the ones the token may use. It reads and writes with your role in each workspace. Changing your password does not revoke it - delete it under Dashboard > API Tokens. Details: cmssy.com/docs/api/mcp.
cs_)The server talks to https://api.cmssy.io by default. Pass --api-url only for another backend.
Add to .mcp.json in your project root:
{
"mcpServers": { "cmssy": { "type": "stdio", "command": "npx", "args": [ "-y", "@cmssy/mcp-server@latest", "--token", "cs_YOUR_TOKEN", "--workspace-id", "YOUR_WORKSPACE_ID" ] } } }
Instead of CLI args, you can set:
CMSSY_API_TOKEN — API token (cs_xxx)CMSSY_WORKSPACE_ID — Workspace IDCMSSY_API_URL — API URL (optional; defaults to https://api.cmssy.io, so set it only for a self-hosted backend)--version and --help need no token, so they answer even when the server is not configured. Run the flag against the same spec your client launches, copied out of your mcp.json:
npx -y @cmssy/mcp-server --version # what an unpinned config runs
npx -y @cmssy/mcp-server@latest --version # what the registry serves today npm view @cmssy/mcp-server version # the newest published version
The first two can disagree, and that disagreement is the answer: a warm npx cache holds the build an unpinned spec resolved to earlier, while @latest re-resolves and reports the newest one. So @latest --version cannot diagnose a stale cache - it is the command that hides it. Ask the unpinned spec first when a tool fails on a field the API should serve, then compare.
Clearing the cache is npx clear-npx-cache, or pin the version in your config so nothing has to be diagnosed.
Full policy: https://www.cmssy.com/privacy. Contact: contact@cmssy.com.
https://api.cmssy.io unless you set CMSSY_API_URL), carrying your API token, your workspace ID, the tool's arguments, the client name and version, and the name of the tool being run. The Cmssy API records one usage event per tool call from those last two.upload_media reads only the local file path or downloads only the URL you pass it, then uploads the bytes to the Cmssy storage URL the API returns. It touches no other file.upload_media. Third parties the Cmssy service itself uses are listed in the policy.As of 0.6.0, most write tools accept an optional response arg:
response: "minimal" (default) - returns a small ack (~200 bytes): {id, slug, hasUnpublishedChanges, updatedAt} for page tools, {pageId, blockId, hasUnpublishedChanges, updatedAt} for block tools, {id, slug, status, updatedAt} for form tools, {id, slug, updatedAt} for model tools, {id, status, updatedAt} for record tools, {id, orderNumber, status, paymentStatus, fulfillmentStatus, total, balanceDue, currency, updatedAt} for order tools, {id, code, type, value, enabled, updatedAt} for discount tools.response: "full" - returns the full mutation response (pre-0.6 behavior).Use "full" only if you need the post-write state inline; otherwise issue a follow-up get_page/get_form/get_model/get_record. This keeps agent context windows from being eaten by echoed content.
Tools that accept response: create_page, update_page_blocks, update_page_settings, publish_page, unpublish_page, revert_to_published, update_page_layout, add_block_to_page, update_block_content, remove_block_from_page, create_form, update_form, create_model, update_model, create_record, update_record, create_manual_order, edit_order, update_order_details, mark_order_paid, record_order_payment, refund_order, cancel_order, close_order, reopen_order, create_return, approve_return, reject_return, cancel_return, receive_return, refund_return, complete_return, update_return_tracking, create_shipment, update_shipment, set_order_pipeline_stage, record_order_invoice, record_order_invoice_correction, create_discount, update_discount, set_discount_enabled.
patch_block_content and the various delete_* / status-only tools (update_form_submission_status, import_records) already returned a compact ack and don't take response.
On connect the server sends instructions that send an agent (v0, Lovable, Bolt, Claude) to get_site_setup first. It returns the files cmssy init writes for Next.js - catch-all page, editor route, proxy, config, block registry, header/footer regions - with the workspace's env vars filled in. The agent then deploys, calls set_preview_url, creates the content.changed webhook for /api/revalidate, has the user open the editor once so the block types register, creates the pages with header and footer in their layout regions, and publishes them.
| Tool | Description |
|---|---|
get_site_setup | Everything to build a site on the workspace: the files to write, packages, env vars filled in, steps |
list_pages | Page tree with hierarchy (optional search filter) |
get_page | Full page with blocks, i18n content and region settings (own regionSettings + resolved resolvedRegions with inheritance source) by slug or id |
get_site_config | Languages, navigation, site name |
get_workspace_info | Workspace name, plan, limits |
list_media | Media library listing |
list_trashed_pages | Page trash: deleted groups with who deleted them, subtree size and when each is purged (30 days after deletion) |
| Tool | Description |
|---|---|
create_page | Create a new page |
update_page_blocks | Set full blocks array on a page |
update_page_settings | Update page metadata and SEO |
publish_page | Publish a page |
set_preview_url | Point the editor at the deployed app (stores the URL's origin) |
unpublish_page | Unpublish a page |
delete_page | Move a page and its subtree to the trash, restorable for 30 days |
restore_page | Restore a trashed page group as unpublished drafts |
revert_to_published | Discard draft, revert to published |
| Tool | Description |
|---|---|
add_block_to_page | Insert a block at position (auto-generates UUID + translations) |
update_block_content | Merge content into an existing block |
patch_block_content | Surgical HTML patch (insert/replace around unique markers) |
remove_block_from_page | Remove a block by ID |
update_page_layout | Update layout blocks and overrides |
update_region_settings | Set one layout region's settings (manifest-validated; other regions untouched) |
update_region_settingsRegion (layout position) settings are declared by the workspace's layout manifest and validated against it on write. The tool reads the page's current layoutRegionSettings, replaces only the named region and writes the whole list back, so sibling regions keep their values (entries for regions the manifest no longer declares, and keys a region's schema no longer has, are dropped on the way - the same pruning the admin editor does). The backend's own BAD_USER_INPUT message is returned verbatim for an unknown region, an unknown key, or a non-empty values on a region that declares no settings (such a region accepts values: {} only); blockWarnings are surfaced when present.
{ "pageId": "...", "region": "sidebar", "values": { "width": "wide" } }
Child pages inherit a region's settings unless they set their own - get_page shows the effective value per region in resolvedRegions (settingsAreInherited, settingsSourcePageId).
patch_block_contentFor small edits on long HTML content strings (e.g. a docs-article body), patch_block_content is ~10x cheaper in tokens than update_block_content and catches marker mistakes before anything writes to the DB.
{
"pageId": "...", "blockId": "...", "locale": "en", "operations": [ { "op": "insert_before", "marker": " Environment Variables ", "html": " cmssy skills install ... ", }, ], }
Four ops: insert_before, insert_after, replace_section, replace_all. Every marker must match exactly once - 0 or 2+ matches error out with the actual count (no silent half-applied state). For replace_section, startMarker is inclusive and endMarker is exclusive. `replace_a