Skip to main content
Use the Codex CLI to connect your local Codex app, CLI, or IDE extension to Inspack. They share MCP configuration on the same machine. Use an active Inspack account with an organization.

Add Inspack

With the Codex CLI installed, run this in a terminal on the computer where you use Codex:
If your organization provided another Inspack server URL, substitute that URL. If you already added the server, skip this command and sign in using its existing name below.

Sign in

Complete the browser sign-in with the Google or Microsoft account you use for Inspack. Complete organization setup if prompted, then check the client and organization on the Inspack approval screen and allow access. The connection stays tied to the organization you approved. After switching organizations in Inspack, reconnect and approve access for the new organization. If the browser does not open, or the app has no sign-in button, run:
Replace inspack with the configured server name if you chose a different name. Keep the terminal running until it confirms successful authentication. The browser may redirect to 127.0.0.1 on your computer to complete the login. When configuring this OAuth connection in the app, leave Bearer token env var, Headers, and Headers from environment variables empty.

Check the connection

Restart your Codex app or IDE extension, or start a new CLI session, then ask:
Use inspack to call get_inspectors and list the inspectors available to my organization.
Receiving your inspector list confirms authenticated tool access.

Troubleshooting

  • Unknown server name: run codex mcp list and use the exact name shown in the login command.
  • Local callback cannot be reached: restart the login command, keep the terminal open, and finish the newly opened browser flow.
  • Sign-in succeeds, but access is denied: check your account and organization, then contact Inspack support with the error message.