Connect Codex to Linq
Set up in minutes
Choose where it runs
On your computer through your own Codex, or hosted in the cloud. The rest of setup adapts to your choice:
Pick what it can do in Linq
A preset of real Linq operations. Each one becomes a tool the agent can call, and it can't touch anything outside the list.
Connect Linq
One sign-in. The agent acts through your account, scoped to the operations you picked.
Add your personal MCP link
The last step mints a private MCP URL for this agent and walks you through exactly this, with your real link filled in. The page flips to Connected the moment your Codex first calls in. Codex connects when a session starts — run codex, or restart a running one (in the Codex app, Restart).
Run this in your terminal. The Codex app shares its config, so it gets the server too
<your-link> is your personal server URL — setup mints it for you.
Tools Codex gets
Linq
20 toolsList one page of conversations; preserve the provider's next_cursor.
Create or reuse a chat and send its required initial text message. First messages cannot contain URLs.
Request a chat name change; confirm final outcome through Linq webhook events.
Queue a text message. Acceptance does not prove delivery; read the message status later.
Edit a text part within 15 minutes of sending, up to five times.
Delete the API record only. This does not unsend the message from recipients' chats.
Add or remove a standard reaction on a message part.
Read attachment metadata and its download URL; no file download is performed.
Block inbound delivery and outbound sending for this handle.
Resume inbound delivery and permit sending to this handle.
About Codex
Frequently asked questions
More ways to connect
Open your Codex agent in one click.
NoClick runs Codex for you with Linq wired in as tools. Connect your account and run.