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.
In a terminal on macOS, use the CLI bundled with Codex Desktop to register the Silverile MCP server and start the sign-in flow:
"/Applications/Codex.app/Contents/Resources/codex" mcp add Silverile --url https://mcp.silverile.com/mcp "/Applications/Codex.app/Contents/Resources/codex" mcp login Silverile
Complete the sign-in screen with your Silverile Key ID and Key Secret, then choose your workspace. Codex manages the saved MCP authentication, so restarting your computer or opening the macOS app from the Dock does not require exportingSILVERILE_MCP_TOKEN again.
If you cannot use MCP sign-in, run the following command with your own Key ID, Key Secret, and Product ID. It produces a URL-safe base64 string with no padding:
echo -n '{"keyId":"ide_XXXXXXXXXXXXXXXX","keySecret":"your_key_secret_here","productId": 12}' \
| openssl base64 -A \
| tr '+/' '-_' \
| tr -d '='Add it to your shell profile so Codex launched from that shell can read it as an environment variable:
echo 'export SILVERILE_MCP_TOKEN="<paste-token-here>"' >> ~/.zshrc source ~/.zshrc
In the 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 Desktop 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"
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.
"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
This affects the manual bearer-token fallback. 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 shell session where the variable is exported.
"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.