Connect Silverile to the Codex desktop app via the MCP Streamable HTTP transport. Once configured, you can browse stories, check your assigned work, and create new backlog items directly from Codex — without leaving your AI assistant.
Once connected, ask Codex in plain English:
Codex calls the Silverile MCP tools on your behalf, scoped to your workspace and credentials.
ide_XXXXXXXXXXXXXXXX) and Key SecretYour Product ID is the numeric ID of your Silverile workspace. To find it, open your project and go to Project Settings — the Product ID is listed there. You will need it when generating your MCP token in the next step.
Codex connects to Silverile exclusively through the MCP Streamable HTTP transport. The recommended setup uses Codex MCP sign-in so you do not need to store a bearer token in a shell environment variable.
Use the Codex CLI to register the Silverile MCP server and start the OAuth sign-in flow. Codex saves the authentication so you do not need to manage a bearer token manually.
macOS — run in Terminal:
"/Applications/Codex.app/Contents/Resources/codex" mcp add Silverile --url https://mcp.silverile.com/mcp "/Applications/Codex.app/Contents/Resources/codex" mcp login Silverile
Windows — run in PowerShell or Command Prompt:
codex mcp add Silverile --url https://mcp.silverile.com/mcp codex mcp login Silverile
If codex is not on your PATH, use the full path to the Codex executable, e.g. "%LOCALAPPDATA%\Programs\Codex\codex.exe".
Complete the sign-in screen with your Silverile Key ID and Key Secret, then choose your workspace. Once saved, restarting your computer or reopening Codex does not require re-exporting SILVERILE_MCP_TOKEN.
If you cannot use MCP sign-in, generate a URL-safe base64 token from your Key ID, Key Secret, and Product ID. Keep the result — you will need it in the next step.
macOS / Linux — run in Terminal:
echo -n '{"keyId":"ide_XXXXXXXXXXXXXXXX","keySecret":"your_key_secret_here","productId": 13452}' \
| openssl base64 -A \
| tr '+/' '-_' \
| tr -d '='Windows — run in PowerShell:
$json = '{"keyId":"ide_XXXXXXXXXXXXXXXX","keySecret":"your_key_secret_here","productId": 13452}'
$bytes = [System.Text.Encoding]::UTF8.GetBytes($json)
$base64 = [Convert]::ToBase64String($bytes)
$base64.Replace('+', '-').Replace('/', '_').TrimEnd('=')Copy the single-line output — that is your bearer token.
Codex reads SILVERILE_MCP_TOKEN from your environment on startup. Set it so the value survives computer restarts and is visible to the Codex app regardless of how it is launched.
macOS — zsh (default shell on macOS 10.15+):
echo 'export SILVERILE_MCP_TOKEN="<paste-token-here>"' >> ~/.zshrc source ~/.zshrc
macOS / Linux — bash:
echo 'export SILVERILE_MCP_TOKEN="<paste-token-here>"' >> ~/.bashrc source ~/.bashrc
Windows — persistent (recommended) — run in PowerShell or Command Prompt:
setx SILVERILE_MCP_TOKEN "<paste-token-here>"
setx writes the variable to your Windows user environment permanently. It does not update the current session — fully quit and relaunch Codex after running this command so it picks up the new variable.
Windows — current PowerShell session only (not persistent):
$env:SILVERILE_MCP_TOKEN = "<paste-token-here>"
Use this only if you launch Codex from the same PowerShell window immediately after. The variable is lost when the session closes.
This step is the same on all platforms. In Codex settings, go to MCP Servers → Connect to a custom MCP and select the Streamable HTTP tab. Fill in the fields:
| Field | Value |
|---|---|
| Name | Silverile |
| URL | https://mcp.silverile.com/mcp |
| Bearer token env var | SILVERILE_MCP_TOKEN |
Click Save. Codex will read SILVERILE_MCP_TOKEN from your environment and attach it as the Authorization: Bearer header on every request.
Once Codex is running with the MCP server active, ask it to validate the connection:
Codex will call the validate_connection tool and confirm your credentials are accepted and the workspace is reachable.
MCP connection refused or 401 in Codex
For the recommended OAuth setup, run the Codex CLI login command shown above again and complete sign-in with an active Key ID and Key Secret. If you chose manual bearer-token setup, regenerate SILVERILE_MCP_TOKEN and confirm Codex can read it.
"zsh: command not found: codex" (macOS)
Codex Desktop bundles its CLI inside the application. Use "/Applications/Codex.app/Contents/Resources/codex" in the commands shown above; it works even when codex is not installed on your shell PATH.
"codex" is not recognized (Windows)
Open PowerShell and run: Get-Command codex to find the installed path. If not found, use the full path to your Codex installation, e.g. "$env:LOCALAPPDATA\Programs\Codex\codex.exe". You may also need to add the Codex bin directory to your PATH.
"Dynamic client registration not supported"
The Silverile MCP deployment is not yet running the OAuth-enabled server version required by Codex. Use the manual bearer-token fallback below until the updated MCP server is deployed, then remove and add the MCP connection again.
Bearer token env var not picked up in Codex (macOS)
Values stored only in ~/.zshrc are loaded by new shell sessions and may not be visible when the macOS Codex app is launched from Finder or the Dock. Use the OAuth setup above, or launch Codex from a terminal where the variable is already exported.
Bearer token env var not picked up in Codex (Windows)
A $env: variable set in PowerShell only lasts for that session. Use setx instead: setx SILVERILE_MCP_TOKEN "<token>" — then fully quit and relaunch Codex so it inherits the updated user environment.
"Product not found" error
Verify that the selected workspace, or the productId in a manually generated token, matches a workspace your account can access. Sign in again or regenerate the manual token with the correct Product ID.
Key Secret not accepted
Confirm the key is still active under Settings → User Settings → IDE API Keys in Silverile. Generate a new key if needed, then sign in again or regenerate your manual token.