Codex MCP integration

What is Model Context Protocol (MCP)?

MCP is a standardized protocol that allows AI assistants like Codex to securely access structured data from various applications. When you integrate Alloy Planning and Feedback with Codex via MCP, you enable Codex to:

1. Access product context: Codex can reference your Alloy Planning work items, customer feedback and other related content.
2. Answer questions with context: Codex can provide answers grounded in your specific product data
3. Assist with product planning: Codex can help draft, refine, and organize product strategies with access to your existing work

Setting Up Codex Integration

Setting up the Codex integration with Alloy Planning and Feedback is straightforward. Codex can connect over OAuth, so you do not need to create an MCP API key, export a bearer token, or edit config.toml by hand.

1. Add Alloy Planning and Feedback in Codex

1. Open the Codex app.
2. Open Settings from the app menu, or press Cmd+,.
3. Select Integrations & MCP.
4. Choose the option to add a custom MCP server.
5. Enter Alloy Planning and Feedback as the server name.
6. Enter the MCP server URL:

https://mcp.index.inc/mcp

7. Save the server.
8. Complete the browser authorization flow when Codex prompts you to connect Alloy Planning and Feedback.

Once authorized, Codex will have secure access to your Alloy Planning and Feedback workspace data. MCP settings are shared by the Codex app, CLI, and IDE extension.

Optional: configure from the terminal

If you prefer to configure Codex from the terminal, run:

codex mcp add alloy --url https://mcp.index.inc/mcp
codex mcp login alloy

Setting up Codex with an MCP API key

You can also connect Codex with an Alloy Planning and Feedback MCP API key. This is useful when you want to manage access with a workspace-scoped key instead of using browser-based OAuth.

1. Generate an MCP API key in Alloy

1. Navigate to your workspace settings in Alloy.
2. Select MCP from the sidebar.
3. Click Create New Key.
4. Provide a name (e.g., "Codex Integration") and optional description.
5. Click Create Key.
6. Copy the generated API key (note: it will only be shown once).

2. Export your MCP API key as an environment variable

Codex reads the MCP API key from an environment variable rather than embedding it directly in the config file. Add the following line to your shell profile, such as ~/.zshrc, ~/.bashrc, or equivalent:

export ALLOY_MCP_API_KEY="<YOUR API KEY HERE>"

Replace <YOUR API KEY HERE> with the MCP API key you generated in Alloy, then reload your shell, for example with source ~/.zshrc, or open a new terminal so the variable is picked up.

3. Configure Codex with the MCP API key

Codex reads its MCP server configuration from ~/.codex/config.toml. Open that file in your editor, creating it if it doesn't exist, and add the following entry:

[mcp_servers.alloy]
bearer_token_env_var = "ALLOY_MCP_API_KEY"
enabled = true
url = "https://mcp.index.inc/mcp"

Save the config and restart any running Codex sessions. Once connected, Codex will have secure access to your Alloy Planning and Feedback workspace data.

Using Codex with Alloy Planning and Feedback integration

With the integration set up, you can now use Codex to interact with your Alloy Planning and Feedback data:

Ask Questions About Your Product

You can ask Codex questions like:

• "What's the status of our Q3 roadmap items?"
• "Summarize the requirements for the new authentication feature"
• "What feedback did we get on the beta release?"

Benefits of Integration

Enhanced Context Awareness

Codex's responses will be informed by your product data, making them more relevant and accurate for your specific needs.

Time Savings

No need to manually reference or copy-paste information from Alloy Planning and Feedback into Codex - the integration means Codex already has access to this context.

Better Decision Support

Codex can provide more valuable insights and recommendations when it has access to your full product context.