ClariLayer

io.github.clarilayerPublished by GitHub account clarilayerv0.31.0Updated Nov 2, 2026

Individual-analyst context layer: recall, remember, and reconcile your data and engineering context.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper ToolsData & Analytics

Overview

AI-generated overview

Hosted context layer that lets an AI recall, remember, correct and forget durable work context across projects and sessions.

What you can do
  • Recall saved context across an authorized space, with source and applicability, and fetch full entries by ID
  • Save confirmed facts, preferences, decisions, rules and lessons, or stage suggestions as proposals for review
  • Forget or exclude specific entries after recalling them, and record bounded completion checkpoints or context-use feedback
  • Analytics path: recall definitions, schema notes and saved queries, import supplied SQL, dbt models and data dictionaries, and reconcile saved definitions against evidence the agent supplies
  • Check local dbt documentation for phantom columns, missing models and type mismatches, optionally staging findings as proposals
When to use it
Useful when you want an assistant to carry settled decisions, rules and preferences from one session or project into the next, or to keep analyst definitions and schema notes consistent. Also fits teams that want reviewable proposals rather than silent memory writes.
Requirements
Remote MCP endpoint reached over streamable HTTP with OAuth, or a context key stored locally as a fallback and sent in the Authorization header. A ClariLayer account and an authorized space are needed; the optional npm CLI requires Node.js. The local dbt check needs no account or warehouse connection.
Before you install
The context key is a secret: keep it out of AI conversations and public issues. Recall only happens if the client calls the tool, and delivery receipts or checkpoints do not prove correct context use. History import and ongoing capture need separate setup and consent, and selected content is processed by an extraction provider, which may incur charges. Semantic search has its own consent. Forget operations delete entries, so target them by returned entry ID.

Installation

In SourceWeft

  1. Open ClariLayer in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.clarilayer%2Fclarilayer/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "clarilayer": {
      "type": "http",
      "url": "https://clarilayer.com/api/mcp/mcp"
    }
  }
}

README

[MseeP.ai Security Assessment Badge]

[ClariLayer]

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.

One decision, carried into the next session

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.

Connect your AI

Use Connect your 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.

ClientProject instruction target
Claude CodeCLAUDE.md
CodexAGENTS.md
Cursor.cursor/rules/clarilayer.mdc
claude.ai / other remote clientsFollow 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.

Optional setup CLI

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 <client>.

Check which version is available before choosing a command:

bash
npm view clarilayer version

With 0.3.0 or later available:

bash
npx clarilayer@latest init# Already connected? Print only the instruction update request:npx clarilayer@latest instructions --agent codex

If your registry still serves 0.2.1, use npx [email protected] 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.

What your AI can do

WorkHow it works
Recallrecall_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 correctremember with work_context saves confirmed durable facts, preferences, decisions, rules and lessons. Ambiguous changes and suggestions remain candidates for review.
ForgetRecall 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 loopcontext_checkpoint records the AI's bounded completion declaration. It does not prove the AI used the right context or completed an external task.
Report usereport_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.

Bring over selected history

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.

Analytics when your work needs 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

[Analytics example: recall a net-revenue definition, compare it with warehouse evidence, then retain a mismatch as a caveat]

A seeded Analytics demo. Your agent supplies the warehouse evidence; a mismatch becomes a caveat for later sessions. This illustrates the Analytics specialist path.

Check dbt documentation locally

bash
cd your-dbt-projectdbt docs generatenpx 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.

Control and privacy

  • Saved context retains its source and applicability. Separate spaces do not merge automatically.
  • History import, ongoing capture and semantic processing each have their own setup or consent boundary.
  • In the personal MCP reconcile path, ClariLayer holds no warehouse or CRM credentials, executes no SQL and calls no HubSpot API. Your agent supplies the evidence. Warehouse evidence may include optional preview rows; CRM evidence is row-free.
  • Suggestions can be staged with 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.

Security · Privacy · Pricing

What is open source?

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.

Source: README.md at commit 87188b0

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.31.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.