You built something in Codex. Now let's get it live.
This guide covers the full path from generated code to a public URL: pushing your project to GitHub, connecting it to Hostman App Platform, and deploying. We'll also set up the GitHub MCP so Codex can create repos and push code on your behalf—no manual git required.
You will need:
You'll need a GitHub account to host your code and connect it to the platform.

Codex needs a token to interact with your GitHub account—creating repos, pushing files, that sort of thing.
GitHub may ask for your password at this point—that's expected.

Fill in the token details:
|
Field |
Value |
|
Note |
Something like |
|
Expiration |
No expiration (so you don't have to redo this) |
Select scopes:
repo: full repository access (create, edit, push)admin:org: only needed if you're working with org reposThat's enough for everything in this guide. Don't select all scopes—there's no need to grant more access than necessary.
Treat this token like a password. If it's ever exposed, revoke it at github.com/settings/tokens and generate a new one.
MCP lets Codex act on your GitHub account directly from the chat interface. Here's how to wire it up.
In Codex:
|
Field |
Value |
|
Name |
GithubMCP |
|
Type |
HTTP Streaming |
|
URL |
|
|
Bearer token env var |
|
Save and fully restart Codex.
Set the environment variable:
Now expose your token to the system. Pick the option that fits:
Open Terminal and run:
For the current session only:
launchctl setenv GITHUB_TOKEN 'your-token-here'
To make it permanent across restarts:
echo 'export GITHUB_TOKEN="your-token-here"' >> ~/.zshrc && source ~/.zshrc
Replace your-token-here with the token you generated in Step 2.
Open PowerShell and run:
For the current session only:
set GITHUB_TOKEN=your-token-here
To make it permanent:
setx GITHUB_TOKEN "your-token-here"
Replace your-token-here with the token you generated in Step 2.
After running the command, restart Codex so it picks up the variable.
Verify it's working:
In the Codex chat, ask:
What MCP tools do you have available for GitHub? List all of them.
If you get a list of tools back—you're good to go.

Something not working? Ask Codex to check your config file:
~/.codex/config.tomlC:\Users\<your-username>\.codex\config.tomlWith MCP connected, you can create a repo and push your code straight from the chat.
Create the repository:
In your Codex project chat, type:
Create a new public GitHub repository called my-app
Codex will ask for permission to run the action—confirm it. You can verify the repo was created at github.com.

Push your code:
Push the project from the current directory to that repository using the GitHub MCP.
Heads up: Explicitly mention the GitHub MCP—otherwise Codex may try to use local git, which can fail if git isn't installed or configured on your machine.
Confirm the action when prompted. When it's done, open the repo on GitHub and confirm your files are there.
Now let's get your app running.
Option A: Connect your GitHub account (recommended)
Gives you access to all your repos and enables auto-deploy—your app will redeploy automatically whenever you push changes.
If the repo doesn't appear, click Add Account, re-authorize, and try again.

Option B: Connect via URL
Good if you'd rather not grant full account access, or if your code is on a different Git host.
Note: auto-deploy isn't available with this method. You'll need to trigger deploys manually after each push.
Finish the setup:
Click Order and wait for the deploy to finish.
Once deployment completes, go to Dashboard → look for the Domain field. That's your app's public URL.
Want a custom domain? Head to Settings to configure it.
Once MCP is set up, pushing updates is just a chat message away. Whenever you make changes to your project, just tell Codex to push them and Hostman will pick up the new commit and redeploy automatically.