> ## Documentation Index
> Fetch the complete documentation index at: https://docs.datalayer.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Codex

> Connect Codex desktop to Datalayer through remote MCP and OAuth.

The original four profile operations passed in native Codex desktop on October 17, 2026. Desktop
and CLI share MCP configuration on the same host; CLI-specific acceptance is
separate. Preserve existing integrations, including any legacy Datalayer server.

**1. Open your Datalayer workspace**

Sign in and open [Connections](https://app.datalayer.so/#connect). Use this
same account for Codex authorization. If an existing Datalayer entry already
points to the server below, reuse it.

**2. Add the server in Codex desktop**

Open **Settings → MCP servers → Add server**. Name it **datalayer**,
select **Streamable HTTP**, and enter this URL:

```text Server URL theme={null}
https://mcp.datalayer.so/mcp
```

Save and restart the connection. Alternatively, use the CLI commands below
on the same host; do not add a second entry if desktop setup already created it.

**3. Authenticate**

Select **Authenticate**, complete Datalayer sign-in in the browser and review
the authorization request. Do not paste an API key into the conversation.

**4. Confirm the connection in a new conversation**

Use `/mcp` to confirm Datalayer is connected and exposes the
[fifteen tools](https://docs.datalayer.so/tools.md), including `find_companies`, `get_company_profile`,
`find_people`, `get_person_profile`, and `get_account_details`. Tool
discovery uses no credits. Ask Codex about your remaining credits to
confirm it calls `get_account_details`. A saved server entry alone does not prove
authentication succeeded.

## Codex plugin

For the Datalayer skill and current tool guidance, install the package from the
[existing Datalayer marketplace](https://gitlab.com/datalayer/plugins):

```bash theme={null}
codex plugin marketplace add https://gitlab.com/datalayer/plugins.git
codex plugin add datalayer-plugin@datalayer
```

If the marketplace is already configured, update it and install the current
package:

```bash theme={null}
codex plugin marketplace upgrade datalayer
codex plugin add datalayer-plugin@datalayer
```

Use version **2.1.1** or newer and start a fresh conversation. Authenticate the
plugin's `datalayer-2` connection using the client sign-in flow and check your
remaining credits with `get_account_details`. That check is free. Inspect
existing connections before adding another server. Version 2.0.5 and earlier
could refuse a request when the attached tool catalog differed from the skill;
the current package supports the fifteen-tool catalog and added capabilities.

The October 26 Codex CLI check verified the current catalog and authenticated
account access. It does not establish every paid operation or interactive view
in every client. See the [setup and troubleshooting guide](https://gitlab.com/datalayer/plugins/-/blob/main/docs/setup.md).

## CLI alternative

With Codex CLI installed on the same host, add the server once, then sign in:

```bash theme={null}
codex mcp add datalayer --url https://mcp.datalayer.so/mcp
codex mcp login datalayer
```

If the server already exists, sign in using its saved name, for example
`codex mcp login datalayer`. Older setups may use `datalayer-v2`; use that name
when signing in to an existing entry. You do not need to recreate a working
connection. If `datalayer` points to a different, legacy server, keep that
connection separate rather than overwriting its URL. Return to a new desktop
conversation afterward.

## Try a search

With an active allowance, copy this into Codex:

```text theme={null}
Use Datalayer to search for Stripe. Show up to three company matches and their websites. Wait for me to choose a match before opening a full profile.
```

On the published plan for new signups, a search with results costs 1 credit. An empty search costs nothing. A new profile costs 1 credit, and a verified work email costs 2.
Ask Codex to report `meta.credits_used`. Check shared usage and saved profiles
in the [dashboard](https://app.datalayer.so/#connect).

For failed authorization after disconnecting, use **Finish disconnecting** in
Datalayer Connections first. See [help](https://docs.datalayer.so/help.md) and
[OpenAI's MCP setup guide](https://learn.chatgpt.com/docs/extend/mcp?surface=app).

The hosted connector lists fifteen tools: `find_people`, `get_person_profile`, `find_work_email`, `validate_email`, `find_companies`, `get_company_profile`, `find_job_postings`, `get_tech_stack`, `find_sites_using_tech`, `list_technologies`, `get_list_filters`, `preview_list`, `build_list`, `get_list_results`, and `get_account_details`. [What you can do](https://docs.datalayer.so/tools.md) explains each one and what it costs. You can paste the [universal setup prompt](https://docs.datalayer.so/getting-started.md#copy-this-into-your-assistant) and let Codex walk through sign-in. The October 17 acceptance covered the original four profile operations. The October 26 CLI check also verified discovery of all fifteen tools and the free account lookup. Full paid-operation acceptance remains separate.

`find_job_postings` searches indexed postings across companies. A page with at least one posting costs 1 credit. An empty successful page and failures cost zero. The identical search repeats free within 24 hours. Each posting includes a shortened description, salary when present, function, employment type, close date and status, source domain, and first-seen and updated dates. Indexed postings are not confirmed hires. A technology stack is a separate lookup from a company profile. Request `dry_run` for a maximum estimate before a larger task, set `max_credits` to cap spending, and inspect section coverage and the credit receipt.

Explicitly requested employer-associated business-email candidates may be returned
as **UNVERIFIED** for zero email credits. Keep the email assessment,
verification status, checked dates and catch-all uncertainty separate; an email assessment of
`valid` with unknown catch-all status is not conclusive verification.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.