willder-core
A context layer that syncs your apps, agents and teams. Access control on every call, real-time coordination. MIT.
Install / Use
claude mcp add willderai -- npx -y github:willderai/willder-coreIf the server publishes to npm under a different name, use that package instead — check the repo README.
MCP Server
Model Context Protocol server
Quality Score
Category
Data & AnalyticsSupported Platforms
Tags
Our assessment of willder-core
willder-core scores 81/100 on our quality scale, 516th of 604 Data & Analytics skills we index.
Its MCP Server is 20 KB long, well organised into 11 sections with 9 code examples: a thorough specification that gives an agent plenty to work with.
It has 10 GitHub stars, so there is little community track record yet; judge it on its content.
Maintenance, license and trust
- The repository was last updated 12 days ago, so willder-core is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 97/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-14. Automated pattern scan on 2026-11-14. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
willder-core compared with similar skills
All 4 of these similar skills score higher than willder-core; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| willder-core (this skill)by willderai | 81 | 10 | 12d ago | MCP Server |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| CowAgentby zhayujie | 100 | 48.0k | today | CLAUDE.md |
Frequently asked questions
- How do I install willder-core?
- Run
claude mcp add willderai -- npx -y github:willderai/willder-core. The install tabs above show the steps for each supported agent. - Which AI agents does willder-core work with?
- It is written for Claude Code, Claude Desktop, Cursor and OpenAI Codex, as a MCP Server file. Other agents that read the same format can often use it too.
- Is willder-core safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 97/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is willder-core still maintained?
- The repository was last updated 12 days ago, so willder-core is actively maintained.
Skill content
View source on GitHubWillder
Apps, Agents, Teams Synced.
Willder is a context layer that syncs your apps, agents and teams, with access control on every call and real-time coordination: what one agent writes, the others read on their next call. Each agent holds its own scoped, expiring token; its memory reads and writes pass one check and land in the audit log; revoke a token and its next call is refused. Connect your Claude Code or Cursor agent over MCP in five minutes.
<p align="center"> <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue" alt="MIT license"></a> <a href="https://github.com/willderai/willder-core/releases"><img src="https://img.shields.io/github/v/release/willderai/willder-core" alt="Latest release"></a> <a href="https://modelcontextprotocol.io"><img src="https://img.shields.io/badge/MCP-server-0b6e4f" alt="MCP server"></a> <a href="https://github.com/willderai/willder-core/discussions"><img src="https://img.shields.io/github/discussions/willderai/willder-core" alt="Discussions"></a> </p> <p align="center"> <a href="https://willder.ai">Website</a> · <a href="docs/README.md">Docs</a> · <a href="docs/architecture.md">Architecture</a> · <a href="docs/connect/README.md">Connect a client</a> · <a href="https://github.com/willderai/willder-core/discussions">Discussions</a> </p> <p align="center"> <img src="docs/images/willder-demo.gif" alt="Claude Code saves that launch is Friday. Codex asks on its next call and gets it, with who wrote it. A marketing agent asks the same question and gets No facts found. The fact is changed to Monday once, and Codex's next read says Monday. The timeline shows who wrote it and who read it." width="880"> </p>What it does
- The right context, unasked. At the start of a task an agent gets a short brief of what matters for it: the scope's rules, decisions and recent writes, ranked by the task's words. Queries search by words, by meaning and by links in the graph. Task-start briefs, hybrid retrieval.
- One memory across every agent. What Claude Code saves, Codex reads on its next call, with who wrote it. Change a fact once and every agent reads the new version. Versions and conflicts.
- Connectors into scopes. GitHub, Google Drive, Slack, Figma and PostHog sync into a scope you choose, under that scope's rules. services/connectors/.
- Access control. Each agent holds its own scoped, expiring token. Its memory reads and writes pass one check and land in the audit log; a revoked token is refused on its next call. What the check does not cover is listed under Limits. The single check.
- Set up in minutes. One command connects Claude Code; Codex, Cursor and other clients have a page each. Connect a client.
- Memory you can see. Every fact keeps who wrote it, where it came from, what it replaced and which agents first read it. Audit and provenance.
How it works
flowchart LR
accTitle: The parts of Willder and how a request moves through them.
accDescr: An MCP client with a capability token and a person in the web app both reach the memory operations. check() decides each guarded operation against Postgres and writes an audit row. Allowed operations read and write the Postgres stores, including pgvector, and the graph through the memory service, which owns Neo4j and the embedding model.
mcp["MCP client: agent token"] --> ops["Memory operations"]
web["Web app: signed-in person"] --> ops
ops --> chk{"check()"}
chk --> pg[("Postgres: scopes, grants, tokens, audit_log, versions, pgvector chunks")]
chk -- allow --> pg
chk -- allow --> ms["Memory service: FastAPI, BGE-384 embeddings"]
ms --> neo[("Neo4j via Graphiti: facts and relations")]
Deep dives: architecture, hybrid retrieval, conflict resolution, database, API, export format, self-hosting.
Why
You run several agents on real work: a coding agent in the repo, a research agent on a schedule, a side project's agent. Nothing decides what each may see, tells the others when one changes something, or records what was read. Willder is the memory they share and the fence between them: scopes, per-agent tokens, a change feed and an audit, with no model in any access decision.
Run it on your machine
This repository is the engine: Postgres with pgvector, Neo4j, the memory service and the MCP server. It runs on your own machine with no willder.ai account and no call to willder.ai. You need Docker with Compose v2, Node 20.19+, 22.12+ or 24+, and a few GB of disk. Without Docker, docs/self-host.md says what to run instead.
git clone https://github.com/willderai/willder-core.git && cd willder-core
npm install
cp .env.selfhost.example .env # then set GRAPHITI_SERVICE_API_KEY to any string
docker compose up -d --wait # Postgres, Neo4j, the memory service; the first build takes minutes
npx prisma migrate deploy # create the tables
npm run selfhost:smoke # write, scoped read, refusal, export, no outside calls
The smoke ends with 9 of 9 steps passed. docs/self-host.md describes each
line it prints and what to do when one fails.
Mint a token for your agent. One per agent, scoped and expiring:
npm run selfhost:token -- --scope team --agent claude-code
It prints a wcap_... token once. Put it in an environment variable and nowhere else:
printf 'Willder token: '
stty -echo; read -r WILLDER_TOKEN; stty echo
printf '\n'
export WILLDER_TOKEN
Connect Claude Code to the local stdio MCP server, from this directory:
claude mcp add -s user willder-local -e WILLDER_CAPABILITY_TOKEN="$WILLDER_TOKEN" \
-- npm --prefix "$PWD" run --silent mcp
Then tell the agent: Save this to Willder: we store sessions in Postgres, not Redis, so they survive a restart. Then ask Willder where we store sessions and why.
It calls memory_ingest with two required arguments, content (the fact) and name (what the
fact is about), and gets back the id a later update passes as baseVersion:
Stored and readable now; graph extraction continues in the background. Version: <version id>.
Then it calls memory_query, which returns one bullet per fact with when and who wrote it (an
agent that has only a token is named by it, quoted), notes on what its grant let it read, and the
answer's revision:
• we store sessions in Postgres, not Redis, so they survive a restart. (as of <when it was stored>) — from: "claude-code" (agent token) (agent) · version <version id>
revision: <16 hex characters>
A token for another scope (npm run selfhost:token -- --scope research --agent second-agent)
gets No facts found. for the same question. Other clients: docs/connect/;
the stdio server and its tools: mcp/README.md.
The engine calls out to one thing at most, and only if you configure it: an OpenAI-compatible model endpoint that extracts facts on writes (a local server works; without one a write is still stored and readable, and only graph extraction is skipped). The web app is optional: it needs a free Clerk development instance to sign people in, and docs/self-host.md lists the other outside calls it makes. An export is one JSON Lines file in a documented format: docs/export-format.md.
Prefer not to run it? The hosted service at willder.ai runs the same engine: docs/quickstart.md.
Prove it does not leak
Two checks, about ten minutes, and neither needs an account. The second revokes the
claude-code token from Run it on your machine (any token you are
willing to revoke works).
1. Run the leak suite. From a fresh clone, with Node 20.19, 22.12 or 24:
git clone https://github.com/willderai/willder-core.git && cd willder-core
npm ci
npm run test:leaks
Installing takes about a minute; the suite runs in seconds with no keys and no network. It
is every test file named *eval.test.ts, *leak.test.ts or *leakage.test.ts: check(),
the guarded memory reads and the MCP tool bodies run for real, and only the database and
memory backends are stubbed. A pass ends with no failed file. One file,
app/api/briefs/staleness-scope-leak.test.ts, reports as skipped unless QA_DATABASE_URL
names a test Postgres (docs/development.md). The suite asserts that:
- a token scoped to one team never receives a sibling scope's facts, graph nodes, uploaded files or briefs, and the in-scope token still does, so an over-broad filter fails too;
- a revoked or expired token is refused on every memory tool over the real MCP endpoint;
- a call without a real caller identity is denied, never audited under a stand-in actor;
- the account tier can narrow a read and never widen one;
- the same holds with thousands of facts and concurrent callers, and a backend failure is reported as a failure, not as an empty answer.
A few cases are named GAP:. They pass by pinning a known defect, and each one says what
the correct behaviour is. The suite proves the code; step 2 proves the running service.
2. Revoke a token and see its next call refused. Revoke the agent's token from the terminal:
npm run selfhost:token -- --revoke claude-code
It prints each token it revoked by id, scope, permission and expiry, never the token, and nothing waits for the token to expire. What the agent sees next depends on how it connects:
- A stdio MCP server already running, like the
claude mcp addconnection above: it keeps listing its tools, but every memory call after the revoke is refused and nothing is read or written. Memory tools answerAccess denied: no valid capability for agent claude-code granting read(orwrite)on the target scope …, and each refusal is a deny row in the audit log under the call's own action (memory.read,memory.writeormemory.entity). - A stdio MCP server started with the revoked token exits before connecting, with
WILLDER_CAPABILITY_TOKEN is not a live token in this database (unknown, expired or revoked), and records acapability.refusedrow. - Over HTTP, the web app's
/api/mcporhttps://willder.ai/api/mcpon the hosted service, the next call getsHTTP 401withInvalid or unknown capability token.and acapability.refuseddeny row for that agent.
npm run selfhost:export holds every one of those refusals as audit lines.
Measured on the hosted service
Measured with dates: the first three rows on the hosted service at willder.ai, the setup row in a clean container. The harness that produced them is not in this repository. Implementation is not proof, and nothing here is a guaranteed latency.
| Claim | Evidence | Status | |---|---|---| | Access control under failure: scoped tokens, default deny, a token revoked mid-sequence denied on its next call, one audit row per read and per refusal | 2026-10-01: held under six concurrent readers and a revoke mid-sequence | Proven in production at failure load | | Connected sources: co
Truncated for display — read the full file on GitHub.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
CowAgent
48.0kOpen-source personal AI assistant & Agent Harness. Plans tasks, runs tools and skills, self-evolves with memory and knowledge. Multi-agent, multi-model, multi-channel. Lightweight, extensible, one-line install.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
