# Codex

Step-by-step guide to connect Screpy MCP to Codex with a user-level Streamable HTTP server.

Use this guide to connect Screpy to Codex CLI, the Codex desktop app, or the Codex IDE extension. Codex can share one user-level MCP configuration across these surfaces.

## Connect Screpy MCP to Codex

### Open your Codex configuration file

Open `~/.codex/config.toml`. On Windows, open `%USERPROFILE%\.codex\config.toml`.

### Add the Screpy MCP server

Add this block to the file, then save it:

```
[mcp_servers.screpy]
url = "https://mcp.screpy.com"
```

### Sign in to Screpy

Run this command in a local terminal:

```
codex mcp login screpy
```

Your browser opens the Screpy sign-in page. Sign in and approve access, then return to Codex.

### Confirm Codex can see the server

Run:

```
codex mcp list
```

The `screpy` server should be connected. In the Codex app or IDE extension, open **MCP servers** and authenticate if Codex marks Screpy as requiring OAuth.

### Test it in a new task

Ask:

> Use Screpy to list my projects and summarize the latest completed crawl for each one.

## If Codex login fails

The first OAuth connection needs a browser and a local callback path. If you are in SSH, a container, or another headless environment, complete the connection from a local Codex session first. Then review [Troubleshooting](/content/docs/mcp/troubleshooting/index.html).