Connect Codex to Pulsetic
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 Pulsetic
A preset of real Pulsetic operations. Each one becomes a tool the agent can call, and it can't touch anything outside the list.
Connect Pulsetic
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
Pulsetic
11 toolsRead one documented monitor page as a bare array; omit private targets and settings.
Read one numbered snapshot page and aggregate counts, with exact monitor ancestry.
Read bounded check codes/flags/timestamps, excluding request/response content and locations.
Read exact 1day/7days/30days/90days aggregate objects, excluding target data.
Read the documented numeric downtime-in-seconds response, not an object wrapper.
About Codex
Frequently asked questions
More ways to connect
Open your Codex agent in one click.
NoClick runs Codex for you with Pulsetic wired in as tools. Connect your account and run.