Verelyn for Codex

Codex documents a route for adding a remote server. Verelyn has not tested it, and Verelyn is not listed in a Codex catalog.

Bring the outside world into a coding session: ask Codex what changed on the tools and vendors you follow.

See the setup steps for Codex →See an example

Give this to your assistant

Read Verelyn's setup guide and tell me which route applies to this client: https://verelyn.com/llms.txt
MCP endpoint: https://verelyn.com/api/mcp
An assistant must not invent priorities, complete payment, or activate the service. The person gives explicit approval in the browser.

You approve the sign-in and permissions yourself, in the browser. An assistant never pays or activates Verelyn for you.

Context from outside the repository.

Codex shares its server settings across the CLI, the IDE extension and the ChatGPT desktop app. Add Verelyn once and each of them can ask it.

Before you pin a versionAsk what a vendor announced this week and read it with the dates before you touch a lockfile.
Sources, not summaries aloneEach update names its publishers, so a surprising claim can be traced in one step.
Only the topics you setAsk about what you follow; Verelyn says plainly when it has nothing new.

How OpenAI documents adding a remote server to Codex.

Add the serverRun the documented command with the server address:
```
codex mcp add verelyn --url https://verelyn.com/api/mcp
```
Sign inFor a server that supports OAuth, OpenAI documents a login command that opens a browser. Approve Verelyn there:
```
codex mcp login verelyn
```
Check itRun codex mcp list, or open /mcp in the terminal interface, to see the server Codex has configured.
AskAsk Codex what changed on a vendor you follow. OpenAI documents approval modes for tool calls, so Codex may ask before it uses a tool.