Few Servers

Home›MCP servers›Developer tools

Pulse MCP server

Remotenpm

PU · placeholder image
Placeholder. No logo or screenshot has been supplied for this listing yet.

Do you maintain this server? Claim this listing to add a logo or screenshot and to correct or extend it. Free, and a person checks every claim.

Claim this listingSuggest a correctionRatings and reviews

What it does

Ask about revenue, MRR, ad spend, LTV and CAC; install the Pulse SDK. Read-only.

Description as published by the publisher in the official MCP Registry, read 10 Oct 2026. Not written or verified by Few Servers.

Facts

Registry namestudio.pulsecircle/pulse
Publisherpulsecircle.studio Namespace verified by the registry through the publisher's domain.
CategoryDeveloper tools sorted by our keyword rules
Transportremote (streamable-http), local package (npm)
Version0.1.2
This version published2 Sep 2026
Last seen10 Oct 2026, in our crawl of the official MCP Registry
Tested by Few ServersNo

Install

  • Remote endpoint (streamable-http), as published: https://mcp.pulse.pulsecircle.studio/mcp
  • npm package, as published: @pulse-circle/mcp · version 0.1.2 · transport stdio
    npx -y @pulse-circle/mcp
    Standard run command for npm packages. The registry publishes the package name, not a command; check the repository for required arguments.

Install details read from the registry record on 12 Oct 2026. We have not run this server.

Keys and settings

The registry record declares a secret value (a key or token) that is not marked required. Declared by the publisher:

  • Authorization (header, secret, not marked required): Bearer <your Pulse API key> — from Settings in the Pulse web app. Clients that speak OAuth 2.1 can omit this and authorize instead.

RepositoryWebsiteRegistry record (JSON)npm package

Being listed is not a safety check. Read the repository and check what a server asks for before you connect it. How the directory works.

Ratings and reviews

No reviews yet.