Skip to main content

​
The server URL

One URL for every client. There is no API key to paste: the server speaks OAuth 2.1, so connecting opens a consent screen and the client holds a token afterwards. See Authentication for why this differs from the API reference. Connect AI at the bottom of the app sidebar shows these same steps with the URL already filled in, which is the shorter route if you are signed in.

​
Setting up a client

Needs claude.ai on the web, or the Claude desktop app.
  1. Open Settings > Connectors.
  2. Choose Add custom connector.
  3. Name it openpulse and paste the server URL.
  4. Press Connect, then approve the Open Pulse consent screen.
  5. The tools appear under the connector in any new chat.
Menu paths and plan requirements are the details that go stale fastest, because vendors rename them. These were checked against vendor documentation current at August 2026. If a menu has moved since, the vendor’s own documentation is the authority — the server URL above does not change.

​
The tools

Start with list_workspaces: every other tool needs a workspace_id from it. Then list_listeners to see what is being watched, and search_signals or get_rollup to read what was found. get_rollup is usually the better answer for a sales question: “who is losing customers to RivalCo” is a get_rollup question, “show me the three worst reviews from last week” is a search_signals one.

​
Why trigger_run is admin-only

Every other tool reads. trigger_run is the one tool that spends real retrieval and model cost the moment it is called, and it is not idempotent: calling it twice queues two runs, not one. Restricting it to admins matches who can already trigger a run from the interface.

​
What is deliberately absent

There is no create, update or delete for listeners. An agent that can create listeners can commit a workspace to recurring spend on every schedule tick, and that mistake is not one a “are you sure?” prompt reliably catches in an agentic conversation. If you need to create or reconfigure a listener programmatically, the equivalent is POST /v1/listeners/analyse-website in the API reference, which requires a workspace API key rather than an OAuth-connected assistant.

MCP overview

What the server is, how OAuth works, and what it deliberately cannot do.

Scoring and quality

What get_quality_report is reporting on.

Runs and signals

What search_signals and trigger_run are reading and queuing.

API reference

The key-authenticated equivalent, including the endpoints MCP omits.