Does Klipy have a native Codex connector?

No. Codex connects the same way every client besides Claude and ChatGPT does: add Klipy's remote MCP server (https://api.klipy.ai/mcp) from Codex's own connector settings and complete OAuth. There's no bundled one-click Codex app.

Can Codex send emails or messages through Klipy on its own?

No. Codex can prepare a draft, but sending always requires prepare_message_send to generate a preview and a single-use confirmation token, then your explicit approval before send_message_draft dispatches anything.

Does connecting Codex cost anything extra?

No. Klipy MCP is generally available on every plan, including Free. You spend tokens only when you accept an action, like sending a draft or applying a suggested CRM update.

What can I limit Codex to doing?

Choose from nine OAuth scopes when you connect, for example crm:read and comms:draft for a read-and-draft-only setup. Anything you leave unchecked stays unavailable to that connection.

Where do I find the exact connection steps for my version of Codex?

Codex's own documentation governs the exact settings screen and config format on its side. Klipy's side is identical for every client: the endpoint URL and the OAuth consent screen described in Klipy's 'other clients' guide.

MCP agent

Codex, connected to your CRM

Add Klipy's MCP server to Codex over OAuth, then ask it to read your pipeline, draft follow-ups, or update deals. You review everything before it sends.

Start free See all integrations

Free on every plan

Connecting Codex is included on every Klipy plan, including Free. API access, webhooks, and the MCP server ship standard, with no add-on fee.

Quick answer

Codex reaches your CRM data, inbox, and meeting history through Klipy's MCP server at api.klipy.ai/mcp, gated by OAuth and nine capability scopes. Codex can read records, draft follow-ups, and surface CRM updates. Sending a message still needs a human to approve a fresh confirmation token before it goes out.

Ask ChatGPT Ask Perplexity Ask Claude

At a glance

What you need to know

38

MCP tools

One remote endpoint (api.klipy.ai/mcp) exposes 38 tools across CRM, comms, and meetings.

9

OAuth scopes

Grant only what a workflow needs, for example crm:read plus comms:draft for read-and-draft-only.

$0

Free on every plan

Klipy MCP is generally available on every plan, including Free; tokens spend only when you accept an action.

Codex can't reach your CRM on its own: Klipy's MCP server closes that gap

Codex is OpenAI's agentic coding tool. On its own, it has no way to read a pipeline, a meeting transcript, or a conversation thread. Connect it to Klipy's MCP server and Codex gains a second surface, your sales data, over the same Model Context Protocol it already uses to reach other tools.

Klipy doesn't drive, extend, or run Codex. Codex calls Klipy, never the reverse. Klipy and Codex aren't in competition, so there's no /compare/codex page: this is a capability gap Klipy's MCP server closes, not a competitive one.

How Codex connects to Klipy

Klipy publishes one remote MCP server for every client: https://api.klipy.ai/mcp, authenticated over OAuth 2.0. Klipy's own docs walk three named clients through step-by-step guides: Claude Desktop, Claude Code, and ChatGPT. Codex isn't one of the three yet, so it follows the generic "other clients" path instead.

Open Codex's own MCP or connector settings.
Add Klipy as a remote HTTP server pointed at https://api.klipy.ai/mcp.
Complete the OAuth consent screen, checking only the scopes your workflow needs. Nine capability scopes gate 38 tools, so a read-and-draft-only setup can grant crm:read plus comms:draft and stop there.
Confirm the connection by asking Codex to call get_current_user.

Anything you leave unchecked on the consent screen stays unavailable to that connection. Confirm one thing on Codex's own side first: whether its current MCP support reaches remote HTTP servers with OAuth, the mode Klipy's server requires. That's governed by Codex's own documentation, not Klipy's, so check there before wiring this up. If the connection doesn't come up cleanly, Klipy's MCP troubleshooting guide covers the client-agnostic failure points.

Use cases

What you can do with it

I can now ask a grounded question across my CRM and conversations without leaving Codex.

ask_klipy retrieves the matching interactions and answers with citations back to the source, read-only, no writes.

Ask your data

I can now turn a recorded call into CRM updates I review before they land.

Codex reads the transcript and surfaces the changes Klipy's agent already proposed; only the ones I accept apply.

CRM updates

I can now draft a follow-up grounded in the actual call or thread, then approve it before it sends.

Sending still runs through the prepare_message_send and send_message_draft token handshake.

Follow-up emails

Trade-offs

Pros and cons

Pros

One remote endpoint (api.klipy.ai/mcp) works the same way for Codex as it does for Claude, ChatGPT, or Cursor, no Klipy-specific SDK to install.
Scope-level consent lets you keep a Codex-driven workflow read-only or read-and-draft, with no write or send access granted at all.
The send handshake (prepare_message_send, then send_message_draft with a fresh token) is identical for every client, so a coding agent can't dispatch a message on its own.
Klipy MCP is generally available on every plan, including Free, with no separate add-on or waitlist.

Cons

Klipy hasn't published a dedicated connect-Codex guide yet; setup follows the generic other-clients flow instead.
Codex's own documentation, not Klipy's, decides whether its MCP support covers remote HTTP servers with OAuth.
delete_crm_record and other write tools are irreversible once you grant the crm:write scope, the same caution that applies to any MCP client.

Sources