Integrations · Codex

Reads run free.
Every write asks.

Codex can prompt only on write tools and let reads run without interruption. That is exactly the contract marketing needs. Two commands, one config line, and Codex drafts campaigns from your real business context while every write waits for your approval, twice: once in Codex, once in Marqeable.

Get early accessRead the blog
Connect in minutes

One URL. Sign in once.

Codex CLI and the desktop app read the same config. Codex Cloud and ChatGPT on the web do not; use the ChatGPT connector there.

Steps verified against the Codex MCP docs on 1 September 2026. Vendors rename menus often; if a step looks different, the server URL is the part that does not change.

  1. 1

    Add the server.

    codex mcp add marqeable --url https://app.marqeable.com/mcp
  2. 2

    Sign in with your Marqeable account.

    codex mcp login marqeable
  3. 3

    Put the server in writes-approval mode so reads never interrupt you and every draft write asks.

    # ~/.codex/config.toml
[mcp_servers.marqeable]
default_tools_approval_mode = "writes"
  4. 4

    Run the first prompt below.

Codex desktop app
  1. 1

    Settings, then MCP servers, then Add server. Choose Streamable HTTP and paste the server URL.

    https://app.marqeable.com/mcp
Your first prompt

Ask Codex what is on the calendar.

Start with a read so you can see the assistant using your real business context. Then ask for one draft and open Marqeable to find it waiting for approval.

Run whoami, then get_business_context, then tell me what is on the calendar this month. The landing page in this repo went live last night; draft the three-email nurture for everyone who signs up on it.
Tools called
whoamiget_business_contextget_content_calendarcreate_automation_draftcreate_content_draft
In Marqeable: an automation draft with three emails, triggered by the signup, not launched until you approve the dry run.

Every write is a draft. No send, launch, or delete tools.

Good to know

Specific to Codex

Why writes mode works here

Writes-approval mode relies on the server labelling its tools honestly. Every Marqeable write is annotated as a write, and every one of them produces a draft, so the prompt you see is the last gate before a draft, not before a send.

You shipped the site. Ship the nurture.

Codex gets a founder from idea to live landing page in an evening. The signups then arrive and nothing happens. Draft the follow-up from the same session and approve it in Marqeable.

Local config only

Codex Cloud and ChatGPT on the web ignore ~/.codex/config.toml. For the web, connect through ChatGPT Developer mode instead; the server is the same.

What the assistant can do

Reads everything. Writes only drafts.

Judge any connector by its tool list. This is ours, in full. There is no send, launch, or delete tool, so a bad prompt, a scheduled run, or a poisoned web page can never reach your list. The gate is structural, not a permission click.

Reads
  • get_business_contextBrand, voice, offer, audience, what you sell and to whom.
  • get_content_calendarWhat is scheduled, so a draft never collides with a send.
  • list_campaignsEvery campaign and its status.
  • get_campaignOne campaign, all its pieces.
  • search_contentFind last quarter's launch email before rewriting it.
  • get_contentOne piece, full copy and brief.
  • get_automation_overviewWhich automations are live and who is inside them.
  • get_automation_planThe steps, timing, and triggers of one automation.
  • search_image_libraryImages you already own, so nothing is regenerated by accident.
  • whoamiWhich user and account the assistant is acting as.
Drafts and reviews
  • create_campaign_draftA campaign with its pieces, saved as a draft.
  • create_content_draftOne email, post, or page. Copy first, no image spend.
  • create_automation_draftA follow-up sequence, assembled but not launched.
  • update_automation_draftChange a step or the timing on a draft.
  • update_content_briefAdjust the brief before the copy is written.
  • add_content_suggestionLeave a note on a draft for whoever reviews it.
  • request_content_changesSend a draft back with what to fix.
  • approve_content_buildSay yes to the images for a draft you have already read.

Sign-in is OAuth 2.1 per user, so no API key is ever pasted into a chat. Multi-account users also get list_accounts and switch_account.

Also connects toClaudeChatGPTClaude Code
Further Reading

Codex and Marqeable, in depth

Codex MCP for Marketing: Put Codex in Writes Approval Mode and Give It Your Campaigns

Codex can prompt only on write tools and let reads run free. That is the contract marketing needs. The config, why it depends on how the server annotates its tools, and one full session.

Read article

You Shipped the Site with Codex. Nobody Shipped the Nurture.

Codex Sites gets a founder from idea to live landing page in an evening. Then the signups arrive and nothing happens. What the page cannot do, and how to draft the follow-up.

Read article

Does It Have an MCP Server? The One Question to Add to Every Martech Evaluation

In 2026 the assistant is the interface and the platform is the backend. A seven-line checklist for judging any marketing tool by its MCP server.

Read article

Draft in Codex. Approve in Marqeable. It runs.

Marqeable is in private beta with a small early cohort. Connect your assistant on day one; hands-on onboarding is included.

Get early accessSee it live