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를 쓰세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
Authorization 비밀 필수 HTTP header이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
레지스트리 이름이 GitHub 계정 clarilayer 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: Authorization
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.31.0)은 3개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Reelsaw
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ 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.
Drive a self-hosted Reelsaw: turn long videos into vertical clips, edit, re-render and export them.
제작자의 저장소에서 쓰인 그대로 가져왔어요. 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.