Omentir

Codex integration

codex illustration for Omentir

Endpoints

MCP
https://omentir.com/api/agent/v1/mcp
REST
https://omentir.com/api/agent/v1/*

Setup

  1. 1

    Create and export a token

    Generate an Omentir API key and export it as OMENTIR_API_KEY before you launch Codex.

  2. 2

    Add mcp_servers.omentir

    In ~/.codex/config.toml, set url to https://omentir.com/api/agent/v1/mcp and bearer_token_env_var to OMENTIR_API_KEY.

  3. 3

    Confirm with /mcp

    If the server is missing, the env var was empty, the table name is wrong, or a project file is in an untrusted repo.

  4. 4

    Read before write

    Fetch agents.md, then get_context and list_agents, before you let Codex create a finder.

Why Codex users connect Omentir

Codex is already in the repo. Connected to Omentir, it can read My Product, inspect finders, and leave a scored list without becoming a LinkedIn client. The CLI and the IDE extension share ~/.codex/config.toml. ChatGPT's connector list is a different store.

Setup in config.toml

Create a revocable API key. Export it before you launch Codex. Add an mcp_servers.omentir table. The table name needs an underscore. bearer_token_env_var is the name of the variable, not the token and not $OMENTIR_API_KEY.

  • url: https://omentir.com/api/agent/v1/mcp
  • bearer_token_env_var: OMENTIR_API_KEY
  • Confirm with /mcp in the session
  • Project-local .codex/config.toml only loads for trusted projects

Codex versus ChatGPT chat

ChatGPT uses Settings, Connectors, and workspace approval. No API key for that path. Codex uses TOML and a Bearer env var. Do not paste a token into the ChatGPT connector UI. Do not wait for workspace approval inside Codex.

A first Codex session that does not invent targeting

Codex moves fast in a repo. Treat create, delete, and reply as named requests. Ask it to show a create_agent config and wait. A refactor that also spins up a finder is how targeting drifts.

Keep LinkedIn off Codex. Caps and send stay in Omentir. Close the session and the work stops.

When ChatGPT chat is the better surface

If you wanted a conversation this afternoon with no repo open, use the ChatGPT connector. Codex earns the TOML file when that coding agent is already the loop you live in.

Frequently asked questions

You can. You should not. The file is easy to commit. Use bearer_token_env_var with the variable name.

Only through Omentir tools under your campaign and safety settings. Your prompts should still require approval for replies and agent lifecycle changes.

https://omentir.com/agents.md is the operator guide. Fetch it before you let Codex create a finder.

Connect your operator to a real sales workspace

Omentir holds the LinkedIn connection and safety limits. Your AI configures agents and inspects results.

Get startedMCP overview

Prefer markdown? Codex integration.md