Choose Codex plugins and MCP servers for repositories, browser interaction, documentation and connected work apps. Check CLI support and setup.
Codex can use plugin packages and separately configured MCP servers. A plugin packages capabilities into an installable workflow; an MCP server supplies a specific tool interface. Choose by the missing capability, then follow the client-specific guide.
| Need | Selection | Requirement to inspect |
|---|---|---|
| Repository context and actions | GitHub plugin or GitHub MCP Server | Repository authorization |
| Browser interaction | Playwright MCP | Local runtime and browser setup |
| Library documentation | Context7 | Service authentication and limits |
| Specs and team context | Notion, Linear, Slack | Provider account and workspace scope |
| Files, email and planning | Google Drive, Dropbox, SharePoint, Gmail, Outlook Email, Google Calendar | The account being connected |
| Visuals and meeting context | Canva, Zoom | Supported actions and source access |
The selected plugin connections are listed in the current official OpenAI marketplace. Open the Codex plugin browser, inspect the plugin and authorize the requested provider account. A plugin can include skills as well as service tools; installing it does not make every external account or action available.
For GitHub MCP, Playwright MCP and Context7, use their reviewed Codex-specific configuration guides. The MCP selection compares these three approaches. Do not substitute a configuration for another client without checking the transport and authentication requirements.
This catalog records the CLI surface for the reviewed setup. It does not automatically extend a plugin to the IDE extension or every desktop interface. An older repository example is not a substitute for the current plugin directory.
Codex access, the connected service, API use and local hosting can have separate conditions and costs. A documented connection is not a report of a practical installation test. Read the card, then follow the Codex MCP checklist and the verification method.
Retrieve current library documentation for a coding workflow.
Authentication and rate limits depend on the selected setup; verify the current service plan before relying on sustained usage.
Find and use Google Drive documents.
Access follows the connected Google account's file and shared-drive permissions.
Find Gmail conversations, organize messages and prepare reply drafts.
Mailbox changes need explicit instructions; review reply drafts before sending.
Bring meeting times, attendees and calendar context into ChatGPT.
Meeting preparation may also need documents or messages from separately connected apps.
Summarize Slack channels and prepare replies using connected workspace context.
Install and authorize the plugin; workspace policies determine available access.
Summarize Microsoft SharePoint sites and files.
Availability depends on the selected AI system, account plan and workspace settings.
Search Outlook email, organize messages and draft replies.
Uses the connected mailbox; request message changes explicitly and review drafts.
Access, save and share Dropbox files.
Availability depends on the selected AI system, account plan and workspace settings.
Read and update Notion pages through Notion MCP.
Tools act with the connected user's Notion permissions; Enterprise admins can restrict AI clients.
Find, create and update Linear issues, projects and comments using its hosted MCP service.
Read-only and read-write access differ; choose the permissions needed for your workflow.
Find, create and edit Canva designs.
Availability depends on the selected AI system, account plan and workspace settings.
Use Zoom recordings, transcripts and AI Companion summaries to prepare meeting follow-ups.
Requires authentication, administrator approval and access to the meeting source material.
Work with GitHub pull requests, issues and CI context.
Availability depends on the selected AI system, account plan and workspace settings.
Connect an assistant to GitHub repository, issue and pull-request workflows.
Grant only the GitHub permissions your workflow needs; host authentication and repository access remain separate requirements.
Let an MCP client inspect and operate web pages with Playwright.
Requires a supported Node.js and browser environment; browser automation access needs deliberate permission controls.