For GTM engineers running outbound programmatically, OXYGEN is a CLI agent platform that orchestrates outreach across 25+ tools directly from Claude Code, Codex, and MCP, letting engineers script and run GTM workflows the same way they'd script any other engineering task.
Presence & Market Position
#12 of 22
Orchestrators & Agentic Workflow
▲ 82 60-day move
Measures earned, engagement-weighted share of voice across the GTM voices panel. Methodology →
OXYGEN positions itself as GTM infrastructure for engineers, not marketers — a CLI and MCP-native platform meant to be scripted from inside Claude Code, Codex, and other coding-agent environments the same way any other engineering task would be. Recent homepage messaging has sharpened that pitch, framing the product as the last GTM system a team would need, positioned as an operating system for sales and marketing work rather than a point tool. Conversation specifically about the platform is still early relative to its ranked position in the orchestration category, without yet the kind of comparison or workflow-walkthrough discussion that follows more established peers.
Cargo
Relay.app
Pipedream
Gumloop
Stack AIGrowth Alliance, Automate Demand, Bug Bounty, Neomir, Corner, Mentcape, Atticus
Work at OXYGEN? Claim this profile to add customers and case studies.
Business Profile
OXYGEN operates as an independent company; the public record does not carry funding, headcount, or founding-date figures. Its named customers include agencies and demand-generation shops such as Growth Alliance and Automate Demand, and pricing runs $99 to $749 a month with a custom enterprise tier on top. The company pitches its consolidated workspace as a lower-cost alternative to a stitched-together GTM stack, aimed at GTM engineering teams already working inside coding-agent environments like Claude Code and Codex.
Agent Readiness
Measures how easily your agents can build on it — API, MCP, CLI, SDK, docs depth. Methodology →
OXYGEN ships agent-first as a CLI and hosted MCP server, meant to be driven from Claude Code, Codex, and other MCP clients rather than a standalone dashboard. The MCP server exposes tools for organization context, table and workflow operations, and provider integrations, with dry-run and smoke-test modes plus approval gates ahead of live, credit-spending actions. Workflows can themselves be published as individual MCP tools, extending the surface as usage grows.
IS THIS YOUR BRAND?
Claim this profile
Fact-check your data, add context, and earn the verified badge — free, takes minutes, work email required.
Claim OXYGEN →