DocGraph Agent Plugins

DocGraph Agent Plugins package DocGraph for agent/plugin ecosystems. This repository contains a Claude Code Plugin and a Codex Plugin that connect local agents to a running DocGraph HTTP MCP endpoint:

http://127.0.0.1:8787/mcp

DocGraph is a local-first document knowledge graph for enterprise documents and local agents. The plugin does not upload your documents to a SaaS service. Run one local docgraph serve process for the workspace, then let Claude Code or Codex connect to that process over MCP Streamable HTTP.

The first release is intentionally simple: install the DocGraph CLI yourself, make sure docgraph is on PATH, start docgraph serve, then install the plugin.

Repository Layout

docgraph-agent-plugins/
  .codex-plugin/plugin.json      # Codex submission artifact manifest
  .mcp.json                      # Default HTTP MCP config for artifact submission
  .mcp.stdio.json                # Optional stdio fallback config
  assets/                        # Icon and DocGraph UI screenshots for submission
  plugins/docgraph/              # Shared plugin package
    .mcp.json                    # Claude Code and Codex HTTP MCP config
    .mcp.stdio.json              # Optional stdio fallback config
    .codex-plugin/plugin.json    # Codex plugin manifest
    .claude-plugin/plugin.json   # Claude Code plugin manifest
    assets/                      # Icon and DocGraph UI screenshots
  .agents/plugins/marketplace.json
  .claude-plugin/marketplace.json
  docs/

The repository root is a valid Codex plugin artifact root. If a submission form expects .codex-plugin/plugin.json at the artifact root, submit this repository root or an archive created from it. The plugins/docgraph copy is retained for repo-local marketplace installs and Claude Code plugin compatibility.

Install DocGraph CLI

Install DocGraph from the main project:

• Main repository: https://github.com/gwork1883/docgraph

After installation, verify that the CLI is available:

docgraph --help

If your shell cannot find docgraph, add the CLI install directory to PATH, then restart Claude Code or Codex.

Start DocGraph

Open the workspace where your agent should use DocGraph and start a local server:

docgraph serve --data .docgraph --host 127.0.0.1 --port 8787

The server exposes MCP at http://127.0.0.1:8787/mcp.

That keeps the index scoped to the current workspace by default. Use a separate .docgraph directory per workspace when you want separate indexes.

Add Document Sources

Use the DocGraph CLI or DocGraph UI from the main project to add document sources such as local documentation, internal docs, or other supported connectors.

For the first plugin release, source management stays in DocGraph itself. The plugins only provide agent access through MCP.

Sync Documents

Sync your configured sources in DocGraph before asking an agent to search or reason over them. The local .docgraph directory stores the graph and indexes used by MCP tools.

After sync, the MCP server exposes tools including:

• doc_search
• doc_context
• doc_get_node
• doc_get_section
• doc_related
• doc_impact

Install The Claude Code Plugin

The Claude Code plugin package is in plugins/docgraph.

For local development, add this repository as a Claude Code plugin marketplace, then install the docgraph plugin from that marketplace. The plugin package includes .claude-plugin/plugin.json and a root .mcp.json file. The repo-level Claude marketplace file is:

.claude-plugin/marketplace.json

TODO: Before publishing, verify the current Claude Plugin Hub submission and marketplace commands in the official Claude Code plugin docs:

• https://docs.anthropic.com/en/docs/claude-code/plugins
• https://docs.anthropic.com/en/docs/claude-code/plugin-marketplaces

Install The Codex Plugin

For local marketplace testing, the Codex plugin package is in plugins/docgraph. For artifact submission, the repository root also contains the required .codex-plugin/plugin.json and matching root assets.

The repo-level Codex marketplace file is:

.agents/plugins/marketplace.json

Install or add this marketplace in Codex according to the current Codex plugin workflow, then enable the docgraph plugin. The plugin manifest points Codex to ./.mcp.json, which connects to http://127.0.0.1:8787/mcp.

To create a submission archive whose root contains .codex-plugin/plugin.json:

git archive --format=zip --output docgraph-codex-plugin.zip HEAD
unzip -l docgraph-codex-plugin.zip | head -30

Verify MCP Tools

First verify the HTTP MCP endpoint outside the agent host:

curl -s http://127.0.0.1:8787/api/health

Then enable the plugin in Claude Code or Codex and ask the host to list or use DocGraph MCP tools. At minimum, verify that doc_search is visible and can search a synced local index.

If docgraph serve is not running, the plugin can still install, but the agent host cannot initialize the DocGraph MCP server at http://127.0.0.1:8787/mcp. In that state DocGraph tools may be missing from the session, or tool calls may fail with a local connection error. Start docgraph serve and open a new Claude Code or Codex session.

FAQ

Does the plugin upload my documents?

No. The plugin connects to a local DocGraph HTTP MCP endpoint. Your documents and indexes stay in the local .docgraph data directory unless you separately configure DocGraph connectors or services that access network sources.

Does the plugin install DocGraph CLI?

No. The first release does not download, bundle, or update binaries. Install DocGraph CLI separately and put docgraph on PATH.

Why does the MCP server fail with command not found?

The agent host cannot find docgraph. Install DocGraph CLI or fix PATH, then restart Claude Code or Codex.

Why are DocGraph tools missing or connection refused?

The local DocGraph HTTP server is not running or is listening on a different port. Start it from the workspace that owns the .docgraph data directory:

docgraph serve --data .docgraph --host 127.0.0.1 --port 8787

Then start a new Claude Code or Codex session so the MCP connection is initialized again.

Which data directory does the plugin use?

By default DocGraph uses .docgraph in the workspace where you start docgraph serve.

Can I change the data directory?

Yes, but do it intentionally by starting docgraph serve with the desired --data directory or config file. The default plugin package connects to http://127.0.0.1:8787/mcp.

Why prefer HTTP MCP over docgraph mcp --data .docgraph?

HTTP MCP lets one long-running DocGraph server own the workspace data directory, Web UI, REST API, sync jobs, and MCP endpoint. Starting a separate docgraph mcp --data .docgraph process for each agent can make Claude Code, Codex, and the Web UI read or write the same SQLite store concurrently. The stdio config is still included as .mcp.stdio.json for isolated fallback testing, but the default plugin path uses HTTP.

Release Preparation

Use this doc before publishing:

• Install guide