MCP server

Pulse MCP lets compatible AI clients work with your Pulse workspace. Ask your client to find and triage issues, review project risk, summarize initiatives, update OKRs, or search workspace knowledge without switching tools.

Pulse hosts the server at:

https://mcp.trypulse.tech/mcp

It uses Streamable HTTP and OAuth. You sign in to Pulse in your browser, so there is no access token to copy into a configuration file.

Setup

General

There are two ways to connect:

• Pulse CLI (recommended for Claude Code, Cursor, and Codex): connects the hosted server and installs the Pulse companion pack. The pack gives supported clients Pulse-specific skills, commands, agents, and safer workflow guidance.
• MCP only: connects the hosted server directly. You get all Pulse MCP tools, but not the optional companion pack.

Set up with the Pulse CLI

The CLI requires Node.js 20 or newer. On macOS or Linux:

curl -fsSL https://mcp.trypulse.tech/install.sh | sh

On Windows:

npm install -g https://mcp.trypulse.tech/cli/trypulse-cli-latest.tgz
pulse install

The setup wizard opens automatically. Select the clients you want to configure. Run pulse install again whenever you want to add another client.

Connect the MCP server directly

In any client with native remote MCP support, add:

Leave authentication headers empty. Your client should discover Pulse OAuth and open a browser when sign-in is required.

Claude

Claude custom connectors work on the web, desktop, and mobile:

1. Open Customize → Connectors.
2. Select + → Add custom connector.
3. Enter Pulse as the name and https://mcp.trypulse.tech/mcp as the remote MCP server URL.
4. Add the connector, select Connect, and sign in to Pulse.
5. Enable Pulse from + → Connectors in the conversations where you need it.

On Team and Enterprise plans, an Owner or Primary Owner must first add Pulse under Organization settings → Connectors. Members can then connect their own Pulse accounts.

Learn more about Claude custom connectors.

Claude Code

Install the MCP server and Pulse companion pack:

pulse install --claude

Restart Claude Code, run /mcp, and authenticate pulse when prompted.

For an MCP-only setup:

claude mcp add --transport http pulse https://mcp.trypulse.tech/mcp --scope user

Run /mcp to sign in and confirm that pulse is connected. See the Claude Code MCP documentation for client-specific settings.

Codex

The same configuration is shared by the Codex CLI, IDE extension, and desktop app. Install the Pulse plugin, companion pack, and MCP server:

pulse install --codex
codex mcp login pulse

The second command opens browser sign-in. You do not need to edit config.toml or create a personal marketplace.

Verify the integration in a fresh, read-only Codex task:

pulse codex-test

For MCP only, add a Streamable HTTP server named pulse from MCP servers in Codex settings, use the hosted URL, restart Codex, and select Authenticate. See the Codex MCP documentation for more client-specific options.

Cursor

Install the MCP server and Pulse companion pack:

pulse install --cursor

Reload Cursor with Developer → Reload Window. Open MCP settings, find pulse, and select Sign in if the browser did not open automatically.

For MCP only, add this to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "pulse": {
      "type": "http",
      "url": "https://mcp.trypulse.tech/mcp"
    }
  }
}

Reload Cursor and finish signing in from MCP settings. See the Cursor MCP documentation for other configuration scopes.

Other clients

Use the values in General for any client with native Streamable HTTP support.

If a client only accepts a local stdio command, use mcp-remote as a compatibility bridge:

{
  "mcpServers": {
    "pulse": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.trypulse.tech/mcp"]
    }
  }
}

This fallback requires Node.js 20 or newer. Prefer a native Streamable HTTP connection when the client supports one.

Common use cases

Describe the outcome you want; you do not need to know Pulse tool names. These prompts are useful starting points—replace the bracketed text with a Pulse name or link.

Turn a brief into delivery work

Read this product brief and propose a Pulse project with milestones and actionable issues. Reuse existing teams, labels, and related work when they clearly match. Show the full structure and assumptions before creating it.

Triage a backlog

Review the open issues for the [Platform] team. Group them by urgency, flag blocked or unassigned work, and suggest the smallest useful set of changes. Show me the proposed updates before changing anything.

Review project risk

Review the [Mobile onboarding] project. Check its target date, milestones, dependencies, open issues, and latest updates. Explain what is at risk and draft a concise status update. Do not publish it until I approve it.

Summarize strategy and progress

Give me an executive snapshot of the [Activation] initiative. Connect its objective and key results to the underlying projects, summarize progress and risk, and call out missing or stale information.

Find workspace knowledge

Search Pulse for decisions and documents related to [billing migration]. Read the most relevant sources and return a concise summary with source links and unresolved questions.

Update a metric

Record [42.7%] as this week's value for [Activation rate], then explain how it affects linked key results and objectives. Ask before recording the value.

FAQ