Add Codex CLI plugin manifest

[internet-dot]

This adds a small metadata pass so the repo is easier to wire into Codex without touching runtime code.

I targeted this repo because it already exposes:

• MCP (Model Context Protocol) support for custom
• Use MCP servers to connect new capabilities, including
• Run non-interactively in scripts for workflow automation

It adds .codex-plugin/plugin.json, a starter .mcp.json, and the scanner workflow.
Permissions: read-only. No secrets. No publish. No runtime changes.
If you want different command wiring or metadata values, I can adjust the branch.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces the foundational configuration required to integrate the Gemini CLI as a Codex plugin. By adding the plugin manifest and MCP server definitions, the project gains the necessary metadata and command wiring to function within the Codex ecosystem.

Highlights

• Codex Plugin Integration: Added the necessary manifest file to register the project as a Codex plugin.
• MCP Configuration: Introduced the .mcp.json configuration file to define the command execution path for the Gemini CLI.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/codex-plugin-scanner.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces configuration files to integrate the Gemini CLI with the Codex and Model Context Protocol (MCP) ecosystems. Feedback highlights a critical path resolution error for the MCP configuration, a naming inconsistency with the project's scoped package name, and a significant protocol incompatibility where the interactive CLI entry point would interfere with MCP's JSON-RPC communication on stdout.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[gemini-code-assist]

The relative path to the MCP configuration file is incorrect. Since plugin.json is located in the .codex-plugin/ subdirectory and .mcp.json is in the repository root, the path should be ../.mcp.json to correctly resolve the file.

Suggested change

	"mcpServers": "./.mcp.json"
	"mcpServers": "../.mcp.json"

[gemini-code-assist]

The plugin name "gemini-cli" does not match the scoped package name defined in package.json ("@google/gemini-cli"). To avoid naming collisions in the Codex/MCP ecosystem and maintain consistency with the project's identity, it is recommended to use the full scoped name.

Suggested change

	"name": "gemini-cli",
	"name": "@google/gemini-cli",

[gemini-code-assist]

The command node bundle/gemini.js points to the main interactive CLI entry point. This entry point initializes a terminal UI (using the Ink/React framework) which outputs ANSI escape sequences and interactive prompts to stdout. This is incompatible with the Model Context Protocol (MCP), which requires stdout to be reserved exclusively for JSON-RPC messages. Using this entry point will cause protocol errors in MCP clients. Please point this to a dedicated non-interactive server entry point or ensure the CLI supports a flag (e.g., --mcp) that enables a pure MCP server mode.