How do I install Weavatrix Online?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Weavatrix Online need an API key?

The publisher lists these environment variables: WEAVATRIX_SYNC_URL, WEAVATRIX_SYNC_TOKEN, WEAVATRIX_CAPABILITIES_URL, WEAVATRIX_ARCHITECTURE_URL, WEAVATRIX_PRECISION, WEAVATRIX_ADVISORY_STORE.

What transport does Weavatrix Online use?

Weavatrix Online runs locally over stdio.

When was Weavatrix Online last checked?

Last checked 2026-11-09. Weavatrix Online extension: guarded sync, advisories, malware review, architecture contracts.

Weavatrix Online MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y [email protected]

Credentials from the publisher

WEAVATRIX_SYNC_URL — Cloud or compatible self-hosted sync endpoint
WEAVATRIX_SYNC_TOKEN — Scoped bearer token for the selected endpoint
WEAVATRIX_CAPABILITIES_URL — Optional explicit endpoint capability document URL; defaults to /api/v1/capabilities on the sync origin with legacy /api/health fallback
WEAVATRIX_ARCHITECTURE_URL — Optional explicit architecture-contract URL
WEAVATRIX_PRECISION — Core semantic precision: lsp (default) or off
WEAVATRIX_ADVISORY_STORE — Optional local advisory-cache file override

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1WEAVATRIX_SYNC_URL=<value> WEAVATRIX_SYNC_TOKEN=<secret> WEAVATRIX_CAPABILITIES_URL=<value> WEAVATRIX_ARCHITECTURE_URL=<value> WEAVATRIX_PRECISION=<value> WEAVATRIX_ADVISORY_STORE=<value> claude mcp add io.github.weavatrix-weavatrix-online -- npx -y weavatrix-online@0.3.4

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.weavatrix-weavatrix-online": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ],9      "env": {10        "WEAVATRIX_SYNC_URL": "<value>",11        "WEAVATRIX_SYNC_TOKEN": "<secret>",12        "WEAVATRIX_CAPABILITIES_URL": "<value>",13        "WEAVATRIX_ARCHITECTURE_URL": "<value>",14        "WEAVATRIX_PRECISION": "<value>",15        "WEAVATRIX_ADVISORY_STORE": "<value>"16      }17    }18  }19}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

Weavatrix Online

Take repository intelligence across a network without handing the network your repository.

The explicit network boundary of the Weavatrix ecosystem. Core and Refactor remain separate installs.

Weavatrix Online is the MIT-licensed MCP connector for Weavatrix Cloud and compatible customer-controlled endpoints. It keeps analysis local, produces an inspectable source-free payload, and requires an exact short-lived confirmation before that payload can leave the machine.

The public Online profile exposes 7 MCP tools for endpoint discovery, advisories, malware review, architecture contracts, and controlled synchronization. The local weavatrix-js graph engine is an implementation detail: its tools are not re-exported, so installing Core, Refactor, and Online together does not duplicate their catalogs in an agent's context.

Installing or starting Online does not synchronize anything. preview_sync makes no network request; sync_graph accepts only the still-valid preview for the same repository, destination, payload, and graph.

Choose the right Weavatrix package

Product	Install	Boundary
`weavatrix`	npm or Cargo	Native local-first MCP product. Both package managers distribute the same local Weavatrix server and engine.
`weavatrix-rust`	Cargo	Protocol-independent Rust repository-intelligence engine for library and CLI use; it does not own MCP transport.
`weavatrix-refactor`	npm or Cargo	Native extension-only transactional refactoring; it uses the Rust graph engine internally.
`weavatrix-online`	npm	This optional network extension: source-free Cloud/self-hosted workflows over an internal local graph runtime.

Online currently uses the JavaScript graph/runtime package internally:

weavatrix-online 0.3.4
  └─ weavatrix-js 0.3.x (internal; no Core tools re-exported)

It does not proxy the native weavatrix executable, import weavatrix-refactor, or copy either engine. Use weavatrix when the graph must remain entirely local. Use weavatrix-online when endpoint status, remotely managed architecture contracts, advisory refresh, or explicit source-free synchronization is part of the workflow.

Install and run

Plugins for Cursor, Codex, Claude, and Grok

The repository now contains one portable plugin bundle at plugins/weavatrix-online plus native marketplace manifests for all four clients. The plugin starts the pinned npm release and includes an optional, compact skill with one lazily loaded card per Online method.

codex plugin marketplace add Weavatrix/weavatrix-online --sparse .agents/plugins plugins/weavatrix-online
codex plugin add weavatrix-online@weavatrix-online

claude plugin marketplace add Weavatrix/weavatrix-online --sparse .claude-plugin plugins
claude plugin install weavatrix-online@weavatrix-online

grok plugin marketplace add Weavatrix/weavatrix-online

Cursor can load the bundle locally from ~/.cursor/plugins/local/weavatrix-online; public marketplace discovery starts after the listing is reviewed and approved.

Direct MCP launch

Run the pinned release without a global install:

npx -y [email protected] C:\path\to\repository

The command starts a stdio MCP server. The first positional argument is the repository to analyze. An existing graph can be supplied explicitly:

npx -y [email protected] C:\graphs\repository\graph.json C:\path\to\repository

The npm package is intentionally an executable MCP product; it does not advertise a nonexistent JavaScript library entry point.

Codex

[mcp_servers.weavatrix_online]
command = "npx"
args = ["-y", "[email protected]", "C:\\path\\to\\repository"]

[mcp_servers.weavatrix_online.env]
WEAVATRIX_SYNC_URL = "https://app.weavatrix.com/api/v1/graphs/sync"
WEAVATRIX_SYNC_TOKEN = "load-from-runtime-secret-storage"

Claude Desktop

{
  "mcpServers": {
    "weavatrix-online": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]",
        "C:\\path\\to\\repository"
      ],
      "env": {
        "WEAVATRIX_SYNC_URL": "https://app.weavatrix.com/api/v1/graphs/sync",
        "WEAVATRIX_SYNC_TOKEN": "load-from-runtime-secret-storage"
      }
    }
  }
}

Keep bearer tokens in the MCP client's runtime secret storage. Do not put them in Git, a committed .env, release logs, or checked-in MCP configuration.

The seven Online tools

Tool	Network	Evidence and effect
`online_status`	Yes	Discovers endpoint capabilities, payload versions, limits, and auth mode without repository evidence.
`refresh_advisories`	Yes	Inventories exact dependency coordinates, queries OSV, validates returned records, and atomically refreshes the local cache.
`scan_dependency_vulnerabilities`	No	Matches the current inventory against that cache. Missing, stale, partial, or mismatched coverage remains `NOT_CHECKED` or `PARTIAL`.
`scan_dependency_malware`	No	Performs bounded static review of installed dependency files. Findings require review and are never a compromise verdict.
`pull_architecture_contract`	Yes	Fetches the owner-approved target for the active opaque repository ID, validates it, and updates the local graph cache.
`preview_sync`	No	Serializes the exact allowlisted payload, hashes it, and issues a five-minute confirmation token.
`sync_graph`	Yes	Sends only the payload approved by `preview_sync`; `dry_run:false` and the matching token are mandatory.

Install Weavatrix Core for read-only repository intelligence and Weavatrix Refactor for guarded source changes. Their methods remain in their owning products.

Typical workflows

Check endpoint compatibility before doing any repository work:

{"name":"online_status","arguments":{"timeout_ms":10000}}

Refresh advisory evidence, then evaluate it locally:

{"name":"refresh_advisories","arguments":{"timeout_ms":20000}}
{"name":"scan_dependency_vulnerabilities","arguments":{"max_age_days":30}}

Review the exact upload without sending it:

{"name":"preview_sync","arguments":{"payload_version":3}}

After a human or trusted controller approves the displayed destination, section summary, counts, size, and body hash, use the returned token:

{
  "name": "sync_graph",
  "arguments": {
    "payload_version": 3,
    "dry_run": false,
    "confirm_token": "token-returned-by-preview_sync",
    "timeout_ms": 30000
  }
}

Changing the graph, repository, destination, payload, or expiry state invalidates that approval. A rejected or unavailable endpoint leaves the graph local.

Network and consent boundary

local repository
      │
      ▼
local graph + derived evidence
      │
      ▼
preview_sync ── inspect destination, sections, counts, size, and SHA-256
      │
      ▼
explicit approval
      │
      ▼
sync_graph ── capability negotiation ── approved endpoint

The connector enforces:

HTTPS for every non-loopback destination;
loopback-only HTTP for local development;
no credentials embedded in URLs;
endpoint capability negotiation before upload;
a bounded versioned payload allowlist;
exact preview hashing and a short-lived confirmation token;
honest NOT_CHECKED and PARTIAL states when evidence is incomplete.

The sync payload contains bounded graph topology and selected derived evidence. It excludes source bodies, snippets, absolute host paths, environment values, credentials, Git remotes, and fields outside the wire allowlist. “Source-free” does not mean anonymous: review the displayed repository identity, destination, counts, sections, and hash before approval.

Configuration

Variable	Required	Meaning
`WEAVATRIX_SYNC_URL`	For Online network workflows	Cloud or compatible self-hosted sync endpoint.
`WEAVATRIX_SYNC_TOKEN`	For Cloud/authenticated endpoints	Scoped bearer token sent only to the approved endpoint.
`WEAVATRIX_CAPABILITIES_URL`	No	Explicit capability document; otherwise `/api/v1/capabilities` with legacy `/api/health` fallback.
`WEAVATRIX_ARCHITECTURE_URL`	No	Explicit owner-approved architecture-contract endpoint.
`WEAVATRIX_PRECISION`	No	Local semantic precision: `lsp` (default) or `off`.
`WEAVATRIX_GRAPH_HOME`	No	Override local graph/cache storage.
`WEAVATRIX_ADVISORY_STORE`	No	Override the local advisory-cache file.

Compatible endpoints must implement the versioned capability and sync contracts. Capability discovery itself sends no repository evidence.

Security evidence without false certainty

Advisory refresh covers pinned npm, PyPI, Go, Maven/Gradle, and crates.io coordinates found in bounded repository manifests. A clean zero is allowed only when the current inventory matches a complete, current Online cache.

Malware review is static and bounded. It can identify evidence such as download-and-execute lifecycle scripts, reverse-shell patterns, decoded execution, miner indicators, credential-file reads, or suspicious exfiltration endpoints. It cannot prove execution, provenance, credential exposure, safety, or compromise.

Architecture contracts are validated locally before becoming active.

Report vulnerabilities privately through GitHub Security Advisories.

Architecture

The connector is a strict modular ports-and-adapters system:

policy
  └─ discovery adapters
       └─ security cache and evidence services
            └─ Online actions
                 └─ MCP composition and executable

policy: destination validation, version matching, inventory identities, and malware evidence rules;
discovery: bounded manifest and installed-package adapters;
security: atomic advisory state, cached matching, scanning, and reporting;
online-actions: capability, contract, advisory, preview, and sync use cases;
composition: extension registration, launcher, and stdio executable.

The checked-in architecture contract enforces zero runtime cycles, production files at or below 300 physical lines, and functions at or below 100 physical lines, with no exceptions and no violation baseline.

Development and release proof

npm ci --ignore-scripts
npm test
npm run verify:release
npm audit
npm pack --dry-run --json

The release gate verifies package identity, dependency ranges, exact installed versions, MCP Registry metadata, checked-in release notes, MIT licensing, the published file allowlist, and tag/version agreement. CI repeats the tests, security audit, and package dry-run on Node.js 24.

License

MIT. Weavatrix Online and its internal weavatrix-js runtime are independently versioned MIT-licensed packages.

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Weavatrix Online?

Does Weavatrix Online need an API key?

What transport does Weavatrix Online use?

When was Weavatrix Online last checked?

Documentation

Weavatrix Online

Choose the right Weavatrix package

Install and run

Plugins for Cursor, Codex, Claude, and Grok

Direct MCP launch

Codex

Claude Desktop

The seven Online tools

Typical workflows

Network and consent boundary

Configuration

Security evidence without false certainty

Architecture

Development and release proof

License