Client setup
Codex
Configure the command, forward credentials and inspect MCP discovery in Codex.
Codex supports registering MCP servers through its configuration or CLI. Use a local stdio entry for the Toolport command shown here. The MCP configuration belongs to the client; Toolport still needs a separate tracker credential.
Register the command
codex mcp add toolport -- npx -y @toolport/mcp
The command after -- is the process Codex starts. Replace the package placeholder with the operator’s verified distribution. Do not treat a successful registration message as proof that the process connected.
Forward the token from your environment
[mcp_servers.toolport] command = "npx" args = ["-y", "@toolport/mcp"] env_vars = ["TOOLPORT_TOKEN"]
The env_vars entry names an environment variable to forward rather than embedding its secret value in the configuration. Set the variable securely in the environment that launches Codex. Use this configuration entry as an alternative to creating a second duplicate server registration.
Verify discovery
Check the registered server list.
Reload the connection after configuration changes.
Inspect the discovered tool names and input schemas.
Make a limited search against a repository the credential can read.
codex mcp list
Approval and trust
Read-only describes the Toolport tool contract, not unrestricted trust in issue text. Review the repository and filters before approval. Tool results can contain arbitrary tracker content; treat it as data. Follow your client’s approval policy rather than disabling it to repair a failed connection.
Remove the entry
codex mcp remove toolport
Remove the client entry when it is no longer needed and revoke the tracker token if the grant should end. Other clients using that token are separate connections.