Using Codex and IDE agents for editorial workflows

If you live in an IDE or a coding agent, you don't want another browser tab for content. Niche runs over MCP, so an agent like Codex (or any IDE agent) can drive the whole editorial workflow from where you already are.

One engine, two surfaces

The browser desk and the agent surface call the same engine. So a story your IDE agent surfaces is the same story, ranked the same way, with the same grounded synthesis a human would get on the web. There's no second-class agent path.

The workflow

1. Connect the MCP endpoint to your agent. (See integrations.)
2. Scan a niche — the agent gets a ranked slate of stories with provenance.
3. Ask for the intelligence — emerging narratives, where investment is moving, the strongest angle — and the engine returns it grounded.
4. Signal-to-story — pick a story, propose angles, draft the platform-native version, all as tool calls. No context-switch, no copy-paste.

Why it's reliable

Long research runs return a session id immediately and the agent polls for the result, so a slow scan never hangs a tool call. The agent does other work while discovery runs.

---

Niche is editorial intelligence for individuals — it finds the stories worth writing about, then turns that signal into publishable content. Start the 3-day trial or connect it to your agent.