Skip to content

PricingSaaS joins Willingness to PayRead the announcement →

Back to the agent
SetupMCP

Connect Pulse to your AI tools

Pulse runs two Model Context Protocol servers. Add whichever one matches what you want your agent to do — or both. Each signs you in through the browser on first connect, so there is nothing to paste to get started.

Pulse
OAuth
https://fbzazuuqlrvbayzuprds.supabase.co/functions/v1/pulse-index-mcp

Your account: build and edit workspaces, add tracked companies, set a focal company, read what changed, and manage digest routines.

PricingSaaS Pulse
OAuth
https://mcp.pricingsaas.com

The research corpus: search every company Pulse tracks, pull pricing history, and read diffs and news. Calls draw down your PricingSaaS credits.

1

Prerequisites

An MCP-compatible client that speaks MCP over HTTP — Claude Code, Claude Desktop, Cursor, Codex, or Gemini CLI. You’ll need a Pulse account for the first server and a PricingSaaS account for the second. Signing in through the browser is all that is required; see below if you need a key instead.

2

Add a server (Claude Code)

One command per server, over HTTP transport:

claude mcp add --transport http pulse-index https://fbzazuuqlrvbayzuprds.supabase.co/functions/v1/pulse-index-mcp
claude mcp add --transport http pricingsaas https://mcp.pricingsaas.com
3

Other clients

Cursor, Codex, and Gemini CLI all read the same config shape. Add the server to your client’s MCP config file:

{
  "mcpServers": {
    "pulse-index": {
      "type": "http",
      "url": "https://fbzazuuqlrvbayzuprds.supabase.co/functions/v1/pulse-index-mcp"
    },
    "pricingsaas": {
      "type": "http",
      "url": "https://mcp.pricingsaas.com"
    }
  }
}

For Claude Desktop, go to Settings → Connectors → Add custom connector, paste the server URL, and set Authentication to OAuth.

4

Sign in and verify

On first connect a browser window opens. Sign in and approve access, and the client registers itself automatically. To confirm the connection is live, ask your agent to run whoamion Pulse server — it returns the account the connection is using. On the PricingSaaS server, get_status returns your remaining credits.

What Pulse server can do

Thirty-one tools: everything you can do in the app — workspaces, companies, focal company, digest routines — plus the market data behind it: company search and details, pricing history, weekly and daily diffs, highlights, news, the pricing knowledge library, and full-text search of pricing pages. A workspace is a named set of tracked companies, optionally centred on one focal company. Free-plan accounts can track up to 1,000 companies across their workspaces.

Workspaces
list_workspaces · get_workspace · create_workspace · rename_workspace · delete_workspace
Companies
find_companies · add_companies · remove_companies
Focal company
set_focal_company · clear_focal_company
Activity
get_workspace_activity
Digest routines
list_routines · create_routine · update_routine · delete_routine
Account
whoami

Try: “Make me a workspace called CRM competitors with HubSpot, Attio and Pipedrive, then tell me what changed in it this month.”

What the PricingSaaS server can do

The pricing-intelligence corpus across every company Pulse tracks. These calls consume credits on every call, with no deduplication — re-fetching the same company is charged again.

Companies
search_companies · search_companies_advanced · get_company_details · get_company_history
Changes
browse_diffs · fetch_diffs · get_diff_highlight
Research
search_text · search_pricing_knowledge · get_pricing_news
Account
get_status

Keys, limits and fair use

Browser sign-in is the way in and needs no key: your MCP client opens the browser once, you approve, and there is nothing to copy from Settings. Running somewhere a browser cannot open — a server, a cron job, a container? Email rob@pricingsaas.com and we will issue a bearer key for that deployment, which works with exactly the same tools.

Pulse Free includes the MCP server in full. There is nothing to buy and no per-seat charge. Two ceilings exist purely to stop a runaway script, and sit far above anything a person working through an assistant will reach: 120 tool calls a minute, and 40 pricing-change lookups every ten minutes. If you ever see one, it says plainly that it is an automation guard rather than a plan limit, and it clears on its own.

Prefer to try it here first?
The in-app agent runs against the same data with no setup.
Open the agent →