Growcita in OpenAI Codex
Codex launches MCP servers as local processes configured in ~/.codex/config.toml. Either snippet below connects it to Growcita's hosted endpoint.
Option 1 — npm wrapper
Add to ~/.codex/config.toml. The wrapper proxies stdio to the hosted MCP server using your key from the environment:
[mcp_servers.growcita]
command = "npx"
args = ["-y", "@growcita/mcp"]
env = { GROWCITA_API_KEY = "gcta_YOUR_KEY" }Option 2 — mcp-remote bridge
The widely-used mcp-remote package bridges stdio to any Streamable-HTTP server and works with every Codex version that supports MCP:
[mcp_servers.growcita]
command = "npx"
args = [
"-y",
"mcp-remote",
"https://growcita.com/api/mcp",
"--header",
"Authorization: Bearer gcta_YOUR_KEY"
]Recent Codex releases can also connect to Streamable-HTTP servers natively — if yours does, point it at https://growcita.com/api/mcpwith the same Authorization header per OpenAI's MCP documentation.
Verify
Restart Codex and ask it to "list Growcita sessions" — the six tools (list_agents, list_sessions, create_session, run_agent_task, get_task, list_tasks) should appear in its tool list. A 401 means the key was mistyped, revoked, or expired.
No MCP? Use the REST API
Everything the tools do is also plain HTTPS — handy inside Codex scripts:
curl -X POST https://growcita.com/api/v1/tasks \
-H "Authorization: Bearer $GROWCITA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"sessionId": "SESSION_UUID", "instruction": "Draft a week of LinkedIn posts about our new feature", "agentType": "organic-social"}'Full reference on the REST API page.
Things to ask
Use Growcita to run a CRO audit of our signup flow and turn the findings into TODO comments in the onboarding code.Ask Growcita's demand-gen agent for an ICP definition based on our positioning, then poll until the task completes.Runs take 1–5 minutes and respect your approval settings — see the MCP server page for the full tool reference.