Codex connection guide
Codex connection guide. Follow concrete contracts, examples and reviewable steps using Xiaohongshu (RedNote), Douyin, WeChat Official Accounts.
Copy the agent prompt manually
Choose a reachable transport
Before configuring Codex, verify whether your installed version supports local stdio, HTTP MCP or explicit HTTP requests.
A client on this computer can test stdio. Localhost inside a container, remote desktop or remote runtime identifies that environment and must be checked separately.
Local configuration example
Replace the placeholder with the absolute project path. This configuration contains no provider key and defaults to demo.
{
"mcpServers": {
"guanliu": {
"command": "node",
"args": [
"/ABSOLUTE/PATH/guanliu/scripts/mcp-server.mjs"
],
"env": {
"GUANLIU_MCP_MODE": "demo",
"GUANLIU_MCP_PORT": "4321"
}
}
}
}First reviewable request
Ask the client to describe xiaohongshu.notes.search, inspect its inputs, and explicitly run a fixture. Retain request_id.
{
"capability": "xiaohongshu.notes.search",
"params": {
"query": "local sample",
"sort": "relevance"
},
"mode": "demo"
}Connection checks
| Check | Expected result |
|---|---|
| Website reachability | http://127.0.0.1:4321/api/health |
| Discovery | find → describe |
| Transport boundary | Same-host process; verify the client version |
| Live execution | Disabled; local fixtures or TEST simulation |
| Result recovery | account what=receipt / result |
Clear inputs. Inspectable output.
Each click runs a local fixture. Advanced JSON inputs are checked against the selected method. Editing does not execute a request.
Copying does not execute. CLI quote is read-only and needs a local customer TEST key. Configure MCP in demo mode first. GET and POST batches both return only fictional local fixtures.
Download contract example (no execution) ↗For TEST budgets, Key scopes or failure scenarios, open the account console. Customer sandbox ↗