Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Individual-analyst context layer: recall, remember, and reconcile your data and engineering context.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
Authorization标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
在终端中运行这条命令
claude mcp add --transport http clarilayer https://clarilayer.com/api/mcp/mcp --header 'Authorization: your-value'运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"clarilayer": {
"url": "https://clarilayer.com/api/mcp/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"clarilayer": {
"type": "http",
"url": "https://clarilayer.com/api/mcp/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
Authorization 机密 必填 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 clarilayer 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.31.0)于3个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, HotCodePush
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
ClariLayer
Your AI should remember how you work.
Turn selected past conversations into memory your AI can use across projects and sessions.
Website · Docs · Connect your AI · Quickstart
ClariLayer keeps the facts, preferences, decisions, rules and lessons you choose to carry forward. Connect Claude Code, Cursor, Codex, claude.ai or another compatible remote MCP client. Your AI can recall relevant work context from the selected authorized space, with its source and applicability visible.
Start free. No credit card for the current personal offer.
You settle a launch decision with your AI:
For the Launch project, show the product demo first. Technical detail belongs in docs. Remember this confirmed decision with its source and project applicability.
In a later session:
Recall the Launch project's saved decisions before drafting the launch page. Show which decision applies and where it came from.
The decision can travel across projects and sessions within the authorized space while retaining its original applicability. A rule for one customer or project stays bounded. If it changes, correct it; if it no longer belongs, use scoped forget or exclusion.
Recall depends on the AI client actually calling the tool. Connecting MCP does not guarantee every answer uses saved context.
Use [Connect your AI](https://clarilayer.com/connect-ai) for guided setup. Select your client and space, give the setup request to that AI, and complete authentication in the client. Use OAuth when the selected route supports it, or store a context key locally as the fallback. Never paste a key into an AI conversation or a GitHub issue.
Already connected? Choose Update my AI setup on the same page, then run its request in the intended project. This updates one recognized ClariLayer instruction block while preserving your own instructions.
| Client | Project instruction target |
|---|---|
| Claude Code | CLAUDE.md |
| Codex | AGENTS.md |
| Cursor | .cursor/rules/clarilayer.mdc |
| claude.ai / other remote clients | Follow the connection and runtime guidance supported by that client |
The installed bootstrap obtains the current workflow from get_project_stanza with mode: "runtime" once at the first relevant use in each new AI session. A routine server guidance update then reaches the next session without copying another long workflow into every project.
The npm CLI supports context-key connection setup and a local dbt check. CLI 0.3.0 replaces the embedded Analytics instructions with a request for your connected AI and adds instructions --agent .
Check which version is available before choosing a command:
npm view clarilayer version
With 0.3.0 or later available:
npx clarilayer@latest init
npx clarilayer@latest instructions --agent codex
If your registry still serves 0.2.1, use npx clarilayer@0.2.1 init --no-stanza to skip its older embedded instructions, then complete Update my AI setup through the guided setup above. The hosted path is available independently of npm publication.
See CLI.md for options and the source-checkout route, CHANGELOG.md for release history, and RELEASING.md for publication checks. Native instruction qualification records the tested client and its limits.
Full setup, manual connection examples and troubleshooting: [QUICKSTART.md](./QUICKSTART.md).
| Work | How it works |
|---|---|
| Recall | recall_context retrieves relevant saved context across the selected authorized space. Preserve source and applicability; project and purpose are relevance hints, not permissions. Fetch complete entries with get_context_entry when needed. |
| Remember or correct | remember with work_context saves confirmed durable facts, preferences, decisions, rules and lessons. Ambiguous changes and suggestions remain candidates for review. |
| Forget | Recall the target first, then use its returned entry ID for the requested forget operation. Do not guess names or delete related entries without a separate request. |
| Complete the context loop | context_checkpoint records the AI's bounded completion declaration. It does not prove the AI used the right context or completed an external task. |
| Report use | report_context_use optionally links bounded feedback to delivered context. A delivery receipt alone is not evidence of answer quality. |
The hosted MCP service was checked on September 17, 2026: capability v64 · server 0.39.0 · 23 tools. Use the live capabilities tool for the current list and versions. Capability reference.
After connection, you can choose supported local history, a destination space and an extraction provider, then inspect the exact preview before accepting an initial import. Ongoing capture requires a separate setup and grant for the sources you choose. Connecting MCP alone does not read history or enable capture.
Source support and extraction-provider support are separate. The current qualified extraction path uses a version-specific Claude CLI profile; OpenAI and Cursor extraction providers are unavailable, and native Cursor history qualification is limited. Check the current history guide before choosing a source.
Selected source content is processed by the chosen extraction provider. ClariLayer stores the extracted context rather than a raw transcript archive. Provider processing may use your allowance or incur provider usage charges.
Optional semantic search has separate organization consent and provider disclosure in Settings. A new connection or history-import choice does not grant that consent. Lexical recall remains available without it.
ClariLayer for Analytics retains its specialist tools:
get_analysis_context recalls definitions, schema notes, saved queries and related context. Recall previews can be truncated; use get_context_entry for full bodies, stored SQL and CRM contracts.bootstrap imports supplied SQL, dbt models, notes, data dictionaries and semantic models. It does not read a repository or warehouse by itself.reconcile compares a saved definition with supported warehouse or bounded, row-free HubSpot evidence supplied by your agent. Salesforce contracts can be stored and recalled; Salesforce reconcile is disabled.General work and engineering context are not independently reconciled. Live trust statuses remain `asserted` / `caveat`; verified is not live.
Watch the Analytics reconcile example
A seeded Analytics demo. Your agent supplies the warehouse evidence; a mismatch becomes a caveat for later sessions. This illustrates the Analytics specialist path.
cd your-dbt-project
dbt docs generate npx clarilayer dbt-check
The CLI compares local manifest.json and catalog.json files for phantom columns, missing catalog models, type-family mismatches and empty descriptions. No account or warehouse connection is needed for the local check. With an explicit --save, bounded findings are staged as proposals in your Context Inbox for review. --save --dry-run previews the payload without a network request.
See the CLI reference and Analytics recipes. The August 2026 dbt drift survey retains its method, evidence and limitations for the published 0.2.1 check.
propose / propose_batch for review. Pending proposals are not live recall context. Ad hoc conversation harvest requires an explicit request and sends distilled candidates, not the transcript.This repository's docs, examples, recipes and setup/dbt CLI are MIT licensed. The hosted ClariLayer service is proprietary. This repository is the public starting point for connecting to the service.
The Governed Context Edge is available through a hand-run private team pilot. Request early access.
For contributions and setup help, see CONTRIBUTING.md.