Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
AI Visibility and Content Intelligence tools for Claude and MCP-compatible agents.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.sleepwalker.ai/mcp在终端中运行这条命令
claude mcp add --transport http sleepwalker https://mcp.sleepwalker.ai/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"sleepwalker": {
"url": "https://mcp.sleepwalker.ai/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"sleepwalker": {
"type": "http",
"url": "https://mcp.sleepwalker.ai/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.sleepwalker.ai/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 sleepwalker.ai 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.1.1)于4个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, AI Deprecations
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
AI Visibility and Content Intelligence for agents, products, and teams.
Run AI-search checks, inspect citations, score content, and save every result in one workspace.
Website · App · Docs · MCP · API · CLI · Cookbook
Sleepwalker helps teams understand how AI systems talk about a brand and what content needs to change. It combines two connected workflows:
You can run the same work from the hosted app, the public API, MCP clients, or the CLI. Results stay connected, so a run started by an agent can be reviewed later in the app or queried from code.
This repository is the public developer surface for Sleepwalker: CLI package, API examples, MCP setup notes, and short guides. The hosted engine, app source, database schema, provider integrations, and billing systems are private.
Try the CLI without an account first. okf export is free and open source. It runs on your machine, fetches a page, and writes an agent-ready markdown bundle to a local folder. No API key, no credits:
npx -y @sleepwalkerai/cli okf export https://www.sleepwalker.ai
One command exports both concepts: the page content and the technical snapshot of what AI crawlers see. Narrow it with --content or --technical. Both concepts are described in the next section.
For everything else, install the CLI:
npm install -g @sleepwalkerai/cli
sleepwalker init
Create an API key in the Sleepwalker app, then run your first visibility check:
sleepwalker auth key set sw_api_live_...
sleepwalker doctor sleepwalker visibility run https://yourbrand.com \ --brand YourBrand \ --prompt "best ai visibility platform 2026" \ --platform perplexity,openai,grok,gemini \ --watch
One command turns any public page into an Open Knowledge Format bundle: a folder of plain markdown files with YAML frontmatter that any AI agent can read directly. OKF is an open format published in Google Cloud's knowledge-catalog repo. The export runs entirely on your machine and is free for everyone: no account, no API key, no credits.
sleepwalker.ai-okf/
├── index.md navigation and okf_version ├── log.md how and when the bundle was generated ├── home.md the content concept └── home-technical.md the technical snapshot
Both concepts ship by default. --content exports only the content concept, --technical exports only the snapshot.
The content concept is the page as a reader sees it: clean markdown with headings, paragraphs, lists, and links, plus the title, description, canonical URL, and timestamp in the frontmatter. Use it to hand pages to agents, prompts, and retrieval pipelines without HTML noise.
The technical snapshot is the page as an AI crawler sees it. Most AI crawlers do not run JavaScript, so the snapshot reads only the served HTML plus the response itself: the redirect chain and HTML size, curated HTTP headers, the html lang attribute, meta and title tags, canonical, icon and feed links, headings, hreflang, social tags, head scripts, every JSON-LD block, a microdata and RDFa summary, links, images, and the robots directives the page and response carry (meta robots and X-Robots-Tag). Use it to audit what ChatGPT, Claude, Perplexity, and Gemini can actually read on your pages.
One excerpt shows why this matters. A client-side rendered page often exports like this:
## Structured data
JSON-LD: none found. AI crawlers get no schema.org data from this page as served.
Everything is reported, nothing is judged: the export quotes what the page serves and leaves conclusions to you. Duplicate titles and canonicals are preserved on purpose, because they are findings. The only network request is the page fetch itself. Flags, caps, and the full section list live in docs/cli.md.
Want to see the shape of the data first? Open docs/responses.md for full example outputs from serialization, prompt suggestions, AI Visibility, Content Intelligence, and report lookup.
okf export. Open source, runs locally, no account needed.okf export also captures the page's technical layer as served, including meta tags, structured data, headers, and robots directives. --technical exports it alone.| Surface | Best for | Entry point |
|---|---|---|
| App | Human review, credits, keys, and full result views | app.sleepwalker.ai |
| API | Scripts, products, scheduled jobs, and reporting workflows | API docs |
| MCP | Claude and other MCP-capable agents | MCP setup |
| CLI | Terminal workflows and automation | CLI docs |
CLI
sleepwalker visibility run https://yourbrand.com \
--brand YourBrand \ --prompt "best ai visibility platform 2026" \ --platform perplexity,openai,grok,gemini \ --watch
API
curl -s https://api.sleepwalker.ai/v1/visibility/runs \
-H "Authorization: Bearer $SLEEPWALKER_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "url": "https://yourbrand.com", "target_entity": "YourBrand", "prompts": ["best ai visibility platform 2026"], "platforms": ["perplexity","openai","grok","gemini"] }'
MCP
https://mcp.sleepwalker.ai/mcp
Ask an MCP-capable client: Check how YourBrand appears across AI search this week.
App
Open app.sleepwalker.ai for the visual workflow, saved results, credits, and keys.
| Path | What it shows |
|---|---|
docs/agents.md | MCP tool catalog and agent workflow walkthrough |
docs/concepts.md | Runs, probes, serialization, scoring, credits |
docs/cli.md | CLI usage, including the free local okf export |
docs/cookbook.md | Runnable workflows, including CI checks |
docs/responses.md | Full example outputs for the main Sleepwalker actions |
mcp/server.json | Remote MCP server manifest |
mcp/tools.json | Public MCP tool catalog, scopes, and credit behavior |
examples/api/curl | One-call examples for public API actions |
examples/api/javascript | Raw fetch plus a zero-dependency client helper |
examples/api/python | urllib examples plus a small client class |
examples/mcp | OAuth and bearer-token setup notes |
Sleepwalker is pay as you go. Reads, lists, and status polling are normally unmetered. Actions that run work, such as visibility checks, content scoring, and serialization, use prepaid credits. okf export is the exception: it runs locally and is always free. Details live in docs/credits.md and the hosted billing docs.
This repository is intentionally small.
| Public here | Private in Sleepwalker |
|---|---|
| CLI, examples, setup notes, short docs | Hosted engine and app source |
| Public API request shapes | MCP server implementation |
| MCP client connection examples | Database schema and billing internals |
| Product-level credit behavior | Provider integrations and routing |
Do not commit real keys. Use environment variables or the CLI key store:
export SLEEPWALKER_API_KEY=sw_api_live_...