Codex MCP setup

Upload files from Codex with Munition MCP

Codex MCP can call Munition's local server to upload reports, screenshots, JSON, and other artifacts. Munition gives AI agents paid tools they can actually use: file upload today, memory next, paid over x402 without API keys or wallets inside the agent.

Keywords: codex mcp, codex cli mcp, MCP file upload, x402 receipt

Install Munition MCP for Codex

Add the Munition MCP server to the Codex MCP config. If your Codex build uses TOML, keep the same command and env values under its MCP server section.

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

[mcp_servers.munition.env]
MUNITION_API_URL = "https://api.munition.io"

Prompt example

Copy this shape into the agent once Munition is installed.

Upload ./reports/q4-summary.pdf with Munition, tag it q4 and board, then return the public URL and the x402 receipt.

Expected result

A successful run should be explicit about the action, output, and paid call.

  • 01

    Codex calls the Munition upload tool with the local path and tags.

  • 02

    Munition charges 0.005 USDC from the local account wallet over x402.

  • 03

    The response includes a public file URL, expiry timestamp, tags, and a receipt similar to {"protocol":"x402","network":"base","amount":"0.005 USDC","resource":"upload"}.

  • 04

    If Codex cannot see the tool, reopen the session after saving the TOML/config and confirm npx can run from the same shell.

Limits and privacy

Use Munition for short-lived shareable agent artifacts, not for access-controlled storage.

  • 01

    Uploads cost 0.005 USDC, are limited to 10 MB, and are retained for 7 days by default.

  • 02

    Uploaded files are public to anyone with the URL. Do not upload secrets, regulated data, or files that should not be public-by-link.

  • 03

    The agent runtime does not need a Munition API key or wallet secret; account and payment state stay in the local Munition MCP server.

Follow the setup path for your client or read the paid upload and x402 model.

FAQ

Short answers for agents and humans configuring Munition.

Does Codex need an API key for Munition MCP?

No. Codex calls the local MCP server, and the local Munition account handles x402 payment state.

What if Codex uses a JSON config instead of TOML?

Use the same npx command, args, and MUNITION_API_URL env value from the setup block in the JSON shape your Codex build expects.

Can Codex upload directories?

Upload a single file up to 10 MB. Zip a directory first if you need to share several files.

Where do receipts appear?

Paid tool responses include receipt fields from the x402 flow; ask Codex to print them when you need an audit trail.

Next step

Give Codex a real upload action

Install Munition MCP, fund the local account, then ask Codex to publish an artifact from your workspace.

Read setup instructions