World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Your StoryOS workspace (records, approvals and agents) for Claude, ChatGPT and any MCP client.
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 20/100 | 热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-11-18 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 4/5 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 StoryOS。按照 https://mcp.popnx.com/i/storyos.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 4/5 项检查 · 你的提问会经过开发者的服务器(mcp.storyos.dev) · ✓ 命令已检查 2026年11月19日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
StoryOShttps://mcp.storyos.dev/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsStoryOS
用 StoryOS 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 StoryOS,或回答中出现 StoryOS 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
StoryOShttps://mcp.storyos.dev/mcp开启新聊天,输入前先从插件列表中选择 StoryOS
用 StoryOS 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 StoryOS,或回答中出现 StoryOS 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user storyos https://mcp.storyos.dev/mcp应能看到 StoryOS 在列表中并显示已连接
用 StoryOS 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 StoryOS,或回答中出现 StoryOS 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 StoryOS 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 StoryOS,或回答中出现 StoryOS 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 StoryOS 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 StoryOS,或回答中出现 StoryOS 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp.storyos.dev/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user storyos https://mcp.storyos.dev/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"storyos": {
"url": "https://mcp.storyos.dev/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"storyos": {
"type": "http",
"url": "https://mcp.storyos.dev/mcp"
}
}
}Claude Code
claude mcp add --scope user storyos --env STORYOS_TOKEN=your-value -- npx -y @storyos/mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"storyos": {
"command": "npx",
"args": [
"-y",
"@storyos/mcp"
],
"env": {
"STORYOS_TOKEN": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"storyos": {
"command": "npx",
"args": [
"-y",
"@storyos/mcp"
],
"env": {
"STORYOS_TOKEN": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"storyos": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@storyos/mcp"
],
"env": {
"STORYOS_TOKEN": "your-value"
}
}
}
}STORYOS_TOKEN 机密 必填 envSTORYOS_URL envSTORYOS_MCP_PROFILE envWEB_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月20日
注册名称已通过域名 storyos.dev 验证(注册中心会核实域名所有权)
代码最后更新于昨天
GitHub 无法识别许可证类型;请打开文件自行查看
在 547 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
OSV.dev 中没有 @storyos/mcp@0.1.2 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月19日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/storyos)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:STORYOS_TOKEN
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于昨天,最新版本(0.1.2)于昨天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 本项 StoryOS | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 4/5 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | NOASSERTION | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
The StoryOS Model Context Protocol server — it exposes your StoryOS workspace to AI agents (Claude first; ChatGPT-compatible by design). It's a thin, stateless translator over the same /api/v1 the web app uses, so it can never drift from the product, and every response is scoped and validated server-side.
Design + roadmap: docs/product/mcp-plan.md. Ticket: MN-076.
Read
| Tool | What it does |
|---|---|
get_started | Orientation + a workspace map; with section it returns one reference section (the filter cheat-sheet, icons, working notes, a tool's full notes). |
list_workspaces | Workspaces the token can access. |
list_databases | Databases in a workspace. |
describe_database | A database's schema — exact api_names, types, options, relation targets: what a write is keyed by. |
search | Full-text record search — turn a name into a real id. |
query_records | Filter / sort / paginate records (structured filter AST). |
get_record | One record in full, by uuid or public number. |
get_links | Web-app URLs for a database, its saved views, and/or a batch of records — without a round-trip per record. |
Write (each returns the resulting record; each 422 is surfaced verbatim)
| Tool | What it does |
|---|---|
create_record | Create a record; values by api_name, selects accept the label, relations accept an array of target numbers/ids (linked in the same write). |
update_record | Merge-update (null clears); record by uuid or public number. Naming a relation sets it to exactly those targets. |
delete_record | Trash a record (restorable 30 days). |
link_records | Link a record to targets through a relation field. replace: true sets the link set to exactly targets — how you re-point or clear a one-to-many link. |
unlink_records | Remove specific links from a relation field (the relation itself stays). |
add_comment | Post a comment. |
attach_file | Attach a file to a record — from a public url (fetched server-side) or inline content_base64; images get a thumbnail. |
list_attachments / delete_attachment | List a record's files, or remove one by id. |
run_button | Press a button field, running its automation actions. |
Build / schema (agents design the workspace, not just fill it)
| Tool | What it does |
|---|---|
list_spaces / create_space | List / create spaces (a space holds databases). |
create_database / update_database / delete_database | Create, rename/move, or delete a database (delete needs confirm = name). |
add_field / update_field / delete_field / change_field_type | Manage fields; select options by label; convert a field's type (dry_run to preview). |
create_view / update_view / delete_view | Manage views; accepts group_by / card_fields / date fields plus filters + sorts. |
create_relation / delete_relation | Link two databases (one_to_many / many_to_many) — paired relation fields. |
reorder_fields / reorder_views | Set field / view order by name. |
Skills (a workspace's saved skills, over MCP)
| Tool | What it does |
|---|---|
list_skills | Skills visible to the caller — their own personal ones, plus every shared one (same visibility rule the in-app Skills list enforces). |
run_skill | Resolve a skill's instructions/when_to_use by name or id, and record the run (last_run_at/last_run_status). The call invokes no model, so you — the connected agent — carry out the instructions against the inputs you pass; they're echoed back, not executed server-side (an agent set to "StoryOS AI" can have the skill named in its Skills field instead). |
A workspace's skills are also exposed as native MCP resources and prompts, for clients that understand those primitives (not just tools):
storyos-skill://{workspace}/{skill} template. resources/list returns one entry per visible skill (across every workspace the token can see); reading one returns the skill rendered as portable Markdown — the exact shape GET /skills/:id/export?format=markdown produces.skill_weekly_status_digest), disambiguated by workspace name on a name collision. prompts/get returns the skill's instructions as a single user-role message, ready to paste into context.Both are read-only and best-effort: a catalog fetch failing for one workspace never blanks out another's, and a failure registering them never breaks the tools (see server.ts).
Automations (build a complete workflow — admin-scoped, #334)
| Tool | What it does |
|---|---|
list_automations | The rules on a database — each with its trigger (field/relation names resolved), condition, actions, enabled state, failure streak and last-run status. |
get_automation | One rule's full, editable definition — human-readable database/field/select names alongside their stable ids — ready to feed back into update_automation. |
create_automation | Create a rule = trigger (record_created / record_updated / record_linked / schedule / webhook_received) + optional condition (a query_records-style filter) + 1–10 actions (set_values / create_record / add_comment / notify_user / update_linked / send_slack_message / send_webhook / send_email / http_request / run_agent). Field/relation/person names and select labels resolve server-side; the in-app validator (AutomationActionsService.validate) validates the whole rule, so a bad reference comes back as a structured error, not a 500. |
update_automation | Rename, enable/disable, or replace a rule's trigger / condition / actions — every field optional, re-validated the same way. |
delete_automation | Delete a rule (requires confirm=true); reports the removed rule's name, trigger and action summary. |
Automations are an admin surface (the API is @RequiresScope('admin') and creator-gated), so all five tools are advertised only to an admin-scoped token — a read- or write-scoped PAT never sees them and therefore can never mutate a rule. These tools call the same endpoints the in-app RuleEditor does; there is no parallel validation path. Diagnose why a rule did (or didn't) fire with get_runs.
Conveniences: query_records / get_record return select values as labels (not option ids) and rich_text as Markdown; create_record / update_record accept Markdown on a rich_text field (headings, lists, links, code → parsed to blocks) and select labels; create_record reports any unset template fields. get_record / query_records / create_record / update_record all include a url — a clickable web-app link for that record — so an agent never has to describe a manual navigation path.
Hosted Streamable HTTP (for ChatGPT / claude.ai connectors without a local process) is the remaining phase — it lands with the cloud tier (see MN-069).
Every listed tool description is billed on every request of every session, so the listing is kept small: under 60,000 characters in total and no description over 1,500 (src/tool-description-budget.test.ts enforces both against the live registry). A description in the source can be as long as the tool needs; tools/list carries a short lead plus [Full notes: get_started section "TOOL NOTES "] (the one canonical pointer format, double quotes), naming the exact section. get_started with no argument returns only the overview and an index of section names (under 10,000 characters, so no client truncates it); get_started with section set to a name from that index returns that one section: the full text of one tool (the long reference grammars are TOOL NOTES create_automation, install_pack, add_field, create_source), FILTERS, ICONS or WORKING NOTES. Matching is exact first, then case-insensitive; an unknown name returns a text answer listing the valid names. One 85,000-character result was the alternative, and a client that truncates a single result would have silently dropped the grammars. A section is only loaded when called, so it costs a capped client nothing up front (src/get-started-sections.test.ts checks every lead points at a section that exists). Where a lead must say something at call time, it is hand-written with a short: key next to the description. The agent-run profile (?profile=agent-run, the Runner's runs) offers get_started too, because parameter hints (FILTERS, ICONS) name it, but keeps every description WHOLE (WHOLE_DESCRIPTION_PROFILES in src/tool-profiles.ts): its 9 tools total about 3k characters, only ~1k more than leads would cost, and a lead is a round trip. src/profile-pointers.test.ts checks, for every profile, that a pointer names a tool the profile offers and a section its own index lists.
Maintainer-only tools (get_branch_name, get_pinned_tabs, set_pinned_tabs, get_dismissed_hints, set_dismissed_hints, list_icon_set; INTERNAL_TOOLS in src/tool-profiles.ts) are not offered on any customer connection. They appear with ?profile=internal over HTTP, or STORYOS_MCP_PROFILE=internal for a stdio server. The icon names list_icon_set used to return are in get_started section ICONS.
The Claude connector directory policy for tool metadata is that a description contains no instructions about model behaviour or other tools. A tool description says what the tool does, takes and returns; it may state a product fact and carry a neutral reference (See also: describe_database, [Full notes: get_started section "TOOL NOTES "]). Guidance for the model (look at the schema before writing, count with count_records, do not retry a held write, ...) lives in get_started section WORKING NOTES, which is a tool RESULT and not a description. src/tool-description-policy.test.ts enforces this against the live registry: every tool description and every parameter description, on every profile, is scanned for imperatives about another tool, sequencing words around a tool name, "read this before"-style calls to action and behavioural instructions (FORBIDDEN_PATTERNS), with self-tests and an explicit ALLOWED_PHRASES list that needs a reason per entry.
describe_database gives exact api_names; you read before you write.get_started section FILTERS.search / list_* / a prior result; names and slugs are accepted and resolved server-side.1. Get a token — in StoryOS, sidebar → API tokens → create one for the workspace you want. Copy the mn_pat_… (shown once; scoped to that workspace). Without this, the server starts and immediately exits with fatal STORYOS_TOKEN is required — that's the config check working, not a broken install.
2a. Claude Code
claude mcp add storyos \
-e STORYOS_URL=https://app.storyos.dev \ -e STORYOS_TOKEN=mn_pat_xxx \ -- npx -y @storyos/mcp
2b. Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json)
{
"mcpServers": { "storyos": { "command": "npx", "args": ["-y", "@storyos/mcp"], "env": { "STORYOS_URL": "https://app.storyos.dev", "STORYOS_TOKEN": "mn_pat_xxx" } } } }
STORYOS_URL is https://app.storyos.dev for the cloud box, or