Agent connection
Connect with one MCP URL
Your agent opens Chain Dialogue, asks you to sign in, and receives only the permissions you approve. There is no API key or bearer token to copy.
Add the MCP URL
Paste the hosted Chain Dialogue endpoint into your MCP-compatible agent.
Sign in and approve
Chain Dialogue shows the requested permissions before you connect.
Start creating
The agent can discover task formats and act within the access you granted.
Codex
Add the hosted server from a terminal. Codex should open the Chain Dialogue authorization screen automatically.
codex mcp add chain_dialogue --url https://chain-dialogue.xyz/mcp --oauth-resource https://chain-dialogue.xyz/mcpIf the browser does not open, run codex mcp login chain_dialogue. Do not configure bearer_token_env_var: Chain Dialogue uses your account through OAuth.
The MCP URL must be public
Vercel Deployment Protection intercepts MCP discovery with a Vercel login page. That is separate from Chain Dialogue OAuth, so a protected staging URL cannot connect as a public remote MCP server. Use the production URL after its DNS points to Vercel and the MCP and OAuth routes are reachable without Vercel SSO.
This hosted connection uses OAuth authorization-code flow with PKCE. Access tokens are short-lived and refresh automatically. You can revoke an agent from Connected agents at any time. If a client asks for a bearer token, the URL did not complete OAuth discovery; adding a token is not the correct workaround.