Skip to content

Deploy Full-Stack Apps with Codex and Rivtor

Codex can use the Rivtor CLI or its local MCP server to upload a project folder. Supply Rivtor authentication through the documented configuration and review the deployment plan before releasing the app.

Choose the right connection

The local MCP server uses the same Rivtor package as the terminal CLI. Keep authentication out of committed project configuration. Check which folder the agent is deploying and use project-scoped credentials where suitable. A successful tool connection does not itself deploy anything.

Configure the MCP connection

Create a Rivtor token through your account’s token page. Replace the placeholder in this configuration with that token using your client’s supported secret workflow. Do not commit credentials to Git.

Codex MCP configuration
[mcp_servers.rivtor]
command = "npx"
args = ["-y", "rivtor", "mcp"]
env = { RIVTOR_TOKEN = "rvt_..." }

Configuration screens and client capabilities can change. Check the official Codex MCP documentation and Rivtor’s connection reference for setup details.

Ask for a plan before deployment

Ask the agent to inspect the service roots, required environment names and data dependencies. Review the selected project and any missing secrets before approving a deploy. The first call can need input; do not tell the agent to invent credentials or disable checks to proceed.

Example agent prompt
Inspect this folder for Rivtor deployment. Use the local MCP connection or CLI for upload, explain the target project and deployment plan, and wait for approval before release.

Codex setup and troubleshooting checklist

  1. Add the local MCP configuration to the Codex configuration file described in the official client reference, keeping the real token out of the project repository.
  2. Confirm the local process can run Node and npx, and that RIVTOR_TOKEN is supplied through the chosen private configuration.
  3. Check the selected working directory before upload. Read any tool error before retrying; a private report link still requires an authorized Rivtor session.

Keep deployment credentials in your private client configuration. Reconnect after replacing an expired token; never paste a credential into a public support question.

Read the deployment result

A deployment status and an application verification verdict answer different questions. Inspect the live URLs, verification issues and skipped checks. Read structured cause and fix fields when a release fails, then repair the relevant service and retry deliberately.

Frequently asked questions

Does connecting MCP deploy my app?

No. Connecting makes tools available. A deploy is a separate operation against a selected project.

Can the remote server read local files?

No. Use the local MCP server or CLI for uploading folders. Remote deployment uses supported Git sources, starters or inline files.

Where do the app and database run?

Rivtor’s container apps and data services run in India. Static assets can be served through Cloudflare’s edge. Check the current limits and evaluate dynamic latency for your users.

Read a complete deployment guide →