One config snippet connects Codex to your workspace over the Productboard MCP Server.
Codex connects to Productboard over the open MCP standard, giving OpenAI's coding agent direct access to the specs your team writes. A workspace admin enables the MCP Server once, and each engineer connects their own Codex with a short config snippet. From then on, every Codex session can read from and write back to your Productboard workspace.
Retrieve the spec for any feature, initiative, or document straight from Productboard. When a PM updates a spec, the next pull gets the latest version, so the agent never builds from a stale copy.
Ask Codex to convert a Productboard spec into sequenced tasks, acceptance criteria mapped to code tasks, and a list of gaps to resolve before writing code.
A clarifying question raised mid-build lands as a comment on the Productboard spec, where the spec owner will see it. The answer stays on the spec for everyone who reads it next.
Update an item's status and other fields as implementation progresses, and edit specs and documents directly from the coding session. Productboard reflects what's being built as it happens.
A Productboard workspace admin first enables the MCP Server under Settings → Integrations → MCP servers and chooses which roles may connect. Then, on your machine:
Add the Productboard server to ~/.codex/config.toml (or a project-scoped .codex/config.toml):
Run codex mcp login productboard.
Complete the browser sign-in with your existing Productboard login. There are no API keys to manage.
The connection acts as you: Codex sees the same specs you can see in Productboard, and every action respects your workspace role.
