Skip to main content
Glama
raintr91

artifactgraph

by raintr91

artifactgraph

Standalone local MCP for any product repo: analyze specs/bullets vs local registries, suggest tags, confirm gaps, and run allowlisted codegen. Cloud only gets a small cloudPromptSlice.


Quick start

Linux / WSL

curl -fsSL https://raw.githubusercontent.com/raintr91/artifactgraph/main/install.sh | bash
cd /path/to/product
artifactgraph init                    # interactive wizard (no flags needed)
artifactgraph rebuild

init runs an interactive wizard — no options required. It walks two steps:

  1. Agents — checkbox multi-select (detected agents are pre-checked).

  2. Types — checkbox common / docs / fe / be / test / all (suggested by the detected stack).

Agent MCP config is always project-local under the current repo; the wizard does not ask for an install location. Flags (--target, --type, --yes, --location) are only for CI / non-interactive use — see docs/INIT.md.

Windows

irm https://raw.githubusercontent.com/raintr91/artifactgraph/main/install.ps1 | iex

Requires Node ≥ 22 (node:sqlite).


Related MCP server: Aedile

Standalone runtime

  • MCP is pinned to the repository where artifactgraph init ran.

  • Product tools use that repo directly; they do not require projectId, platform-repos.json, base-docs, or base-tests.

  • Config, lexicons, registries, generated harness files, and the SQLite index are project-local.

  • MCP package repositories do not ship or own workspace project maps.

The package installer does not initialize an arbitrary repository. Run artifactgraph init separately from each repo where ArtifactGraph is wanted.

Lane policy

  • Docs is the canonical registry/parity hub and the default ArtifactGraph home (--type=common,docs).

  • FE/BE/tests installs index that repo only and are useful only for local tag/allowlist hints.

  • ArtifactGraph never follows DOCSKIT_ROOT or CODEGENKIT_DOCS_ROOT. Codegenkit uses its docs pointer for canonical FE IR/registries; Docskit uses its own pointer for architecture ID lookups.


Versions (chọn bản)

Version

Dùng khi

Cách lấy

v1.0.0

Base / project nhỏ đang ổn với package cũ trên main tại thời điểm tag

git checkout v1.0.0 · hoặc pin install vào tag này

v2.0.1 (release/2.0.0)

v2 standalone runtime + contract-safe install manifest lifecycle

Branch/PR này · sau merge: main

v2.2.0

Init wizard 2 bước (agents → types, luôn project-local, không hỏi location) + .gitignore merge theo contract Platform DNA (manifest gitignore[], status báo thiếu, deinit giữ shared)

main mới nhất

# Giữ v1 (không nâng)
git clone … artifactgraph && cd artifactgraph && git checkout v1.0.0 && npm run build

# Thử v2
git checkout release/2.0.0 && npm run build && artifactgraph version   # → 2.0.1

Commands

Step

CLI

Wire agents + initialize/update current repo (interactive wizard)

artifactgraph init

Non-interactive init (CI; skips the wizard)

artifactgraph init --target=cursor --type=fe --yes

Remove unchanged stale harness assets

prune (dry-run) / prune --yes

Remove this repo's owned harness + local MCP

artifactgraph deinit [--yes]

Remove all tracked repos + MCP + CLI globally

artifactgraph uninstall [--yes]

Index registries

rebuild

Preflight

analyze / gaps / parity

Command recommendation

recommend-command --command … / allowlist-check --command …

Deprecated executable shim

gen --command … (2.x compatibility only; owning kit executes in next major)

install and init-project are deprecated compatibility aliases of init.

deinit is the inverse of init for one product repo. uninstall is global and may be run from anywhere: it removes every repo in the install ledger, repo-local and global MCP wiring, the CLI links/tree, and then the ledger. Both commands preview without changing files unless --yes is supplied; in a TTY they preview and ask for confirmation. Modified managed files are preserved and reported, and shared agent config files lose only their artifactgraph entries. Older installs can be found with:

artifactgraph uninstall --discover ~/workspace --yes

The ledger is stored at $ARTIFACTGRAPH_STATE_DIR/installs.json, $XDG_STATE_HOME/artifactgraph/installs.json, or ~/.local/state/artifactgraph/installs.json.


License

MIT

F
license - not found
-
quality - not tested
B
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

  • F
    license
    -
    quality
    C
    maintenance
    Enables natural language queries on technical specifications and automated code compliance checks using local RAG with vector search, integrated via MCP.
  • A
    license
    A
    quality
    B
    maintenance
    Enables AI coding assistants to analyze codebases locally before generating code, reducing duplication and enforcing architecture boundaries.
    1
    3
    MIT
  • F
    license
    -
    quality
    C
    maintenance
    Secure local development platform that exposes controlled developer capabilities (FS, Git, search, command execution) to AI assistants via MCP with deny-by-default security and audit logging.

View all related MCP servers

Related MCP Connectors

  • Cross-agent artifact workspace with provenance across Claude Code, Codex, Cursor, LangGraph.

  • Generate, audit, and maintain legal policies that match what your code actually does.

  • Reference data agents need before writing code: dependency advisories, API schemas, component specs.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/raintr91/artifactgraph'

If you have feedback or need assistance with the MCP directory API, please join our Discord server