Getting Started
MereKit Link starts from a single YAML file. You can use it as a standalone inspector, as a Mere workspace helper, or as the policy layer in front of Executor-backed product integrations.
Install
npm install -g @merekit/link
mere-link --versionIf you already use the public Mere command plane, install @merekit/cli instead and run the same Link commands under mere link:
npm install -g @merekit/cli
mere link config init --output mere.link.yaml
mere link config validate --config mere.link.yaml --jsonThe standalone @merekit/link package remains the source package for Link behavior and docs. The @merekit/cli package bundles a generated Link adapter so operators can keep one root mere entrypoint across apps.
For local development inside this repo:
pnpm install
pnpm verifyCreate A Config
mere-link config init --output mere.link.yamlThat creates a small graph with one workspace entity, one workspace project, and a few starter surfaces.
Validate And Inspect
mere-link config validate --config mere.link.yaml --json
mere-link entities list --config mere.link.yaml --json
mere-link projects list workspace --config mere.link.yaml --json
mere-link surfaces list workspace workspace --config mere.link.yaml --jsonUse context inspect when an agent needs a single project context.
mere-link context inspect workspace workspace --role work --config mere.link.yaml --jsonEvaluate Operator Policy
Operator policy is optional in the YAML, but when used it gives agents a neutral preflight before exporting context or preparing writes.
mere-link policy taxonomy --json
mere-link policy evaluate workspace workspace --capability project.context.export --operator approved-agent --config mere.link.yaml --jsonAdd A Surface
schemaVersion: 1
integrations:
url:
plugin: url
github:
plugin: executor
namespace: github
entities:
workspace:
name: Workspace
projects:
workspace:
name: Workspace
surfaces:
docs:
integration: url
kind: link
id: https://example.com/docs
code:
integration: github
kind: repo
id: owner/repo
optional: trueRun validation again after every shape change.
mere-link config validate --config mere.link.yaml