Connect an MCP client to Pulse

Connect an MCP client to Pulse

From Pulse 8.0.0 onwards, Pulse exposes a Model Context Protocol (MCP) endpoint so that AI assistants can query your Pulse and TM1 environment through a set of tools. This page shows how to connect an MCP client to that endpoint.

Minimum Pulse version: 8.0.0. For what the tools actually do, see Pulse MCP Tools

Before you start

You need three things:

  • A running Pulse 8.0.0 or later that the client machine can reach over the network.

  • A Pulse API key. Create one from your user profile as described in Create a Pulse API key

  • Node.js, if your client needs the mcp-remote bridge (Claude Desktop does).

The API key inherits the permissions of the user who created it, so create it with an account that has the level of access the assistant should have, and no more.

Find your MCP endpoint

The endpoint is the Pulse server address followed by /mcp. The MCP server page under Administration shows the connection options for your installation:

image-20260723-092148.png

Pulse uses these default ports for the application server:

Protocol

Default port

Example endpoint

Protocol

Default port

Example endpoint

HTTPS

8093

https://your-pulse-host:8093/mcp

HTTP

8099

http://your-pulse-host:8099/mcp

The API key travels in an Authorization header on every request. Over plain HTTP that header is sent in clear text, so use HTTPS for anything other than a local test on the Pulse server itself.

Claude Desktop

Claude Desktop connects through the mcp-remote bridge, which is fetched on demand by npx, so there is nothing to install beyond Node.js.

  1. Install Node.js if it is not already present.

  2. In Claude Desktop, go to Settings then Developer then Edit Config.

  3. Add the pulse entry below, replacing the endpoint and the API key with your own values.

  4. Restart Claude Desktop.

{ "mcpServers": { "pulse": { "command": "npx", "args": [ "-y", "mcp-remote", "https://your-pulse-host:8093/mcp", "--header", "Authorization:Bearer YOUR_API_KEY" ] } } }

The missing space in Authorization:Bearer is deliberate. Claude Desktop splits arguments on spaces, which would break the header into two arguments. Do not add a space after the colon.

If Pulse uses a self-signed certificate, the connection fails on certificate validation. As a temporary measure while you install a trusted certificate, add an env block:

{ "mcpServers": { "pulse": { "command": "npx", "args": [ "-y", "mcp-remote", "https://your-pulse-host:8093/mcp", "--header", "Authorization:Bearer YOUR_API_KEY" ], "env": { "NODE_TLS_REJECT_UNAUTHORIZED": "0" } } } }

NODE_TLS_REJECT_UNAUTHORIZED: "0" disables certificate checking for that process. Treat it as a workaround, not a configuration. See Pulse SSL and TLS Configuration

Claude Code

Claude Code speaks HTTP MCP natively, so no bridge is needed. Register the server from a terminal:

claude mcp add --transport http pulse https://your-pulse-host:8093/mcp --header "Authorization: Bearer YOUR_API_KEY"

Then confirm it is registered with claude mcp list.

Other MCP clients

Whatever the client, only two values change: the endpoint URL and the authorization header.

  • Endpoint: https://your-pulse-host:8093/mcp

  • Header: Authorization: Bearer YOUR_API_KEY

Clients that support remote MCP servers directly (with a url and custom headers) can use those two values as they are. Clients that only support local stdio servers need the mcp-remote bridge, as in the Claude Desktop example above. Check your client's own documentation for the exact configuration keys.

To use Pulse tools from inside the Arc Assistant, follow the Arc pages instead:

Verify the connection

A working connection shows all three of the following:

  1. The client lists pulse as a connected server.

  2. It discovers the Pulse tools. A standard Pulse 8 installation exposes 35 tools, listed in Pulse MCP Tools

  3. A tool call returns data. Ask the assistant to run get_version, which is read-only and touches nothing. It returns the Pulse build, for example Pulse Version is: 8.0.20260826.

If the server connects but no tools appear, restart the client. Most clients discover tools only at startup.

Working with large responses

Some Pulse tools return very large payloads that can exceed an assistant's context window. A few habits keep sessions responsive:

  • Always scope calls by environment, service and date range rather than asking for everything.

  • get_server_state and get_performance_instance return every environment or the full log detail for the period. Narrow the date range before widening the scope.

  • search_process_history returns individual executions and is capped, so it is not a reliable source for totals. Use get_process_history, which returns aggregated counts per process or chore and is not capped.

Troubleshooting

Symptom

Likely cause

What to check

Symptom

Likely cause

What to check

Server never connects

Endpoint unreachable

Open the endpoint URL in a browser from the client machine. Check DNS, firewall, VPN and proxy.

Certificate or TLS error

Self-signed or untrusted certificate

Install a trusted certificate on Pulse, or use the env block above as a temporary workaround.

401 or authentication failure

API key wrong, revoked, or malformed header

Re-copy the key. Confirm there is no space after Authorization: in the Claude Desktop form and no stray whitespace in the key.

Connects but no tools listed

Discovery runs at startup only

Fully restart the client, then check the client's MCP log.

Fewer tools than expected

Version mismatch

Run get_version and confirm the server is 8.0.0 or later.

Pulse web UI works but MCP does not

Different surfaces

Treat web access and MCP access as separate checks. The web app being up says nothing about the key or the client config.

Security

  • Use HTTPS. The API key is sent on every request.

  • Create a dedicated key per client and per environment. Do not reuse one key across dev, test and production.

  • Store the key in a secret manager or an environment variable where the client supports it. Never commit it to source control, and never paste it into a screenshot, a ticket or a documentation page.

  • Rotate keys periodically, and rotate immediately if a key is exposed.

  • By default, generated API keys cannot be deleted. If your organisation needs users or administrators to be able to delete them, enable AllowApiKeyDeletion in the Pulse configuration.

  • Review the Pulse logs for repeated authentication failures or unexpected access patterns.