Claude
- Open Add custom connector ↗
- Name it OrgPulse and paste the URL
- Click Add, then sign in to your account
https://orgpulse.cloudcounsel.co.nz/mcp
CloudCounsel Limited·IT & security·Live in ![]()
Salesforce admin watchdog
OrgPulse monitors a Salesforce org for the things that expire or run out and break logins and integrations, and answers questions about them in your AI. It saves Salesforce admins the routine work of checking an org by hand: daily checks, alerts before something breaks, and plain answers about who can see what. Its tools only read from Salesforce. They never create, change or delete anything in your org.
What it does
Expiring items. Lists what is about to expire and could break a login or an integration: certificates (including SAML and credential certificates), user passwords, time-limited permission set assignments, licences, trial expiry, scheduled jobs, refresh tokens (estimated from the connected app's policy) and retiring API versions your org still uses. If OrgPulse cannot read one of these because the integration user lacks a permission, it says so and names the permission, instead of reporting an empty list.
Limits and storage. Reports API limits, data and file storage, licence counts and async queue depth, so you can see how close you are to a limit.
Access explanations. Pick a user and a field, an object or a record (by its Salesforce ID), and OrgPulse shows the full access path, including which profile, permission set, group or sharing rule grants each piece. When access is denied it names the one change that would grant it. You can also compare two users on the same field.
Alerts. A daily check of each org can send email or Slack alerts when an item nears a threshold you set and again when it clears, without repeats. Watches are configured in OrgPulse, never in Salesforce.
History. OrgPulse keeps the latest check, a daily summary and every change (new, moved, resolved or expired items and limit changes), so it can say what is new since the last check.
Coverage depends on the integration user's licence. Anything OrgPulse cannot read is listed under "Not checked".
How it connects
An org admin signs in to OrgPulse and proves they own the org through Salesforce's standard OAuth login. They then choose who the checks run as: a dedicated read-only integration user with a limited permission set that OrgPulse provides (recommended), or, for a quick trial, the admin themselves. Your AI never receives Salesforce credentials; it holds only an OrgPulse access token.
What it does not detect
Tokens held by External Credentials, Auth Provider upstream secrets, security tokens, Salesforce-managed domain certificates, user licence contract dates, sandbox lifecycle, and the TLS certificates of remote endpoints. Refresh token expiry is an estimate.
Access and data
No tool writes to Salesforce. Outside your AI, during setup and only if the admin asks, OrgPulse makes three changes scoped to its own access (listed on the connect page) using the admin's sign-in for that one request. Configuring a watch writes only OrgPulse's own settings, and replaces that watch's earlier settings. OrgPulse stores org identifiers, the integration username, check results and change history, and alert settings. It does not store customer record data. See the privacy policy for what is collected, why, who receives it, how long it is kept and how to delete it.
Which permission sets expire in 10, 25 and 45 days for Alice, Bob and Carol Synthetic?
https://orgpulse.cloudcounsel.co.nz/mcphttps://orgpulse.cloudcounsel.co.nz/mcporgpulse.cloudcounsel.co.nzNot found; the server needs sign-in so there may be skills that our scan couldn't access
Salesforce admin watchdog. OrgPulse monitors a Salesforce org for the things that expire or run out and break logins and integrations, and answers questions about them in your AI. It saves Salesforce admins the routine work of checking an org by hand: daily checks, alerts before something breaks, and plain answers about who can see what. It is listed under IT & security.
Open its listing in the app's connector directory and connect. Sign in to your account in the browser window that opens. It uses OAuth, so the AI never sees your password. Step-by-step setup for each app is on this page.
The OrgPulse MCP server URL is https://orgpulse.cloudcounsel.co.nz/mcp. Paste it as a custom connector in Claude, ChatGPT, Gemini or Grok, or add it to Claude Code, Cursor or any MCP client. Setup steps.
Yes. OrgPulse is published or run by CloudCounsel Limited, so it is the official MCP server. See other official connectors.
It is listed in 1 store: ChatGPT. Apps where it is not listed can usually still add it as a custom connector.
It is ranked 13,315 of 15,293 in the ChatGPT directory. A rank is the store's own order, not a usage count. How we track ranks.
It has 9 tools: 8 read data and 1 can delete or overwrite data. See every tool and its inputs.
Yes. 0 tools can change data and 1 tool can delete or overwrite it. Most AI apps ask before they run these. The store marks these as destructive:
None that we found. Not found; the server needs sign-in so there may be skills that our scan couldn't access.
Here are examples from its store listing. Type one into your AI after you connect.
No. Its answers come back as text in the chat. Connectors with interactive UI.
The top-ranked connectors in IT & security include:
This page updates every day. To ask about OrgPulse from Claude, ChatGPT or a coding agent, connect the Agent Ready MCP server: it tracks ranks, tools and new listings across the AI plugin stores.