> Graphify: shared context of codebase for agents and developers. Canonical: https://graphify.com/blog/best-codex-plugins · Full index: https://graphify.com/llms-full.txt

# Best Codex plugins in 2026, picked by job

*November 21, 2026 · Syed Fahad*

The best Codex plugins are the few that match work you do every week. A plugin bundles MCP servers and skills into one install, so a good one gives Codex a new ability in a minute. For review, try CodeRabbit or Greptile. For errors, Sentry. For issues, Linear. For backend and deploys, Supabase, Vercel or Cloudflare. For library docs, Context7. For a large codebase, Graphify.

I checked every install path below against each vendor's own docs on 21 November 2026. Plugin catalogs move fast, so if a command here stops working, the linked vendor page wins.

## How do you install a Codex plugin?

Start Codex and open the plugin browser:

```text
codex
/plugins
```

Run `/plugins` in Codex CLI, or open the **Plugins** tab in ChatGPT. Search for the plugin, open it and install. Codex and ChatGPT share one plugin directory, so a plugin you find in one is the same listing in the other. Start a new session after you install, so the plugin's tools and skills load. OpenAI's [plugins guide](https://learn.chatgpt.com/docs/plugins) has the details.

Two things catch people out:

- **Some plugins live in the vendor's own marketplace.** You add that marketplace first with `codex plugin marketplace add owner/repo`, then install with `codex plugin add`. Greptile, Sentry and Context7 document it that way.
- **The Codex IDE extension doesn't support plugins yet.** In your editor, add the tool's MCP server with `codex mcp add`. The CLI and the extension read the same `~/.codex/config.toml`, so you set it up once. Our guide to [adding an MCP server to Codex](/blog/how-to-add-an-mcp-server-to-codex) covers that path.

## Best Codex plugins at a glance

| Job | Plugin | Install in Codex | Source |
| --- | --- | --- | --- |
| Review your changes before a PR | CodeRabbit | `/plugins`, search CodeRabbit (needs the CodeRabbit CLI) | [CodeRabbit docs](https://docs.coderabbit.ai/cli/codex-integration) |
| Read PR reviews, review a branch | Greptile | `codex plugin marketplace add greptileai/skills` | [Greptile docs](https://www.greptile.com/docs/integrations/codex) |
| Debug production errors | Sentry | `codex plugin marketplace add getsentry/plugin-codex` | [getsentry/plugin-codex](https://github.com/getsentry/plugin-codex) |
| Read and update issues | Linear | `/plugins`, or `codex mcp add linear` | [Linear docs](https://linear.app/integrations/codex-mcp) |
| Database, auth, Edge Functions | Supabase | `/plugins`, or `npx plugins add supabase-community/supabase-plugin` | [Supabase docs](https://supabase.com/docs/guides/ai-tools/plugins) |
| Build and deploy on Vercel | Vercel | `/plugins`, search Vercel | [Vercel changelog](https://vercel.com/changelog/vercel-plugin-openai-codex-and-codex-cli-support) |
| Build and deploy on Cloudflare | Cloudflare | `/plugins`, search Cloudflare | [Cloudflare docs](https://developers.cloudflare.com/agent-setup/codex/) |
| Current library docs | Context7 | `codex plugin marketplace add upstash/context7` | [Context7 docs](https://context7.com/docs/clients/codex) |
| Shared context on a large codebase | Graphify | `/plugins`, search Graphify | [Graphify for Codex](https://docs.graphify.com/integrations/codex) |

You won't need all of these. Install the two or three that match your stack and turn the rest off with Space in the `/plugins` browser.

## Which Codex plugins help with code review?

**CodeRabbit** runs a review of your working changes from inside Codex and returns findings with severity, so you can fix them in the same session. It drives the CodeRabbit CLI, so install that first and sign in:

```bash
curl -fsSL https://cli.coderabbit.ai/install.sh | sh
coderabbit auth login
```

Then open `/plugins`, search for `coderabbit` and install it. Ask:

```text
Review my current changes with CodeRabbit
```

**Greptile** brings its pull request reviews into Codex and can review your local branch before you open a PR. The plugin bundles Greptile MCP and a CLI, and both sign in with OAuth. It needs Node 22 or newer and a Greptile account with your repositories connected:

```bash
codex plugin marketplace add greptileai/skills
codex plugin add greptile@greptile-plugin
```

Start a new task, connect the Greptile MCP server it supplies, and finish the browser sign in. The [Greptile Codex docs](https://www.greptile.com/docs/integrations/codex) list the `login` and `review` skills.

Codex also has its own review built in. If `@codex review` on GitHub covers what you need, you may not want a second reviewer. Our walkthrough of [Codex code review with Graphify](/blog/codex-code-review) shows how to set that up and check each finding against callers and tests.

## Which Codex plugin helps you fix production errors?

**Sentry.** Its Codex plugin bundles the hosted Sentry MCP server with Sentry's skills for SDK setup, debugging issues, code review with Sentry context and feature setup. It is also in `/plugins`:

```bash
codex plugin marketplace add getsentry/plugin-codex
codex plugin add sentry@sentry-plugin-marketplace
```

Sentry's [agent plugin docs](https://docs.sentry.io/ai/agent-plugin/) also offer `npx @sentry/agent-plugin install`, which finds the assistants on your machine and wires the plugin into each. A good first prompt is "What are the top errors in the last 24 hours?"

## How do you connect Codex to Linear?

Search for Linear in `/plugins`, or add Linear's hosted MCP server yourself:

```bash
codex mcp add linear --url https://mcp.linear.app/mcp
codex mcp login linear
```

Codex can then read issues for context and create or update them without copy and paste. Linear's [Codex setup page](https://linear.app/integrations/codex-mcp) has the `config.toml` version too.

## Which Codex plugins help you build and deploy?

**Supabase** bundles its MCP server with two skills, `supabase` and `supabase-postgres-best-practices`, so Codex can query your database, manage migrations and deploy Edge Functions. Find it in `/plugins`, or install it into every agent on your machine at once:

```bash
npx plugins add supabase-community/supabase-plugin
```

**Vercel** gives Codex skills and specialist agents for building and deploying on Vercel. Install it from `/plugins`, per Vercel's [Codex changelog post](https://vercel.com/changelog/vercel-plugin-openai-codex-and-codex-cli-support). The [Vercel plugin docs](https://vercel.com/docs/agent-resources/vercel-plugin) cover the other agents it supports.

**Cloudflare** installs Cloudflare's skills and registers its MCP servers. Run `/plugins` and install Cloudflare. The first time Codex calls a Cloudflare tool, it sends you through OAuth to pick permissions. Cloudflare's [Codex page](https://developers.cloudflare.com/agent-setup/codex/) has example prompts and a troubleshooting list.

Pick the one your app runs on. Installing both Vercel and Cloudflare mostly gives Codex two opinions about where to deploy.

## How do you give Codex current library docs?

**Context7** pulls current, version specific library docs into the session, so Codex stops writing against an API that changed last month. The plugin adds a skill that looks docs up when you ask about a library, and signs in with OAuth:

```bash
codex plugin marketplace add upstash/context7
codex plugin add context7@context7-marketplace
```

If you only want the MCP server, OpenAI's own [Codex MCP docs](https://learn.chatgpt.com/docs/extend/mcp) use Context7 as the example:

```bash
codex mcp add context7 -- npx -y @upstash/context7-mcp
```

## How do you give Codex shared context on a large codebase?

This is the job I work on, so read this section knowing I'm biased.

On a big repository, Codex spends a lot of each task finding its way around: which module owns billing, who calls the function you're about to change, what else a pull request reaches. **Graphify** is shared codebase context for coding agents and the people working with them: a code graph, a Wiki, Memory and PR reviews, with the graph underneath powering the rest. Over MCP, Codex can find symbols, follow callers, check the impact of a change, recall team memory and read Graphify's review of a pull request with `review_status`.

To install it, open the [Graphify listing](https://chatgpt.com/plugins/plugin_asdk_app_6abe89f7f5d88191b9422522bb8562a4) and select **Install plugin**, or open `/plugins` in Codex CLI and search for **Graphify**. Select **Connect**, finish the browser sign in, and start a new session. You need at least one repository with the status **Indexed** in [Graphify](https://app.graphify.com).

In the IDE extension, or if you'd rather keep the setup in your own config, add the server by hand:

```bash
codex mcp add graphify --url https://api.graphify.com/mcp
codex mcp login graphify
```

Or put it in `~/.codex/config.toml` for your user, or `.codex/config.toml` for one project:

```toml
[mcp_servers.graphify]
url = "https://api.graphify.com/mcp"
auth = "oauth"
```

Use one path, not both, or every Graphify tool shows up twice. Then try a first prompt from the [Graphify for Codex docs](https://docs.graphify.com/integrations/codex):

```text
Use Graphify's impact tool on the function that validates session tokens in owner/name. List the callers and files that could break if I change its signature.
```

The [Graphify and Codex integration page](/integrations/codex) shows both the hosted setup and the open source Graphify CLI, and [how to give Codex context on a large codebase](/blog/how-to-give-codex-context-on-a-large-codebase) walks through a first session.

**GitNexus** does a similar job from a different angle. It builds a code knowledge graph on your machine, with no server, and connects to Codex over MCP, skills and hooks:

```bash
codex mcp add gitnexus -- npx -y gitnexus@latest mcp
```

It also ships as a Codex plugin through `codex plugin marketplace add abhigyanpatwari/GitNexus`. The [editor setup guide](https://github.com/abhigyanpatwari/GitNexus/blob/main/docs/editor-setup.md) has the install commands. GitNexus is licensed under PolyForm Noncommercial 1.0.0, so read the terms before you use it at work.

## When does another tool fit better?

A list like this is only useful if it tells you when to skip something, so here's my honest take:

- **Your repository is small.** If Codex can read the whole thing in one go, a codebase context tool adds structure but not much else. Start with Context7 and a review plugin.
- **You only want review comments on pull requests.** CodeRabbit or Greptile, or Codex's own `@codex review`, may be all you need. Graphify's PR reviews make the most sense when you also want the graph and Memory behind them.
- **You can't send code to a hosted service.** Use something that runs locally: the open source Graphify CLI or GitNexus. Hosted Graphify answers from repositories indexed in your workspace, not from files on your laptop.
- **Your question is about a library, not your code.** That's Context7's job. A code graph knows your repository, not the latest docs for a framework.
- **You live in the IDE extension.** Plugins don't load there yet, so use each tool's `codex mcp add` path.

## Plugins, MCP servers or skills: which do you need in Codex?

They overlap, so it helps to keep them straight:

- **An [MCP server](/glossary/mcp-server)** connects Codex to an outside tool or data source.
- **A skill** is instructions and scripts Codex loads when a task matches.
- **A plugin** is the install package. It can bundle MCP servers, skills and other pieces into one install. Most plugins in this list are a hosted MCP server plus a few skills.

If a tool you want ships only as an MCP server, add it with `codex mcp add`. Using Claude Code as well? The [best Claude Code plugins](/blog/best-claude-code-plugins) list covers that side, and [best MCP servers for codebase context](/blog/best-mcp-servers-for-codebase-context) compares the context tools in more depth.

## FAQ

### What are the best Codex plugins in 2026?

Pick by job. CodeRabbit or Greptile for code review, Sentry for production errors, Linear for issues, Supabase for the backend, Vercel or Cloudflare for deploys, Context7 for library docs, and Graphify for shared context on a large codebase.

### How do I install a Codex plugin?

Run `/plugins` in Codex CLI, or open the **Plugins** tab in ChatGPT. Search for the plugin and install it. Some plugins live in their vendor's own marketplace, which you add first with codex plugin marketplace add. Start a new session after installing.

### Do Codex plugins work in the IDE extension?

Not yet. Plugins work in Codex CLI and in Codex inside the ChatGPT desktop app. In your editor, add the tool's MCP server with codex mcp add instead, because the CLI and the IDE extension share the same config.toml.

### What is the difference between a Codex plugin and an MCP server?

An MCP server connects Codex to an outside tool. A plugin is the install package: it can bundle MCP servers, skills and other pieces into one install. Most plugins in this list are a hosted MCP server plus a few skills.

### Is Graphify a Codex plugin?

Yes. Graphify by Graphify Labs is listed in OpenAI's plugin directory, which Codex and ChatGPT share. Install it from /plugins, connect, and sign in with OAuth. You can also add it by hand with codex mcp add graphify --url https://api.graphify.com/mcp and codex mcp login graphify.

## Try it

Connect a repository at [app.graphify.com](https://app.graphify.com), then install the [Graphify plugin](https://chatgpt.com/plugins/plugin_asdk_app_6abe89f7f5d88191b9422522bb8562a4) from `/plugins` in Codex. Questions? Find us on [Discord](https://discord.gg/graphify).
