GraphyLoop

Name: GraphyLoop
Author: chadixearth

by chadixearthversion 0.6.5i★ –iRuns on your computer

Registry nameio.github.chadixearth/graphyloop

Install

Overview

Description from the maker (original English)

Workflow planner, wave dispatcher, persistent swarm memory, and deploy preflight for AI agents.

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: Search & AI memory

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": {
    "graphyloop": {
      "command": "npx",
      "args": [
        "-y",
        "graphyloop",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add graphyloop -- npx -y graphyloop mcp

Open in Cursor

Or copy the settings yourself

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

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

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": {
    "graphyloop": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "graphyloop",
        "mcp"
      ]
    }
  }
}

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 chadixearth, 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 Search & AI memoryi

More stars than 0% of the other 7256 servers in this category
Published to the registry more recently than 87% of the other 7256 servers in this category
Basic checks equal to or better than 100% of the other 7256 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 GraphyLoop 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.6.5) reached the registry 5 days 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: Context7, Codebase Memory, Exa

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

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated today

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

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.

GraphyLoop

GraphyLoop is a one-command agentic workflow kit for AI coding agents: it wires Claude Code, OpenCode, Codex, Cursor, Gemini CLI, Oh My Pi and DeepSeek Harness with Workflow v3 (inline-first, one parallel wave, proof before done), a 25-agent squad, persistent memory, Agent Skills and an MCP server. It also ships as a Claude Code plugin and an MCP Registry server. Zero dependencies.

Landing page · npm · Harness guide · Reference · llms.txt

Quick Start

Pick one of three install channels:

1. `npx` installer (all 7 harnesses)

npx graphyloop        # a bare command installs — it wires every harness it detects

restart your harness, open a real project, then ask your agent:

/chadi-init

Requires Node.js ≥ 20. On a fresh machine with no harness yet, GraphyLoop wires all seven so you are ready whichever one you open first. Target specific ones with --harness claude,omp. Nothing is written into your workspace — everything lives in your home config (~/.graphyloop/ plus each harness's own directory).

2. Claude Code plugin marketplace

Inside Claude Code:

/plugin marketplace add chadixearth/graphyloop

/plugin install graphyloop@graphyloop

then start the workflow with:

/graphyloop:chadi-init

The marketplace manifest is .claude-plugin/marketplace.json and the plugin lives at integrations/claude-code/ (15 /graphyloop:chadi-* commands, 26 agents, 3 core skills, and the graphyloop MCP server). Use the plugin OR `npx graphyloop --harness claude` for Claude Code, not both (installing both registers duplicate tools and agents).

3. MCP Registry

Server name: `io.github.chadixearth/graphyloop` (server.json). Any MCP client that resolves from the official MCP Registry runs the graphyloop npm package over stdio via:

npx -y graphyloop mcp

Supported harnesses

Harness	`--harness`	Detected when	How GraphyLoop wires it	Start the workflow
OpenCode	`opencode`	`~/.config/opencode/`	plugin (`graphyloop_` tools) + 26 agents + 15 `/chadi-` commands + AGENTS.md	`/chadi-init`
Claude Code	`claude`	`~/.claude/` or `~/.claude.json`	MCP server + 26 agents + 15 commands + `~/.claude/rules/graphyloop-workflow.md` (or install the Claude Code plugin instead)	`/chadi-init` (plugin: `/graphyloop:chadi-init`)
Codex	`codex`	`~/.codex/`	MCP server + 15 prompts + bundled skills in `~/.agents/skills/` + AGENTS.md	`/prompts:chadi-init`
Cursor / Windsurf	`cursor`	`~/.cursor/`	MCP server + bundled skills in `~/.agents/skills/` (workflow loads from `graphyloop-workflow` skill; project init writes `/AGENTS.md`)	ask: "run the graphyloop workflow init"
DeepSeek Harness	`dsh`	`~/.dsh/` or `$DSH_HOME`	MCP server + 26 role prompts + `graphyloop-squad` skill + AGENTS.md	load the `graphyloop-squad` skill
Oh My Pi	`omp`	`~/.omp/`	MCP server in `~/.omp/agent/mcp.json` + 26 squad agents + skills; AGENTS.md only if you have none	ask: "run the graphyloop workflow init"
Gemini CLI	`gemini`	`~/.gemini/`	MCP server in `~/.gemini/settings.json` + `/chadi-*` TOML commands + bundled skills in `~/.gemini/skills/`; GEMINI.md only if you have none	`/chadi-init`

Per-harness file locations, verification, dsh notes, and the Gemini CLI sign-in change (personal Google sign-ins stopped working on June 18, 2026; an API key still works): docs/harnesses.md.

Setup with any AI assistant (copy-paste)

Paste the block below into your AI harness — it installs, verifies (GRAPH_LOOP_DOCTOR_OK), and reports on its own. Raw copy: docs/SETUP-PROMPT.md.

You are setting up GraphyLoop (github.com/chadixearth/graphyloop, npm package `graphyloop`) — a one-command agentic workflow kit for AI coding agents: a 25-agent squad, parallel wave planning, persistent memory, a harness-neutral workflow and an MCP server that works in any harness. Zero dependencies.

Goal: install it for THIS machine's harness(es), verify the install actually works, and report. Do NOT edit any config file by hand — run only the installer. Do NOT run npm publish, npm login, or anything unrelated.

Steps:

Prerequisites:

Run node --version — must be 20 or newer. If older, tell the user to install Node.js 20+ and stop there.
Detect which harnesses exist on this machine (check for any of): ~/.config/opencode/ (OpenCode), ~/.claude.json or ~/.claude/ (Claude Code), ~/.codex/ (Codex), ~/.cursor/ (Cursor / Windsurf), ~/.dsh/ or $DSH_HOME (DeepSeek Harness / dsh), ~/.omp/ (Oh My Pi / omp), ~/.gemini/ (Gemini CLI). On Windows, ~ = %USERPROFILE%.

Install:

Run: npx --yes graphyloop (a bare graphyloop is the install command: it wires every detected harness, or all 7 on a fresh machine.)
To target specific harnesses: npx --yes graphyloop --harness claude,omp (names: opencode, claude, codex, cursor, dsh, omp, gemini)
Optional Claude Code plugin path (use the plugin OR npx graphyloop --harness claude, not both): inside Claude Code run /plugin marketplace add chadixearth/graphyloop then /plugin install graphyloop@graphyloop.
If npx asks "Ok to proceed?", answer yes. If npx is missing, stop and tell the user to install Node.js 20+ (npx ships with npm).

Verify — every applicable check must pass:

npx --yes graphyloop doctor prints one row per harness (present / wired) and its LAST line must be GRAPH_LOOP_DOCTOR_OK. If it prints GRAPH_LOOP_DOCTOR_ISSUES , run the fix: command it shows for each unwired row, then run doctor again.
Core engine files exist: ~/.graphyloop/graphyloop/cli.mjs , ~/.graphyloop/mcp-server.mjs , ~/.graphyloop/lib/mcp.mjs , ~/.graphyloop/lib/engine.mjs .
OpenCode (if present): ~/.config/opencode/opencode.json contains plugin entries "./plugins/graphyloop/plugin.js" and "./plugins/server-guard/plugin.js", and ~/.config/opencode/agents/ contains 26 .md files.
Claude Code (if present): ~/.claude.json has an mcpServers.graphyloop entry, ~/.claude/rules/graphyloop-workflow.md exists, and ~/.claude/agents/ is populated (unless using the Claude Code plugin instead).
Codex (if present): ~/.codex/config.toml contains a [mcp_servers.graphyloop] section, and ~/.agents/skills/graphyloop-workflow/SKILL.md exists.
Cursor (if present): ~/.cursor/mcp.json has a "graphyloop" entry, and ~/.agents/skills/graphyloop-workflow/SKILL.md exists (Cursor uses no home rules file; the workflow loads from ~/.agents/skills/graphyloop-workflow).
DeepSeek Harness (if present): ~/.dsh/cordis.patch.yml contains a row id: graphyloop-mcp naming '@deepseek-ai/dsh-mcp-client', ~/.dsh/AGENTS.md exists, and ~/.dsh/skills/ holds graphyloop-squad. Optional deeper check: dsh --profile headless --dump-config prints that row. In dsh the tools are namespaced — call them as mcpgraphyloop (e.g. mcpgraphyloopswarm_state).
Oh My Pi (if present): ~/.omp/agent/mcp.json has mcpServers.graphyloop, and ~/.omp/agent/agents/ holds the squad .md files. An existing ~/.omp/agent/AGENTS.md is intentionally kept — the workflow then loads from the bundled skill graphyloop-workflow.
Gemini CLI (if present): ~/.gemini/settings.json has mcpServers.graphyloop, ~/.gemini/commands/chadi-init.toml exists, and graphyloop-workflow/SKILL.md exists in ~/.gemini/skills/ (or ~/.agents/skills/ when Codex/Cursor is also installed). An existing ~/.gemini/GEMINI.md is intentionally kept.
If any check fails: re-run the install with --force (automatic backups) and re-verify. Still failing? Report the exact error and stop.

Wrap up: tell the user to RESTART their harness (close/reopen the terminal or editor), open a real project (not their home directory), and start the workflow: ask for /chadi-init (OpenCode, Claude Code, Gemini CLI — or /graphyloop:chadi-init with the Claude Code plugin), /prompts:chadi-init (Codex), or "run the graphyloop workflow init" (Oh My Pi, Cursor, Windsurf). In the DeepSeek Harness there are no slash commands: ask the agent to load the graphyloop-squad skill instead. Give a one-line summary of what was installed.

Do not ask permission for reversible steps — proceed. Stop only for: Node < 20, an install failure, or a prompt you cannot answer.

How the workflow works

Workflow v3 is harness-neutral: the same 12 rules run in OpenCode, Claude Code, Codex, Cursor, Windsurf, DeepSeek Harness, Oh My Pi and Gemini CLI.

flowchart LR

A[Recall memory_search] --> G0[Goal + proof state what & check] G0 --> B{Size the work} B -- "inline ≤ 8 known files" --> I[Inline edit any mix of layers] B -- "2+ independent slices (~5+ min each)" --> C[ctx pack + contract ctx-slug.md + contract-slug.md] C --> D[One wave 1–3 lanes, driver keeps a slice] D --> E[Proof, not claims run it, real browser / URL] I --> E E --> F[Report Changed / Files / Verified / Skills / Blocked] F --> G[Record memory_store + why & commit/PR]

Recall first, record last — memory_search before planning; memory_store one dense line after, including the *why* and the commit/PR it landed in.
Goal + proof up front — state the end state, the measurable check that proves it, and the invariant it must not break ("prompt the what, not the how"; never weaken a test to make it pass).
Inline first (measured) — up to 8 known files in any mix of layers, when the code is known or mappable in one batched read pass; a dispatch costs the driver minutes of waiting while an inline edit costs seconds.
Fan out only for 2+ independent slices of about 5+ minutes each — 1–3 lanes (max 4), strictly disjoint files; the driver keeps the largest or most coupled slice and builds it while lanes run.
Context pack before dispatch — write ctx- .md (path:line, current code, pattern to copy) so lanes start editing instead of rediscovering.
Freeze the contract — contract- .md is the only cross-lane dependency.
Turn economy — batch reads, first edit by turn 5, done in about 20 turns (40+ = mis-sized).
Isolate what collides — a lane that runs servers, databases or browsers gets its own wor

Only the beginning is shown; read the rest in the repo

GraphyLoop

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 Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

GraphyLoop

Quick Start

1. npx installer (all 7 harnesses)

restart your harness, open a real project, then ask your agent:

2. Claude Code plugin marketplace

then start the workflow with:

3. MCP Registry

Supported harnesses

Setup with any AI assistant (copy-paste)

How the workflow works

1. `npx` installer (all 7 harnesses)