This quickstart uses Bily Connect, the recommended sign-in path. It keeps credentials out of client configuration and uses the signed-in user’s current organization and store memberships.
Open MCP settings
Sign in to Bily, then open Settings > MCP.The selected store matters only if you later create a fallback key. Bily Connect uses the signed-in user’s current memberships. Add Bily to Codex
Add this block to ~/.codex/config.toml:[mcp_servers.bily]
url = "https://api-dispatcher.bily.ai/mcp"
default_tools_approval_mode = "prompt"
tool_timeout_sec = 120
Sign in to Bily
Restart or reload Codex. When it asks to connect Bily, sign in and approve MCP access.Bily Connect uses the mcp_access scope. Bily checks the signed-in user’s organization and store memberships for every operation.
Confirm your identity and stores
Ask the client:Use Bily to show my authenticated identity, organizations, and accessible stores.
Search for the right operations first. Do not make changes.
search, then use execute with bily.context() for one-call discovery. Preview a store operation
Continue with a read-only request:For store.example.com, find the Bily operation for a revenue trend comparison.
Explain its required dates and verification guidance before executing it.
Keep approval mode set to prompt. One execute call can contain several helper calls. Review the complete function before you approve it.
