MCP & IDE agents
Wire OpenAI Codex to Piloterr in config.toml
Codex reads MCP servers from ~/.codex/config.toml, not .mcp.json. Point url at mcp.piloterr.com and pass x-api-key in http_headers so the coding agent can call the library.
- TOML only: ~/.codex/config.toml, mcp_servers table, http_headers
- OpenAI Codex CLI and IDE, not ChatGPT Developer mode
- Hosted Streamable HTTP, full Piloterr tool list
- Same credits as REST, no extra Codex-specific plan
At a glance
TOML
config.toml
~/.codex
home config
190+
library tools
HTTP
MCP url
Why connect Codex
Codex does not read Cursor files
A project .mcp.json is invisible to Codex. If you use both tools, keep Cursor JSON and Codex TOML in sync by hand.
http_headers, not a CLI --header
Put x-api-key under the server’s http_headers table. There is no claude mcp add equivalent.
Built for implementation agents
Codex is a coding agent. Hosted MCP gives it live product, SERP, and crawl data while it edits your client.
Health check stays in the browser
https://mcp.piloterr.com/health is plain HTTP. The MCP root URL is not. Codex talks to the root with protocol headers.
Codex-specific Piloterr work
TOML and OpenAI’s agent, not a Claude or Cursor clone.
Generate a typed client from live JSON
Codex calls an Amazon or company tool, then writes Zod or Pydantic models from the real payload.
Home-directory config
Servers live under ~/.codex. That is user-global. Do not expect a per-repo TOML unless you document a copy step.
Pair with AGENTS.md
Tell Codex to use Piloterr tools when a target is behind Cloudflare, instead of inventing a scraper.
No Developer mode UI
ChatGPT’s remote connector is a different product. Codex is file-based MCP. See the ChatGPT page for the connector.
Codex vs ChatGPT for Piloterr
| Approach | DIY | Piloterr |
|---|---|---|
| Config | ChatGPT: dashboard connector | Codex: ~/.codex/config.toml |
| Primary UI | Chat thread | Coding agent in a repo |
| Header name | UI secret field | http_headers.x-api-key |
| Shares Cursor JSON | No | No, TOML is separate |
Add Piloterr to Codex
Step 1
Create an API key
Copy x-api-key from the Piloterr dashboard.
Create an API keyStep 2
Edit ~/.codex/config.toml
Add an mcp_servers.piloterr table with url https://mcp.piloterr.com/ and http_headers for x-api-key.
Step 3
Restart Codex
Reload the CLI or IDE so it re-reads TOML. Confirm the server name appears.
Step 4
Ask Codex to call a tool
“Use the Piloterr crawler on this URL.” If tools are missing, validate TOML indentation and the trailing slash on the URL.
Workflow recipes
Scaffold an SDK method from a live offer
Codex calls a product-offer tool, then writes the method and a fixture in one pass.
Repair OpenAPI comments
It fetches a domain or company payload and updates stale field notes in your spec.
Build a small enrich CLI
Codex implements a bin that wraps one Piloterr REST route, using MCP only while coding, REST in production.
Check WAF before you ship a crawler
One WebUnlocker call from Codex, then it decides whether your DIY fetch is hopeless.
When Codex is the right MCP client
Scenario
You already run OpenAI Codex
Recommendation: This page, config.toml
Scenario
You want a ChatGPT connector
Recommendation: ChatGPT Developer mode
Scenario
You want Anthropic’s CLI
Recommendation: Claude Code
Scenario
You want Google’s CLI
Recommendation: Gemini CLI
Codex TOML snippet
Home file, not a repo .mcp.json. Replace the key. Keep this file out of screenshots.
[mcp_servers.piloterr]
url = "https://mcp.piloterr.com/"
[mcp_servers.piloterr.http_headers]
"x-api-key" = "your-x-api-key"See also
MCP
ChatGPT
Claude Code
CursorTransparent credit pricing
Pay only for successful requests. Start with +500 credits, then scale with plans from $49/mo.
Premium
$49/mo
18,000 credits
Premium+
$99/mo
40,000 credits
Startup
$249/mo
110,000 credits
Ready to get started?
Your web scraping API is one click away. Start with +500 credits, no infrastructure to set up, no proxies to manage, and no credit card required.
- +500 credits
- No credit card required
- All endpoints included