Use GPDoc with Codex and Claude Code

GPDoc provides one repository-owned plugin for Codex and Claude Code. Both clients use the same GPDoc MCP server and shared skill so an agent can work with Markdown and GPDoc files in the active workspace.

What the plugin can do

• Open or create Markdown and GPDoc files in the active workspace.
• Read and edit source without converting plain Markdown into a closed format.
• Preserve GPDoc front matter, file identity, comments, and suggestions.
• Add reviewable comments or suggestions when the selected workflow calls for review.
• Share a file only after an explicit user request and GPDoc account authentication.

Local editing does not require a GPDoc account or sign in. Sharing requires a GPDoc account and a device login because it creates or updates an online shared file.

Install from the repository marketplace

The plugin is available from the GPDoc repository. From a local checkout, add its repository marketplace and install the gpdoc@gpdoc package.

Codex

codex plugin marketplace add /path/to/gpdoc
codex plugin add gpdoc@gpdoc

Claude Code

claude plugin marketplace add /path/to/gpdoc
claude plugin install gpdoc@gpdoc

For plugin development, Claude Code can also load the local package with claude --plugin-dir ./plugins/gpdoc.

Use the plugin

Ask Codex or Claude Code to open a workspace file in GPDoc, review selected Markdown, add a suggestion, or share a file. Codex can render the MCP App when the host supports it. Claude Desktop can return a local preview URL. A host without a graphical surface can still use the file tools.

The GPDoc MCP server stays scoped to the active workspace. It does not place reusable tokens, secrets, or credentials in document source, public URLs, or agent messages.

Other file workflows

Provider transfers, source-control storage, and website publishing are file workflows, not Codex or Claude plugin integrations. See Export, share, and publish GPDoc files for those actions.