Before you start
Use a current Codex version that supports remote HTTP MCP servers and OAuth. You need an existing FIRCY account and a browser on the device where you start authorisation.
Add the connection
In Codex’s MCP settings, add a remote server named fircy with this URL:
https://mcp.fircy.com/mcp
For the Codex CLI, the equivalent commands are:
codex mcp add fircy --url https://mcp.fircy.com/mcp
codex mcp login fircy
Follow the browser sign-in and approve the read permissions. Return to Codex and ask: “Check my FIRCY connection, then summarise recent activity.”
If you maintain configuration manually, the server entry is:
[mcp_servers.fircy]
url = "https://mcp.fircy.com/mcp"
Use Codex’s OAuth login for that entry. Do not put API keys, client secrets, or access tokens in the configuration.
Troubleshooting the browser return
Complete sign-in on the same device and browser where you started. Codex uses a local callback during authorisation; a blocked local callback can prevent completion. Restart the login from Codex if the request expires.