One Visualping MCP server for ChatGPT, Codex and the Responses API. Install the Visualping app in ChatGPT, add the server to Codex, or call it from your own agent. Visualping keeps checking the page after the conversation ends.
Pick the surface you work in. All three talk to the same server and sign in with your Visualping account.
Open Apps in ChatGPT, search for Visualping, click Connect and sign in with your Visualping account. In a chat, pick Visualping from the plus menu to use it in that conversation.
On admin-managed workspaces such as ChatGPT Enterprise, an admin may need to allow apps and custom connectors first.
The Codex CLI, the IDE extension and the ChatGPT desktop app share one configuration, so you set it up once. Run these two commands, then log in to visualping.io and click Allow.
codex mcp add visualping --url https://visualping.io/mcp
codex mcp login visualping[mcp_servers.visualping]
url = "https://visualping.io/mcp"The same server as an entry in ~/.codex/config.toml, or in .codex/config.toml inside a trusted project. In the Codex TUI, /mcp lists the servers that are connected.
Pass the server as an mcp tool. The Visualping MCP needs an OAuth access token in the authorization field, not a REST API key. Keep approvals on so you can review what the model sends to the server.
curl https://api.openai.com/v1/responses \
-H "Authorization: Bearer $OPENAI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "gpt-6-astra",
"tools": [{
"type": "mcp",
"server_label": "visualping",
"server_url": "https://visualping.io/mcp",
"authorization": "<visualping-oauth-access-token>",
"require_approval": "always"
}],
"input": "Watch https://competitor.example/pricing daily and flag price changes."
}'Building a scheduled job with no user to sign in? The Visualping REST API with an API key is the simpler route.
Each request maps to a Visualping MCP tool, and the assistant only gets the permissions your Visualping role allows.
“Watch this pricing page every day and alert me only if a price drops below $500.”
Creates a monitor with a plain-English alert condition. Visualping AI reads each change against it and flags the ones that matter.
“What changed on my monitors this week?”
Reads the change timeline, with the Visualping AI summary and Important flag for each event, so the assistant can answer without opening a screenshot.
“Check it now and tell me what you see.”
Triggers an immediate check, waits for the capture, and reports what the page showed.
“Send alerts from the pricing monitors to this webhook instead of email.”
Changes where a monitor sends its alerts, from email and webhooks to Slack, Microsoft Teams, Discord, Telegram, SMS and n8n, within what your plan includes.
“Dismiss the cookie banner and open the Pricing tab before each check.”
Sets the page actions a monitor runs before every capture, for content that is not on the page as it first loads.
“Only check during business hours, Monday to Friday, and pause the staging monitors.”
Restricts checks to a daily window in your account's time zone, and pauses monitors while keeping their history.
ChatGPT and Codex can reason and write code, but they need a durable place to put a watch. Visualping is that place.
Keeps watching after the conversation ends
Visualping checks the page on its own schedule from its own servers. There is no polling loop to write and no cron job for the agent to maintain.
Every change comes with a Visualping AI summary
Each change event carries a summary and an Important flag, so the assistant can read what moved without opening screenshots. Describe what matters in plain English to tune the alerts.
Your sign-in, your permissions
OAuth sign-in with your Visualping account, with nothing to paste into a config file. The assistant can only do what your Visualping role allows, in the workspaces you belong to.
Works on every plan, including Free
There are no separate MCP limits. Checks and pages count against the plan you already have, so you can start with a free account.
The Visualping REST API works on every plan with an API key, which suits server-side agents and scheduled jobs that have no user to sign in. The developer guide walks through both routes, with Codex and Claude Code examples.
Create a free Visualping account, connect the server, and ask for your first monitor.
No. ChatGPT and Codex sign you in with your Visualping account in the browser. The Responses API takes an OAuth access token instead of an API key. API keys are only for the REST API.
Any plan, including Free. There are no separate MCP limits. Checks and pages count against your plan's normal quota. The Free plan checks hourly at most, and shorter intervals need a paid plan.
The Visualping app is published in the ChatGPT app directory. Whether your workspace can install apps and connect MCP servers depends on your ChatGPT plan and settings. On admin-managed workspaces such as ChatGPT Enterprise, an admin may need to enable it.
Yes. The Codex CLI, the IDE extension and the ChatGPT desktop app read the same config.toml, so one codex mcp add and one login cover all three.
Yes. The mcp tool type works with remote servers over Streamable HTTP. Set server_url to https://visualping.io/mcp and pass a Visualping OAuth access token in authorization. The server publishes standard OAuth discovery metadata and supports dynamic client registration, so your app can obtain the token with a normal authorization-code flow.
Labels, Google Sheets notifications, and user, billing and account settings are managed in the Visualping dashboard. Monitors themselves, including their schedule, page actions and alert destinations, can be created, read and changed by the assistant.
Yes. The Visualping MCP server also works in Claude Code and in Claude on the web and desktop. See the Claude Code integration page for the setup.