Claude Code vs Oxygen (announcing the MCP server)

Every other sales call I take opens with the same question.

"How is Oxygen different from Claude Code?"

They're not competitors. Use both.

We just shipped the OXYGEN MCP server. 120+ GTM integrations. One endpoint. Plug it into Claude Code and your agent can hit your full GTM stack without you fighting environment variables, OAuth tokens, or onboarding the rest of your team to your local dotfiles.

Here's how I think about the split:

→ Claude Code is the open dev sandbox. Use it to build, hack, and ship custom workflows. → OXYGEN is the purpose-built GTM agent. Think of it as the execution layer and memory layer of your GTM. Native tables, native signals, compounding memory across every run, skills your team actually uses.

The two compose well.

Example I keep coming back to. You ship a new feature in Claude Code. Then you tell your OXYGEN agent: "plan and execute the launch campaign for this feature. Pull the ICP from our database, pick the angle, draft the LinkedIn post, queue the outbound sequence, schedule the webinar."

That second step is what an MCP server alone can't do. It needs an agent that already knows your ICP, your tone, your offer, your last 30 campaigns, and has the rights to act on your stack.

Claude Code for the dev work. OXYGEN for the GTM work. The MCP server is the bridge.

Link in the comments if you want to plug it in.