Skip to content
DevelopersOpen app ↗
Browse documentation
Linkwiz API · v1

Connect Codex

Connect Codex directly to Linkwiz using OAuth and your workspace permissions.

Your Linkwiz login is all you need. No API key or secret to create. You must be a workspace owner or admin, with API access included in your plan.

For the Codex app and CLI. ChatGPT connections are set up separately.

Add Linkwiz to Codex

Open a terminal on the computer where you use Codex. Copy and run this command:

Add Linkwiz
codex mcp add linkwiz --url https://app.linkwiz.ai/mcp --oauth-client-id linkwiz-codex
Prefer to edit the configuration file?

Add this to ~/.codex/config.toml (Windows: %USERPROFILE%\.codex\config.toml). If a Linkwiz entry already exists, update it instead of adding a duplicate.

Codex configuration
[mcp_servers.linkwiz]
url = "https://app.linkwiz.ai/mcp"

[mcp_servers.linkwiz.oauth]
client_id = "linkwiz-codex"
callback_url = "http://127.0.0.1/callback"

Sign in and choose your workspace

If a sign-in page did not open, run:

Sign in to Linkwiz
codex mcp login linkwiz

Finish sign-in in a browser on the same computer as Codex.

Sign in with your Linkwiz account, choose your workspace, review the requested permissions and select Connect workspace.

Reads use existing data. Creating reports or adding people requires write permission and your approval in Linkwiz; accepted profiles are then queued for scanning under your plan.

Try your first question

Return to Codex and start a new task if Linkwiz tools have not appeared.

First question
Which Linkwiz workspace is connected? List my reports without changing anything.

What to expect: your workspace name and available reports. An empty list is normal if the workspace has no reports.

Need help?

Why is there no API key or secret?

You authorize access by signing in and approving a workspace. Codex stores the resulting OAuth tokens automatically. The client ID is public; it is not a password. Do not enter a Linkwiz REST API key into the secret or bearer-token field.

The connection failed or no tools appeared
  • Command not found or unknown option: update/install the official Codex CLI and reopen your terminal. These commands were checked against CLI 0.147.0.
  • Dynamic registration unsupported: include the --oauth-client-id shown in step 1.
  • Localhost refused to connect: start login again on the computer running Codex. Its callback at http://127.0.0.1:PORT/callback uses a temporary local listener; opening that link on your phone will not work.

For access denied, check workspace membership, selected permissions and your plan’s API access. If write permissions were added later, reconnect and approve them. An expired development tunnel requires a new URL and connection.

Advanced: remote computers and OAuth callbacks

This guide covers Codex running on your local computer. For a remote machine/container, use a securely forwarded local listener and Codex’s callback configuration. Linkwiz accepts its registered 127.0.0.1 callback paths with a temporary port, including the server-specific suffix used by Codex CLI 0.147.0. Arbitrary paths and tunnel callbacks are not supported. Tokens use mandatory PKCE.

Disconnect or switch workspace

In Linkwiz, open Workspace settings → Integrations → Disconnect to stop future access. Connecting again to the same assistant replaces your account’s previous workspace connection. Previously shared conversations remain in the assistant.

codex mcp logout linkwiz clears the local sign-in; codex mcp remove linkwiz removes the server entry.

Explore capabilities and limitations →