Connect Codex to Phasoric
First prepare an accessible Phasoric vault. Use the Codex installation on the machine or host where the task runs.
Add and authenticate
- Add the server with the Codex CLI:
codex mcp add phasoric --url https://phasoric.com/api/mcp
codex mcp login phasoric
codex mcp list
- Complete Phasoric sign-in in the browser and review consent. Approve continued access if offered.
- Start a new Codex task using that host's configuration. Ask it to list your Phasoric vaults and read the project brief before changing code.
For configuration-based setup, merge this entry into your existing Codex configuration rather than replacing the file:
[mcp_servers.phasoric]
url = "https://phasoric.com/api/mcp"
OAuth login is separate from adding the URL. If an existing entry uses a manual bearer-token environment variable, choose which authentication method to retain; do not leave a missing environment-variable credential in place and assume OAuth will override it. See Codex's official MCP documentation for current configuration and credential precedence.
Use the brief in a coding task
Read the implementation brief in my Phasoric Vault. Summarize its constraints
and acceptance criteria, then inspect this repository before making changes.
Keep the source note path in your explanation.
Phasoric supplies permitted knowledge. Codex performs repository work using its own workspace permissions; MCP access does not grant repository or deployment authority. After reviewing the implementation, ask for a proposed decision-note update and approve it separately if you want it written back.
A configured URL is not proof of authenticated access. Confirm list_vaults and a note read, and use the shared troubleshooting guide if either fails.