Use Pulsewise
from your
AI assistant.

Ask about leave. Prepare for a 1:1. Update a goal. Pulsewise MCP connects your assistant to the work you already do.

Connect your assistantExplore the possibilities

Works with

  • Claude
  • ChatGPT
  • Codex
  • Cursor

Also connects with other compatible MCP clients.

Your AI assistantPulsewise connected
You

Who's off tomorrow?

Your assistant

Ravi is on leave tomorrow, 16 October.

R
Ravi Shah16 October · Full day
Approved
See how an approval works
You

Approve Maya's leave request for the 16th.

Your assistant

Confirm approval for Maya Patel's casual leave on 16 October, full day?

Waiting for your confirmation

Your Pulsewise permissions.

Read only or read and act.

Disconnect whenever you choose.

Start with something
on your mind.

Use your own words. Your assistant can read information and carry out supported tasks within your Pulsewise access.

Find your assistant’s setup
For your workdayLeave, goals and the things you need to do.
  • “What's my leave balance?”
  • “Book Friday off as casual leave.”
  • “How are my goals going?”
  • “What review work do I owe?”
For your teamPrepare for conversations and follow through.
  • “Prepare me for my 1:1 with Ravi.”
  • “Add 'promotion timeline' to our 1:1 agenda.”
  • “Approve Maya's leave request for the 16th.”
  • “Give kudos to the design team for the launch.”

Approvals are available to approvers. The assistant asks for confirmation first.

For HR and adminsFind people and understand aggregate engagement.
  • “Find people in the Design department.”
  • “Invite [email protected] to the workspace.”
  • “How is company engagement?”
  • “What's my team's pulse score?”

Company engagement is available to admins. Pulse scores remain aggregate.

You choose the access.
You keep control.

Your assistant acts as you. Connecting it does not give it access beyond your Pulsewise permissions.

Read onlyAsk questions and get context.
Read and actAlso carry out supported tasks.

Choose your access level when you connect.

Confirm the decisions

Before approving or rejecting leave and attendance requests, or checking you in, the assistant asks first and repeats who, what and when.

Your admin has the final say

Admins can review connected apps, revoke a connection or switch AI connections off for the account. Access stops immediately.

Anonymous pulse stays anonymous

The assistant gets aggregate scores. Small groups show no score, with the same privacy floor as the app.

Read about AI access
Some things stay in Pulsewise

Answer pulse surveys and check-ins, submit reviews and give ratings in the app. Survey and pulse-action lifecycle controls, anonymity settings, health configuration and admin configuration also stay in Pulsewise. Your assistant can save a self-review draft, but you submit it yourself.

One connection.
Your choice of assistant.

Choose your assistant below. Sign in to Pulsewise and approve the access you want to give it.

Already in Pulsewise? Open Settings, MCP for setup and your connected apps.

Log in to Pulsewise

ClaudeWeb and desktop
  1. Open Settings, Connectors, then Add custom connector.
  2. Name it Pulsewise and paste the server URL.
  3. Click Add, then Connect. Sign in and approve in Pulsewise.
ChatGPTOAuth connection
  1. Open Settings, Apps and Connectors. Under Advanced settings, turn on Developer mode.
  2. Choose Create, name it Pulsewise, paste the server URL and pick OAuth.
  3. Choose Create, then Connect. Sign in and approve in Pulsewise.
CodexConnect from your terminal

First, add Pulsewise with the Codex CLI:

1. Add Pulsewise
codex mcp add pulsewise --url https://mcp.pulsewise.io/mcp

Then start the sign-in flow:

2. Sign in
codex mcp login pulsewise

Complete sign-in in your browser and approve the access you want to give Codex in Pulsewise.

CursorConnect from your editor

Add this to ~/.cursor/mcp.json, keeping any existing servers:

mcp.json
{
  "mcpServers": {
    "pulsewise": {
      "url": "https://mcp.pulsewise.io/mcp"
    }
  }
}

Open Cursor Settings, MCP, then Connect. Sign in and approve in Pulsewise.

Claude CodeConnect from your terminal

Run this command:

Terminal
claude mcp add --transport http pulsewise https://mcp.pulsewise.io/mcp

Run /mcp inside Claude Code, pick pulsewise and choose Authenticate.

Other MCP clientsOAuth or a personal API token

Use the same server URL. If your client supports OAuth, it will ask you to sign in to Pulsewise.

Otherwise, create a personal API token in Pulsewise Settings, API tokens, and configure your client to send it as Authorization: Bearer <token>.

A few things
worth knowing.

What is Pulsewise MCP?

MCP stands for Model Context Protocol, a standard for connecting AI assistants to apps and data. Pulsewise MCP lets your assistant read information and carry out supported tasks in your Pulsewise account, within your permissions.

Which AI assistants can I connect?

Connect Claude, ChatGPT, Codex, Claude Code and Cursor, or another compatible MCP client. Sign in with OAuth where supported. Clients without OAuth can use a personal API token. Your assistant may have its own plan or administrator requirements for connections.

Does MCP use Pulsewise AI credits?

The MCP connection makes no AI calls inside Pulsewise. The AI runs in your chosen assistant, whose usage limits and charges apply. Contact us to confirm current Pulsewise plan and pricing terms for your workspace.

Can an administrator turn AI connections off?

Yes. Account admins can see connected AI apps, revoke individual connections or turn AI app connections off for the whole account in Settings, AI connections. Revoking or switching off stops access immediately. You can also disconnect your own apps in Settings, MCP.

Can an assistant see individual pulse responses?

No. Through MCP, the assistant receives aggregate pulse scores. Small groups show no score, using the same privacy floor as the app. Anonymous pulse responses are not exposed.

Is my data used to train AI models?

Data handling and training policies depend on the AI assistant you connect and your agreement with that provider. Pulsewise answers the requests allowed by your connection. Review your assistant provider’s policies and your organization’s requirements before connecting.

What stays in the Pulsewise app?

Answer pulse surveys and check-ins, submit reviews and give ratings in Pulsewise. Survey and pulse-action lifecycle controls, anonymity settings, health configuration and admin configuration also stay in the app. An assistant can help save a self-review draft, but cannot submit it or give a rating.

Bring Pulsewise into
your next conversation.

Connect your assistant to the Pulsewise account you already use.

Connect your assistantNew to Pulsewise? Sign up