Repovine

Name: Repovine
Author: legann

by legannversion 0.1.1i★ –iRuns on your computer

Registry nameio.github.legann/repovine

Install

Overview

Description from the maker (original English)

Checkout-local repository context graph over MCP; `npx repovine setup` wires skills, agents, hooks.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Online shops & payments

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "repovine": {
      "command": "npx",
      "args": [
        "-y",
        "repovine"
      ]
    }
  }
}

Run this in your terminal

claude mcp add repovine -- npx -y repovine

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "repovine": {
      "command": "npx",
      "args": [
        "-y",
        "repovine"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "repovine": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "repovine"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account legann, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Online shops & paymentsi

More stars than 0% of the other 2534 servers in this category
Published to the registry more recently than 22% of the other 2534 servers in this category
Basic checks equal to or better than 100% of the other 2534 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Repovine safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spree Commerce: open-source B2B and marketplace ecommerce

by spree

Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.

Runs in the cloud★ 15,812BSD-3-ClauseUpdated 8 days ago

Install

Stripe MCP

by stripe

Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.

Runs in the cloud★ 2,043MITUpdated 12 months ago

Install

MCP Cn Commerce

by TonyWang-hub

8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending

Runs on your computer★ 96MITUpdated 28 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

repovine

Repository context assembled and conveyed to coding agents.

The repository knowledge layer

A repository-agnostic core. Across supported languages, frameworks, and infrastructure formats, repovine normalizes repository structure into one queryable model.

Contract boundaries by design. The graph connects repository units through shared code, template, and runtime contracts. These boundaries support repository-scale navigation, dependency impact, runtime flow, and configuration.

Versioned knowledge with explicit ownership. Version-controlled annotations attach intent, invariants, risks, and operational knowledge to graph nodes. Agents and developers author them; repovine checks freshness and structural consistency against repository state.

Together, these layers support intent-driven, context-compiled, contract-verified development. Task intent guides MCP context assembly, and observable claims are checked against repository state.

Checkout-local by design. The live graph and indexes are built from each checkout's working tree and run in memory. Configuration and authored knowledge travel through Git. No database is required.

Benchmarks. Across correctness and restraint tasks drawn from public software repositories, 90% of Repovine runs passed their case-specific diff gate, compared with 10.6% of baseline runs. Explore the results.

Quick start

Start in an existing repository:

npx repovine setup claude # or codex, cursor, all

setup connects the selected client to repovine, adds repovine skills, hooks, and instructions, and builds the repository graph.

The graph model

repovine deterministically derives a graph of cross-unit contracts from repository state. Source and infrastructure plugins translate stack-specific structures into the same vocabulary of packages, modules, exported symbols, templates, runtime resources, and their relationships—so navigation, dependency impact, runtime flow, and configuration work consistently across supported stacks. Explore the design rationale.

How it works

The engine and MCP provide the base workflow. Interactive clients use it directly. For explicit protocol runs, Delivery Protocol adds a structured assignment → result → compliance contract around the same workflow.

Client

In clients such as Claude Code, Codex, or Cursor, the agent uses repovine MCP directly while the developer stays in the loop.

graph LR

SRC["sources"] --> S1["Stage 1: gather facts"] S1 --> S2["Stage 2: build graph"] S2 --> ANN["versioned annotations on graph nodes"] A["agents and developers"] --> ANN S2 --> S3["Stage 3: build search index"] ANN --> S3 S3 --> MCP["MCP tools"] ANN --> MCP MCP -->|"bounded context"| C["Cursor, Claude Code, or Codex"]

Stage	Input	Output
Stage 1: gather facts	sources	exports, imports, env names, routes, infra
Stage 2: build graph	facts	packages → modules → symbols; infra/template/domain edges
annotations	graph + agent/developer writes	versioned intent, invariants, risks, side effects, and operational constraints
Stage 3: build search index	graph + annotations	token index; optional embeddings to assist fuzzy search
MCP	graph + annotations + index	bounded graph and annotation query results

Delivery Protocol

Delivery Protocol defines the assignment → structured result → compliance report contract. Core owns the schemas, projections, and validators that ground the protocol in observable repository state.

The agent uses MCP to access repository context while it works. The repovine CLI validates the assignment and result and produces the compliance report.

graph LR

IN["assignment"] --> AV["assignment validation"] AV --> A["agent"] A <-->|"repository context during the run"| MCP["repovine MCP"] A --> R["structured result"] AV -->|"validated assignment"| V["repovine compliance validation"] R --> V S["observable repository state + recorded context"] --> V V --> OUT["compliance report"]

repovine validates schema conformance, assignment linkage, and claims it can recompute from the graph, annotations, recorded MCP context, and an optional revision delta. The compliance report covers protocol conformance and repository grounding; behavioral correctness and merge readiness are outside the protocol's scope.

The runnable LangGraph harness demo applies the protocol in an end-to-end agent workflow. Its orchestration topology, sandbox, retries, worktree isolation, and provider behavior are demo-specific implementation choices. See the Delivery Protocol integration guide.

MCP tools

Each tool returns a scoped, structured response.

Query tools, with typical questions for a large repository:

Group	Example question	Tools
Navigate	where is authentication? what is inside the billing package?	`search_context`, `map_context`, `inspect_node`
Runtime	what are the entrypoints? how does an order flow through services?	`get_entrypoints`, `trace_flow`
Contracts & config	which consumers are affected by an API change? which environment variables does the worker read?	`analyze_dependencies`, `get_config_surface`
Architecture	are there boundary violations or god modules?	`analyze_architecture`

Maintenance tools service the graph and annotations:

Group	Purpose	Tools
Memory	which nodes are annotated or stale?	`get_annotation_status`, `write_annotation`, `merge_annotations`, `validate_annotations`, `get_annotation_merge_status`
Sync	rebuild and check the graph	`refresh_context`, `get_build_status`, `get_context_session_quality`
Domains	tune the domain config	`suggest_domains_config`
Declines	dismiss reviewed advisory items	`decline_advisory` (kind: `domains-config` \	`carrier-link-gaps`)

Setup and CLI

setup adds the following repovine integrations to the workspace while preserving existing configuration and project specialists:

Integration	Included
MCP server	the repovine MCP tools
Skills	`repovine-workflow`, `repovine-annotations`, `repovine-refresh`, `repovine-review`, `repovine-status`
Subagents	`repovine-repo-explorer`, `repovine-annotation-writer`, `repovine-architecture-auditor`, `repovine-code-reviewer`
Hooks	pre-edit boundary notice, post-edit stale-graph notice, session-start "MCP first" reminder
Instructions	`AGENTS.md` (Cursor uses `.cursor/rules`)

Command	Goal
`npx repovine`	run the stdio MCP server outside an IDE/CLI client
`npx repovine setup cursor` (or `claude`/`codex`/`all`)	add the integrations above, then build the graph
`npx repovine build`	build the graph
`npx repovine status`	graph / config / annotation health
`npx repovine doctor`	diagnose the workspace integration
`npx repovine clear`	remove repovine-managed workspace files
`npx repovine --version` · `--help`	version / help
`npx repovine delivery --help`	harness/CI Delivery Protocol commands: descriptor, manifests, run brief, validation, and compliance
`npx repovine agents --help`	harness/CI utilities for repository roles, deterministic orientation, and context-session quality

STDIO is the only supported MCP transport in v1. For remote, devcontainer, WSL, VM, or devbox use, launch the repovine subprocess inside that environment so it runs in the checkout being analyzed.

Supported stacks

Area	Support
Languages	First-class support: TypeScript (JS/JSX via the TS toolchain, needs `tsconfig.json`); Python partial (backend routes + server-rendered templates)
Frameworks	React, Next.js, Nuxt, SvelteKit, Angular, NestJS, serverless monorepos; Vue/Svelte single-file components (script blocks only)
IaC	Partial, expanding coverage: SAM/CloudFormation, Terraform, Kubernetes, Helm, Dockerfile, docker-compose, Vercel

IaC parsers turn infra files into runtime-resource nodes plus links to the code and images behind them. They cover selected resources and relationships rather than complete format schemas. Coverage is under active development, and extending the existing extractors is a contribution area. Design detail: DESIGN.md.

Requires Node.js 22+ and one indexable root: tsconfig.json, pyproject.toml/setup.py (needs python3), or IaC files. Repositories with supported IaC files can be indexed without a source project; the graph contains infrastructure modules and runtime resources, but no code modules.

Repository files

File / dir	Git	Role
`repovine.config.json`	commit	main config: graph build and MCP output
`repovine.domains.json`	commit	logical organization of the repository graph
`repovine.annots.json`	commit	semantic annotation memory
`.repovine/`	ignore	local engine cache and workspace state

Defaults work for most TypeScript repositories. Config reference: docs/workspace-files.md.

Status

Preview (0.1.0), usable today and open to contributions. The graph schema and @repovine/plugin-sdk still change.

Contribute

repovine's plugin architecture provides two public producer surfaces for extending language and infrastructure coverage, both exposed by @repovine/plugin-sdk:

Plugin	What it adds
Language source producer	a language: source files → modules, imports, exports, semantic hints
IaC parser	an infra format: files → runtime-resource nodes and links

Built-in and third-party producers share the same public plugin contracts; core validates their output and owns graph identities and ontology. See the plugin guide and runnable Go source plugin, IaC plugin, and other examples.

Learn more

DESIGN.md: system boundaries, graph contract, trust model, and limitations
CONTRIBUTING.md: dev setup, quality gates
Documentation: guides, references, and the TODO app walkthrough
Platform support: per-surface OS tiers, prerequisites, and promotion rules
examples: runnable plugins and the Delivery Protocol harness demo

License

MIT. See LICENSE.

Repovine

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Online shops & paymentsi

Common questions

Alternatives

Spree Commerce: open-source B2B and marketplace ecommerce

Stripe MCP

MCP Cn Commerce

README from the maker

repovine

The repository knowledge layer

Quick start

The graph model

How it works

Client

Delivery Protocol

MCP tools

Setup and CLI

Supported stacks

Repository files

Status

Contribute

Learn more

License