Codex Integrations
Codex supports integration with a variety of development tools and platforms, expanding its capabilities and application scenarios.
* * *
## GitHub Integration
Codex integrates deeply with GitHub, allowing direct code reviews within PRs.
### Feature Overview
| Feature | Description |
| --- | --- |
| **PR Review** | Use @codex review in PR comments to get a review |
| **Auto Review** | Automatically triggers a review for every new PR |
| **CI Fix** | @codex fix the CI failures |
| **Cloud Tasks** | Other @codex commands launch cloud tasks |
### Setting Up GitHub Integration
1. Configure Codex Cloud
2. Go to the settings page to enable Code Review
3. Authorize access to your GitHub repositories
4. Select the repositories to enable
### Requesting a Review
## Using in PRs
# Enter in PR comments
@codex review
# Specify review focus
@codex review for security issues
# Review performance issues
@codex review for performance regressions
### Codex Response
Codex will:
1. React to the PR with π
2. Analyze code changes
3. Post review comments
4. Flag discovered issues (P0 and P1 by default)
### Customizing Review Guidelines
Define review rules in the repository's AGENTS.md:
## Review guidelines
## Review guidelines
- Don't log PII (Personally Identifiable Information)
- Verify authentication middleware wraps every route
- Check for SQL injection vulnerabilities
- Ensure error messages don't leak sensitive info
- Treat typos in docs as P1 issues
> Codex only flags P0 and P1 issues by default, which can be adjusted in AGENTS.md.
* * *
## Slack Integration
Through the Slack integration, team members can use Codex directly within channels.
### Setting Up Slack Integration
1. Go to the Codex settings page
2. Find the Integrations section
3. Add the Slack app
4. Authorize access to the Slack workspace
### Usage
## Using in Slack
# In a Slack channel
@codex review this PR: https://github.com/xxx/pull/123
# Explain code
@codex explain this function
# Assign a task
@codex fix the bug in auth module
### Applicable Scenarios
* Quickly get AI assistance during team collaboration discussions
* Delegate tasks for remote team members
* Asynchronous work scenarios
* * *
## Linear Integration
Linear is a project management tool that Codex can integrate with to handle Issues.
### Setting Up Linear Integration
1. Go to the Codex settings page
2. Add the Linear integration
3. Authorize access to the Linear workspace
4. Configure Issue handling rules
### Use Cases
| Scenario | Description |
| --- | --- |
| **Issue Handling** | Automatically create code modifications based on Issues |
| **Review Sync** | Add review findings to Issues |
| **Status Updates** | Automatically update Issue status |
| **Comment Replies** | Use @codex in Issue comments |
* * *
## MCP (Model Context Protocol)
MCP is a protocol that connects Codex with external tools.
### MCP Overview
* **STDIO Server**: Local process, communicates via standard input/output
* **HTTP Server**: Remote server, communicates via HTTP API
### Configuring MCP Servers
## MCP Configuration
# ~/.codex/config.toml
# STDIO Server
[mcp_servers.filesystem]
command = "npx"
args = ["-y", "@modelcontextprotocol/server-filesystem", "./docs"]
# HTTP Server
[mcp_servers.api]
url = "https://api.example.com/mcp"
bearer_token_env_var = "API_TOKEN"
### Common MCP Servers
| Server | Function |
| --- | --- |
| **filesystem** | File system access |
| **github** | GitHub API |
| **postgres** | PostgreSQL database |
| **fetch** | Web fetching |
| **openai-docs** | OpenAI documentation |
### MCP Tool Permissions
## Tool Permission Configuration
# Tool whitelist
[mcp_servers.filesystem]
enabled_tools = ["read_file", "write_file"]
# Tool blacklist
disabled_tools =
# Tool approval mode
[mcp_servers.filesystem.tools.write_file]
approval_mode = "ask" # ask | approve | deny
* * *
## OAuth Authentication Configuration
Some MCP servers require OAuth authentication:
## OAuth Configuration
[mcp_servers.figma]
url = "https://api.figma.com/mcp"
scopes = ["file:read"]
oauth_resource = "codex-integration"
# OAuth callback port
mcp_oauth_callback_port = 8080
# Credential storage
mcp_oauth_credentials_store = "keyring"
* * *
## Frequently Asked Questions
### Q: What plan is required for GitHub integration?
A Codex Cloud subscription (Plus or above) is required.
### Q: Can I restrict which repositories Codex can access?
You can selectively authorize repositories in the settings.
### Q: How are MCP servers installed?
Most MCP servers are installed via npm, and Codex manages them automatically.
### Q: Are other integrations supported?
Codex continuously adds new integrations, stay tuned for official updates.
YouTip