# Connecting an agent to Oddlynew (setup steps)

You are reading this because a user wants to connect Oddlynew to their AI client and you are guiding them through it. You cannot add the connector from inside a chat; the user does it in their client's settings while you guide them. Give one step at a time, wait for confirmation, and adapt when their UI differs slightly (client UIs change faster than this page).

The MCP server URL to enter everywhere below is:

```
https://mcp.oddlynew.com/mcp
```

Signing in happens through the browser with the user's Oddlynew account.

## Check the plan first

As of 29 September 2026, from the vendors' own documentation. Ask which plan the user is on before the first step; if their plan cannot add a connector, say so instead of walking them through menus they will not find.

- **ChatGPT on the web:** adding a connector needs developer mode, which is not on the Free plan and works only in ChatGPT on the web, not in the phone app (a phone browser works). Reading and writing through a connector is supported on Business, Enterprise and Education. On Business only admins and owners can use developer mode; on Enterprise and Education an admin grants it first (Permissions & Roles, then Connected Data). On Plus and Pro, OpenAI documents developer mode connectors as read and fetch only, so tell the user their agent may not be able to change documents from there.
- **Codex in the ChatGPT desktop app:** Codex is its own view in the desktop app, separate from Chat and Work, and it does not use developer mode. It keeps its own list of MCP servers, shared with Codex CLI and the Codex IDE extension, so a server added in one of them is there in the others.
- **Claude:** custom connectors work on every plan. The Free plan allows one custom connector. On Team and Enterprise plans only an Owner can add it for the organization; each member then connects it for themselves.
- **Codex:** version 0.147.0 or later.
- **Cursor:** Cursor's MCP documentation names no plan requirement (read 13 October 2026). On a team, an admin can limit which servers members may add (an MCP allowlist in the team settings).

## Claude (web or desktop app; one connection covers both)

On a Team or Enterprise plan, an Owner first adds the connector for the organization: **Organization settings**, then **Connectors**, click **Add**, hover over **Custom** and choose **Web**, paste the MCP server URL, and click **Add**. Members then skip step 2 below and find Oddlynew in their list, usually with a "Custom" label.

Shortcut: give the user this link. It opens Claude's **Add custom connector** dialog with the name and the MCP server URL already filled in, so steps 1 and 2 shrink to clicking **Add**:

```
https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Oddlynew&connectorUrl=https%3A%2F%2Fmcp.oddlynew.com%2Fmcp
```

Without the link:

1. Open **Customize**, then **Connectors**.
1. Click the add (**+**) button and choose **Add custom connector**. Enter the name `Oddlynew`, paste the MCP server URL, and click **Add**.
1. Click **Connect** next to Oddlynew and complete the Oddlynew sign-in.
1. Set both Oddlynew tools, guide and run, to **Allow always**: in **Customize**, then **Connectors**, open Oddlynew and change each tool from asking to always allow, or choose **Allow always** the first time Claude asks. Oddlynew is meant for an agent that works on its own; actions through the organization's integrations that matter, such as sending mail or spending money, still wait for an organization admin inside Oddlynew. To turn Oddlynew on or off for one conversation, use the **+** button at the lower left of the chat, then **Connectors**.

## ChatGPT (web, including a phone browser)

Developer mode connectors work only in ChatGPT on the web, from a laptop or a phone browser; OpenAI does not offer them in the phone app. Codex in the desktop app connects differently; see the next section.

1. Turn on developer mode: click the profile (bottom left) and open **Settings**. On Business, Enterprise and Education it is under **Apps**, then **Advanced settings**; on Plus and Pro OpenAI documents it under **Security and login**. Enable **Developer mode** there. If it is not where you expect, search "developer mode" in the settings search. The toggle carries an elevated-risk badge. In plain words: with developer mode on, ChatGPT can use every tool of every connector added this way, including tools that change or delete data, and a connector could try to trick it. That is why the user should add only servers they trust. For Oddlynew, allow its tools when ChatGPT asks, for the whole conversation where it offers that, so the agent can work without a confirmation at every step. Close settings.
1. In the left sidebar, open **Plugins** and click the add (**+**) button. On Business, Enterprise and Education, create it from **Settings**, then **Apps**, then **Create** instead.
1. Name: `Oddlynew`. Keep **Server URL** selected as the connection kind and paste the MCP server URL.
1. Accept "I understand and want to continue" and create the connector.
1. Authenticate: either the sign-in screen opens directly, or open **Plugins**, then **Installed**, find Oddlynew, and click **Connect** or **Authenticate**. Complete the Oddlynew sign-in.

## ChatGPT desktop app (Codex view)

These steps are for Codex, which is its own view in the ChatGPT desktop app, separate from Chat and Work: select **Codex** from the top-left menu first. OpenAI does not document these servers for Chat or Work. The list is shared with Codex CLI and the Codex IDE extension, so if the user already added Oddlynew to Codex CLI, it is already here; skip to step 4.

1. In the Codex view, open **Settings**, then **MCP servers**.
1. Click **Add server**.
1. Name: `Oddlynew`. Choose **Streamable HTTP**, not STDIO, and paste the MCP server URL. Save, then click **Restart**.
1. Oddlynew shows that it needs sign-in: click **Authenticate** and complete the Oddlynew sign-in. Typing `/mcp` in the composer lists the connected servers.

## Cursor

From Cursor's MCP documentation (cursor.com/docs/context/mcp and its install links page, read 13 October 2026). Cursor supports OAuth for remote servers.

1. Open this install link; Cursor opens and asks whether to install the Oddlynew server. Confirm it.

```
cursor://anysphere.cursor-deeplink/mcp/install?name=oddlynew&config=eyJ1cmwiOiJodHRwczovL21jcC5vZGRseW5ldy5jb20vbWNwIn0%3D
```

If the link does not open Cursor, add the server by hand to `~/.cursor/mcp.json` (available in every project), merging it into any servers already there:

```json
{
  "mcpServers": {
    "oddlynew": {
      "url": "https://mcp.oddlynew.com/mcp"
    }
  }
}
```

2. When Cursor asks, complete the Oddlynew sign-in.
1. MCP servers are turned on and off under **Customize** in the sidebar: check that Oddlynew is on. If it does not connect, open the Output panel (Cmd+Shift+U) and select "MCP Logs".

## Claude Code (terminal)

```
claude mcp add --transport http --scope user oddlynew https://mcp.oddlynew.com/mcp
claude "/mcp"
```

In the /mcp picker, select **Oddlynew** and press **Authenticate**.

## Codex (terminal)

Use Codex CLI 0.147.0 or later. The final command opts in to MCP 2026-07-28.

```
codex mcp add oddlynew --url https://mcp.oddlynew.com/mcp
codex mcp login oddlynew
codex --enable mcp_2026_07_28
```

## Other clients

Use the client's remote-MCP or custom-connector flow: add a remote MCP server with the URL above and sign in when asked. Plan eligibility, admin approval, and per-conversation enablement belong to the client. A client with no remote MCP support cannot connect.

## After the connection works

Two optional settings make every client work much better. Once the connection works, offer them to the user; whether to change them is the user's choice:

1. **Allow the Oddlynew tools always.** Guide and run can be set to always allow in the client's own tool or connector settings ({% docref blockKey="-o4QPNBnsR4" documentId="019fd60a-2a09-70a8-8aff-cf7c4464719c" %}Setting up your client: let your agent work without asking per call{% /docref %}). If the user is asked to approve each Oddlynew call, you can tell them that always allow is the recommended setting and show them where to change it.
1. **Add one instruction.** If the user wants every chat to use Oddlynew without being told, they put this line into the client's custom instructions, or a project's instructions, with the organization's id: `Use Oddlynew as my knowledge base. Oddlynew organization: <organization id>`. The id comes from `organizations.listMine` once the connection works.

Connecting is the whole setup: no skill or plugin needs installing on top.

Working conventions for connected agents are at `/agent-onboarding.md` on this same origin, for when the user's task needs them. If the user wants to go on, setting up their Oddlynew organization is the usual next step.