Pounce AI
Pounce for CodexUse Pounce in Codex
Pounce for Codex connects OpenAI’s coding agent to Pounce’s MCP server, so Codex can pull South African businesses, signals and tenders into the work you give it.
Set it up
Works with Codex’s MCP support. Pounce’s MCP server needs a Growth or Agency plan.
Make the key in Pounce: Settings, API keys (Growth and Agency plans). Treat it like a password.
Put the key in an environment variable Codex can read:
export POUNCE_API_KEY=YOUR_KEYAdd the server:
codex mcp add pounce --url https://app.pounce.co.za/mcp --bearer-token-env-var POUNCE_API_KEYRun codex mcp list to see Pounce, then start Codex.
Check it works
Ask: “Use Pounce to match the companies in customers.csv and add a column with their latest signal.”
Then ask for what you need
- “Find steel fabricators in Ekurhuleni with a website”
- “Open the full record for the third one”
- “Which construction companies in KwaZulu-Natal won contracts this month?”
- “Show my ten best leads and why each fits”
- “Which cleaning tenders close this week in Gauteng?”
- “Here are my 20 customers: which of them had news lately?”
- “Draft an email to that contractor about our plant hire”
- “How many export rows have I used this month?”
The MCP server and the API come with the Growth and Agency plans. Each business returned with its contacts uses one export row, as a CSV row does.