Can Codex connect to remote MCP URLs directly?

Not today: Codex launches stdio processes from config.toml and has no remote-URL form. The bridge pattern costs you nothing though: npx -y @sitegpt/cli mcp is the same server, same account, and same three tools as the remote endpoint, and if Codex adds remote support later your grant carries over unchanged.

How do I connect SiteGPT to Codex?

Add a [mcp_servers.sitegpt] entry to ~/.codex/config.toml that runs npx -y @sitegpt/cli mcp, or install the CLI and call it directly. Codex can then build and manage chatbots.

Does it work without a SiteGPT account?

Yes. Codex can create and train a chatbot from a URL with no credentials and return a preview-and-claim link.

Yes. Mint a scoped token with sitegpt tokens create, pass it via SITEGPT_API_TOKEN, and script every step with --json output and stable exit codes.

Codex cannot reach SiteGPT. How do I debug it?

Run the exact command from your config.toml by hand: npx -y @sitegpt/cli mcp. The standalone run surfaces the real error, almost always a pending browser sign-in or a revoked grant. Once it works in a bare terminal it works in Codex, because Codex launches the same process.

SiteGPT × Codex

Add AI customer support with Codex

Codex can drive SiteGPT over MCP or the CLI to build and manage support chatbots straight from your terminal.

All agent surfaces →

codex

> Build a support bot for acme.com and test it   trained acme.com, no login needed  asked 3 questions, all answered  ✓ ready, here is your claim link

Connect in two minutes

Connect SiteGPT to Codex

~/.codex/config.toml

[mcp_servers.sitegpt]
command = "npx"
args = ["-y", "@sitegpt/cli", "mcp"]

Codex is OpenAI's coding agent. Learn more at Codex.

MCP in Codex

How MCP works in Codex

Codex reads MCP servers from ~/.codex/config.toml: each [mcp_servers.<name>] entry declares a command to launch, and Codex talks to it over stdio. There is no remote-URL form, so servers that live on the web need a local bridge process.

SiteGPT ships that bridge: npx -y @sitegpt/cli mcp runs the server locally, signs you in through the browser on first use, and exposes the same three tools (search, execute_read, execute_write) as the remote endpoint. Same account, same permissions, no API key in the TOML.

From there, Codex can treat customer support as part of the codebase it maintains: build the chatbot for the product it is writing, keep the training sources synced with the docs it just changed, and read the support conversations that describe the bugs it is about to fix.

If the server does not respond, run the bridge by hand: npx -y @sitegpt/cli mcp from a terminal surfaces the real error, usually a pending browser sign-in or an expired grant. Codex launches the same command, so whatever works standalone works inside it.

Zero to operated

One TOML entry, then it is part of the job

Codex maintains codebases; supporting the product those codebases serve is the same discipline. One config entry makes it part of the job.

One TOML entry

Add [mcp_servers.sitegpt] with the CLI bridge command to ~/.codex/config.toml. First use opens browser OAuth; the TOML never holds a credential.

Build support as part of the repo

Ask Codex to create a chatbot for the product site and train it on ./docs. The embed snippet lands in the diff like any other change.

Treat docs changes as training changes

When Codex edits documentation, the same session re-syncs the affected knowledge sources, keeping the customer-facing answers aligned with the code.

Read support as an input

What users ask the bot about the API is a roadmap signal. Codex can pull and cluster those questions before planning the next change.

Input → outcome

Your agent types the left side.
Your customers see the right.

agent session

> Stand up support for acme.com   created chatbot (no account)  trained 142 pages + help center  set persona + brand colors  ✓ live, claim link ready

🤖

Acme Support

Online · answers instantly

Do you ship to Canada?

Yes! We ship to Canada on all plans. Standard delivery takes 5-7 business days and duties are included at checkout.

Source: acme.com/shipping

Anything else I can help with?

Ask anything…

Works in any agent that can read a URL: it discovers the no-signup onboarding flow on its own.

Why SiteGPT for Codex

Terminal-native, CI-ready

Codex drives SiteGPT the way it drives everything else: shell commands with --json output and stable exit codes. What works in a session scripts cleanly into CI with a scoped token.

Support as part of the pipeline

Retrain the chatbot when docs change, verify answers after a release, file the transcript. Codex can make support upkeep a build step instead of a monthly chore.

No signup to start

Codex can spin up a real, trained chatbot from a URL with no SiteGPT account. You only sign up to keep it.

Steal these

Prompts worth keeping in the repo notes

Everything below runs against your live account once connected. Reads run freely; anything that changes data asks first.

“Create a support chatbot for the site in this repo and train it on ./docs.”

Bot created, docs ingested, embed snippet in the diff.

“What are users asking the support bot about the API?”

Clustered questions from live conversations, straight into your planning.

“Sync the bot’s knowledge with the docs I just edited.”

Changed sources re-queued for training, with approval on the write.

“Show conversations where users hit errors this release and cluster the causes.”

A triage view of what the release actually broke, from real reports.

Codex + SiteGPT, answered

Can Codex connect to remote MCP URLs directly?: Not today: Codex launches stdio processes from config.toml and has no remote-URL form. The bridge pattern costs you nothing though: npx -y @sitegpt/cli mcp is the same server, same account, and same three tools as the remote endpoint, and if Codex adds remote support later your grant carries over unchanged.
How do I connect SiteGPT to Codex?: Add a [mcp_servers.sitegpt] entry to ~/.codex/config.toml that runs npx -y @sitegpt/cli mcp, or install the CLI and call it directly. Codex can then build and manage chatbots.
Does it work without a SiteGPT account?: Yes. Codex can create and train a chatbot from a URL with no credentials and return a preview-and-claim link.
Can I use it in CI?: Yes. Mint a scoped token with sitegpt tokens create, pass it via SITEGPT_API_TOKEN, and script every step with --json output and stable exit codes.
Codex cannot reach SiteGPT. How do I debug it?: Run the exact command from your config.toml by hand: npx -y @sitegpt/cli mcp. The standalone run surfaces the real error, almost always a pending browser sign-in or a revoked grant. Once it works in a bare terminal it works in Codex, because Codex launches the same process.

The same platform trusted with real support traffic