NV oOS Content Graph

NV oOS Content Graph transforms your WordPress content into a visual knowledge graph — organized, searchable, and interactive. Every post, page, category, tag, and author becomes a node; every relationship becomes an edge.

No API keys. No AI required. The core graph engine runs entirely on your WordPress server using your existing content. Optional remote sources (like Wikidata) are opt-in — see External services below.

What You Get

One-Click Graph Builder

Click “Build Graph” and ~10-30 seconds later, your entire site becomes a visual graph. Supports incremental rebuilds and scheduled cron updates.

Interactive Graph Explorer

Explore your content visually using Cytoscape.js. Search for nodes by label, click for details, zoom and pan. Color-coded by content type (posts, pages, terms, users).

Visual Theming & Styling

Style the graph to match your brand from the new Appearance tab: dark, light, auto, and WordPress-admin themes; per-type colors and icons (colorblind-safe defaults with automatic WCAG 2.2 contrast correction); color-by-type/community/degree modes; an interactive legend; edge style presets; layout presets; a minimap; keyboard navigation; hover focus with quick-info tooltips; optional directional edge-flow animation; and theme-aware PNG export. See docs/visual-theming.md.

Content Gap Analysis

Discover orphan content (no internal links), thin topic clusters, and missing link opportunities. Generate actionable content strategy recommendations.

Six Export Formats

Download your graph as JSON (NetworkX), GraphML (Gephi/yEd), CSV, Neo4j Cypher, Obsidian vault, or standalone HTML page.

Schema.org JSON-LD

Automatic structured data injection for SEO — taxonomy terms as about and internal links as relatedLink.

Related Content Widget

Appends graph-neighbor posts to your content based on knowledge graph proximity.

REST API

Full programmatic access with 19 endpoints. Read endpoints require the read capability (all logged-in users), a valid assistant credential (Authorization: Bearer cred_XXXXX.SECRET, issued by the NV oOS base plugin when installed), or a valid guest token (guest tokens are provided by the NV oOS base plugin when installed); write endpoints require manage_options.

Extensible Tool System

14 built-in tools for graph operations: query, search, traverse, analyze, export. Addon plugins can register their own tools.

Addon Ecosystem (all optional)

• nvoos-content-graph-ai — AI chat assistant with 13 AI providers, AI tools, embeddings, RAG, and agent memory
• nvoos-content-graph-ai-platform — agents, skills, slash-commands, professions, A2A, ACP, and federation

Privacy Notice

This plugin does not collect, store, or transmit any personal data by default. The core graph engine runs entirely on your WordPress server using your existing content.

Remote Sources (opt-in only): When you explicitly configure a remote source driver (e.g. Wikidata, REST API, RSS feed), the plugin sends HTTP requests to the URLs you provide. No data is sent off-site without your explicit setup. Remote source credentials (API keys, tokens, passwords) are stored in the database encrypted with AES-256-GCM via the OpenSSL PHP extension, falling back to base64 encoding with an admin warning when OpenSSL is unavailable.

Optional AI Addons: The companion plugin nvoos-content-graph-ai (not included in this plugin) sends content to third-party AI providers (OpenAI, Google Gemini, etc.) when configured. Refer to that addon’s documentation for its privacy policies.

External services

This plugin does not require any external service for its core functionality. All graph data is computed and stored on your own WordPress server.

Wikidata (wikidata.org)

The optional “Resolve External Entity” tool and the Wikidata remote-source driver query the Wikidata API (https://www.wikidata.org/w/api.php) — only when you explicitly request an entity lookup by QID (e.g. Q42) or configure a Wikidata source.

• What is sent: the QID or entity identifier you provide, plus standard HTTP request metadata (your server’s IP address, user agent).
• When: only on your explicit request; never automatically or in the background.
• What it is used for: fetching the entity’s label, description, and sitelinks so it can be ingested as a graph node.
• Service provider: Wikimedia Foundation — Terms of Use: https://foundation.wikimedia.org/wiki/Policy:Terms_of_Use — Privacy Policy: https://foundation.wikimedia.org/wiki/Policy:Privacy_policy

User-configured remote sources (opt-in only)

When you configure a remote source driver (REST API, RSS/Sitemap feed, SPARQL endpoint, webhook receiver, etc.) in Settings, the plugin sends HTTP requests to the URLs you provide. What is sent depends entirely on the endpoint you configure. These requests happen only when you manually trigger a sync, schedule one, or receive a webhook. Remote source credentials (API keys, tokens, passwords) are stored in the database encrypted with AES-256-GCM via the OpenSSL PHP extension.

Stripe payments (opt-in only)

The “Get NV oOS Complete” buttons on the plugin’s settings page open an optional checkout for the NV oOS Complete plugin bundle — the full NV oOS plugin (base + Pro) installed as a separate plugin. Card and payment details are entered directly on Stripe’s servers (js.stripe.com iframe); the plugin never stores or transmits card data. Stripe.js is loaded only when the purchase modal is opened — merely visiting the settings page contacts no third party. The checkout is created and verified by the vendor’s own server, operated by NV Digital Solutions on behalf of NV Digital Unlocked LLC (the seller of record); this plugin only sends the product name, your site URL, the Stripe payment ID, the purchasing administrator’s email address, the buyer’s declared country, and a timestamp recording your agreement to the Terms of Service to that service. For buyers in the EU, a billing address (street, city, optional postal code) is collected in the modal, attached to the payment for VAT records, and shown to the vendor on the license. A local purchase record (license key, payment ID, price paid, the purchasing administrator’s email address, country, and the consent timestamp) is stored after the vendor confirms the payment. Payment is entirely optional — the core plugin is fully functional without it.

• Service provider: Stripe, Inc. — Privacy Policy: https://stripe.com/privacy

Installing the NV oOS Complete bundle (manual install is the primary path)

After a successful purchase you can download the NV oOS Complete ZIP and install it manually via Plugins → Add New Plugin → Upload Plugin — this is the recommended, fully transparent path. The plugin also offers an optional automatic installation (a convenience that downloads the ZIP and runs WordPress’ built-in installer for you). Either way, the ZIP comes from a signed, short-lived URL provided by the vendor’s checkout service (which serves the package from the project’s GitHub release page, github.com). No data is sent to GitHub.

Free base version download

The purchase modal also offers a “Get the free NV oOS base version — no payment required” link. It opens the project’s GitHub release page (github.com/nvdigitalsolutions/mcp-ai-wpoos) in a new browser tab so you can download the free base plugin yourself. The link is fetched entirely by your browser — the plugin sends no data to GitHub and contacts no server when the link is shown.

Third-Party Libraries

This plugin bundles the following open-source libraries:

• Cytoscape.js v3.28.1 — MIT License — https://github.com/cytoscape/cytoscape.js
• cytoscape-fcose v2.2.0 — MIT License — https://github.com/iVis-at-Bilkent/cytoscape.js-fcose
• layout-base v2.0.1 — MIT License — https://github.com/iVis-at-Bilkent/layout-base
• cose-base v2.2.0 — MIT License — https://github.com/iVis-at-Bilkent/cose-base

All libraries are served locally from assets/vendor/ and never loaded from third-party CDNs. Each library’s license text ships alongside it (assets/vendor/<name>/LICENSE).