snow-flow

MCP运维云端

提供方 groeimetai · 包名 snow-flow

运维云端 stdio · 本地进程 未标注 社区 / 第三方 Claude DesktopCursorClineClaude Code
查看接入方式

🤖 AI-powered ServiceNow development with 400+ MCP tools. Works with Claude, GPT, Gemini, Ollama & 75+ providers. Deploy widgets, manage incidents, aut

一句话选型结论

按资料字段整理

snow-flow 属于运维云端类 MCP 服务器,stdio · 本地进程,鉴权方式未标注,可直接接入 Claude Desktop、Cursor、Cline 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类运维云端 传输方式stdio · 本地进程 鉴权未标注 部署方式本地部署
GitHub 星标 61 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

运维云端
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

snow-flow ai ai-agent servicenow

支持客户端

适用场景

snow-flowaiai-agent

安装与配置

stdio · 本地进程 未标注
客户端在本机拉起子进程,数据不出本机
npx -y snow-flow

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Cross-platform,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
云资源查询

查实例、存储、账单等云上资源状态。

部署与发布

把部署、重启、回滚这类操作接进对话。

监控与告警

拉取监控指标,异常时让模型帮你判断。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Cursor、Cline,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在运维云端场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
snow-flow当前 未标注 stdio · 本地进程 本地部署 有 2026-04-12
lobehub 未标注 stdio · 本地进程 本地部署 有 2026-04-11
TrendRadar 未标注 stdio · 本地进程 本地部署 有 2026-04-13
Ui Tars Desktop 8a825770 未标注 stdio · 本地进程 本地部署 有 2026-05-17
ruflo 未标注 stdio · 本地进程 本地部署 有 2026-04-13
FastGPT 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

运维云端
字段来自项目仓库与公开索引,中文说明由本站标注
提供方groeimetai上游标注的维护方 groeimetai
分类运维云端本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时snow-flow · Cross-platform本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-04-12上游最后核验时间

详细介绍

8.7 KB
来自项目仓库与上游目录的原文,未做删改

███████╗███████╗██████╗ █████╗ ██████╗
██╔════╝██╔════╝██╔══██╗██╔══██╗██╔════╝
███████╗█████╗ ██████╔╝███████║██║
╚════██║██╔══╝ ██╔══██╗██╔══██║██║
███████║███████╗██║ ██║██║ ██║╚██████╗
╚══════╝╚══════╝╚═╝ ╚═╝╚═╝ ╚═╝ ╚═════╝

A ServiceNow MCP server, and the skill guides that teach an agent to use it.

Two packages, and nothing else:

Package What it is
@serac-labs/servicenow-mcp An MCP server for ServiceNow. 400+ snow_* tools over stdio or streamable HTTP, plus blast-radius impact analysis.
@serac-labs/skills 57 ServiceNow skill guides. Plain markdown an agent loads into its prompt so it uses those tools like a practitioner.

The two are meant to be used together. The server gives a model the ability to act on a ServiceNow instance;
the skills give it the judgement to do so without breaking one — which update set to be in, why a Business
Rule needs ES5, what to check before renaming a field.

Both work with any MCP client. Neither requires the Serac product.

Quick start```bash

npm install -g @serac-labs/servicenow-mcp


Point your MCP client at the `servicenow-mcp-stdio` binary:```json
{
  "mcpServers": {
    "servicenow": {
      "command": "servicenow-mcp-stdio",
      "env": {
        "SNOW_INSTANCE": "https://dev12345.service-now.com",
        "SNOW_CLIENT_ID": "…",
        "SNOW_CLIENT_SECRET": "…"
      }
    }
  }
}

Credentials come from an OAuth application registry entry on your instance (System OAuth > Application Registry). A developer instance from developer.servicenow.com is enough
to try everything here.

If nothing works — an auth error, or a response that will not parse — ask the server what is wrong before
changing anything:```bash
servicenow-mcp-stdio --doctor


It names which credential source was used, whether the URL is usable, whether the instance is awake (a
hibernating developer instance answers with an HTML login page, which makes every tool look broken), whether
the OAuth exchange succeeds, and which roles the account holds. The model can ask for the same report by
calling `snow_diagnose_setup`.

The catalog is far larger than a context window, so tools are **deferred** by default: `tools/list` returns
two meta-tools and the model widens its own surface as it works.```
tool_search({query: "incident"})  → the matching tools, now enabled
tool_execute({tool: "snow_query_incidents", args: {query: "priority=1"}})

Set SNOW_LAZY_TOOLS=false to register the whole catalog up front instead. Full options, library usage and
the multi-tenancy rules are in the package README.

As a Claude Code plugin

The repository is also a plugin marketplace, so the server and all 70 skills arrive in one step:```
/plugin marketplace add serac-labs/serac
/plugin install servicenow@serac


The server runs through `npx`, so nothing has to be installed first: export the same three variables as
above and it is ready. The same entry is in `.mcp.json` at
the repo root, which Claude Code reads for this project. Other clients each want it somewhere else: copy it
into `.cursor/mcp.json` (Cursor), `~/.codeium/windsurf/mcp_config.json` (Windsurf), or `.vscode/mcp.json`
for VS Code, which names the same block `servers` rather than `mcpServers`.

### Using the skills

A skill is a directory with a `SKILL.md`: YAML frontmatter naming the skill and the `snow_*` tools it
expects, then prose. Nothing loads them automatically — a host decides which ones to put in front of the
model. Copy the ones you want into your agent's skills directory, or read them from the package:```ts
import { skillsRoot } from "@serac-labs/skills/root"

They are worth reading on their own, even without an agent involved. Start with
es5-compliance,
update-set-workflow or
blast-radius.

Working on it

Requires Bun 1.3.14 — pinned in the root package.json packageManager field, which is
also what CI installs.```bash
bun install
bun typecheck # tsgo across both packages
bun run test # both suites
bun run lint # oxlint


Tests do not run from the repo root directly — run them per package, or through turbo with `bun run test`:```bash
cd packages/servicenow-mcp && bun test
cd packages/skills && bun test

Adding a tool

Tools live in packages/servicenow-mcp/src/servicenow-mcp-unified/tools//snow_.ts, one file
per tool, each exporting a toolDefinition and an executor. The registry is generated by walking that
directory, so a new file in the right shape is a new tool — there is no central list to edit. Regenerate the
published manifest afterwards:```bash
bun run --cwd packages/servicenow-mcp generate:tools-json


### Adding a skill

Create `packages/skills//SKILL.md` with frontmatter, then regenerate the embedded map:```bash
bun run --cwd packages/skills generate

bun test in that package fails if the embedded map drifts from the tree, or if frontmatter names a tool the
MCP server does not actually have. Both of those have shipped to users before.

Two files that are production, not build output

packages/servicenow-mcp/tools.json and packages/servicenow-mcp/sn-roles.manifest.json are committed
generated files, and live services fetch them straight from main over raw.githubusercontent.com. They are
published by being committed. Moving or renaming either one is a production change: the consumer has to be
repointed and deployed first, and the old path removed in a separate commit afterwards. See
the package README.

Releases

@serac-labs/servicenow-mcp publishes from .github/workflows/publish-mcp.yml — a manual
workflow_dispatch, versioned from packages/servicenow-mcp/package.json and nothing else, with OIDC
trusted publishing and signed provenance. Every PR that touches the package runs the same build, test and
packaging gates without publishing, including one that copies the package out of the workspace entirely and
proves it installs, builds and tests with no monorepo around it.

The MCP registry listing is a second, separate dispatch:
.github/workflows/publish-mcp-registry.yml uploads the repo-root server.json once the npm version is
live. server.json repeats that version and the package name, so a gate on every PR touching either file
fails when the two disagree — bun run --cwd packages/servicenow-mcp check:registry-manifest.

@serac-labs/skills releases the same way, from .github/workflows/publish-skills.yml, with gates
adapted to what that package actually ships: the tarball must contain every entrypoint and every skill
directory, and every published subpath must load under node from a real npm install — skillsRoot()
hands consumers a filesystem path, so an import that merely succeeds proves nothing.

Its npm trusted publisher does not exist yet, so no version has gone out. Creating it (bound to
serac-labs/serac + publish-skills.yml) is a manual step on npmjs.com; see the workflow header.

What used to be here

This repository was a fork of opencode carrying a terminal AI agent,
a TUI, a desktop app and a web console. Twenty-five packages went; the two above remain. The
@serac-labs/core CLI those packages built is discontinued — it stays installable on npm at its final
version, but there are no further releases and no security fixes for it.

The ServiceNow work was always the part worth keeping, and it was the part buried deepest. It is now the
whole repository.

One artifact of that era is deliberately still here: the install script at the repo root. Every CLI already
installed in the world fetches that exact URL when it self-upgrades, and serac.build/install redirects to
it. Deleting the file would pipe a GitHub 404 page into those users' shells. It stays until it is replaced
with something that tells them what happened — do not tidy it away.

Contributing

Read CONTRIBUTING.md first — it is short. Every PR links an issue, and the code style
rules are in AGENTS.md.

License

Apache License 2.0. See NOTICE for third-party attributions: this code's history
begins in the MIT-licensed opencode project.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
snow-flow 怎么安装?

在客户端按下面的安装命令接入:npx -y snow-flow。对应的包名是 snow-flow。装完在客户端配置里引用同一个包或端点。

snow-flow 怎么在 Claude Desktop、Cursor、Cline 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

snow-flow 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

snow-flow 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

snow-flow 支持哪些客户端?

资料标注支持 Claude Desktop、Cursor、Cline、Claude Code;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

snow-flow 能提供哪些能力?

资料显示能力标签包括 snow-flow、ai、ai-agent、servicenow。具体工具清单以官方文档为准。

snow-flow 需要什么运行环境?

运行时为 Cross-platform;属于本地进程,需要在本机装好运行环境。

snow-flow 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-04-12。