MCP connector

Agent Hub Connector

Give MCP clients a governed view of one Pulse workflow.

Pulse Agent Hub Connector publishes a workflow-scoped tool catalog over Model Context Protocol. Each tool inherits the source boundary, allowed task, owner, escalation path, and review rule already defined in the Pulse Agent Hub card; the client never widens access to the underlying systems.

Request connector access Read the docs

Capture
Draft
Review
Route

Where to start

Choose the first workflow

Use this page to see when Pulse fits, what it can organize, what your team still controls, and what to send next.

When this matters

An MCP client wants Pulse-governed workflow context, but raw system access widens the trust surface beyond what the workflow owner approved.

What Pulse can organize

Pulse Agent Hub Connector exposes a workflow-scoped MCP tool catalog that inherits the source boundary, review rule, and audit posture of the Pulse Agent Hub card.

What your team controls

Workflow owners approve the tool catalog, source boundary updates, and write-path review rules before any MCP client sees them.

What to send us

Bring the workflow you want to expose, the MCP client you plan to wire, and the workflow owner who can approve the catalog.

What Pulse starts with

What the connector exposes

Each MCP tool maps to a Pulse-governed workflow. Tools quote the source boundary, never the raw system, and any write action requires the same review rule employees see in the Agent Hub card.

Workflow brief tools

Source-boundary-aware fetch tools

Owner and escalation lookup tools

Review-gated draft tools

Audit log tools

How it works

From signal to reviewed next step

Catalog

Pulse publishes the tool catalog scoped to the workflow id the client is bound to.

Call

Client (Claude, Cursor, custom agent) invokes a tool through MCP; the connector enforces the workflow source boundary.

Review

Write or send paths require the configured review rule; the response includes the audit handle.

Capabilities

Why a connector, not a raw API

Agent directory

Each MCP tool maps to one Pulse-governed workflow with a named owner.

Explore

Source planning

Tools quote the source boundary instead of widening client access.

Explore

Governance rules

Workflow review rules apply to every tool call.

Explore

Integration surface

Standard Model Context Protocol — works with Claude Desktop, Cursor, and custom agents.

Explore

Change control

Catalog changes go through the workflow owner; clients see them via a versioned manifest.

Explore

Audit trail

Every tool call is logged for the workflow owner and tenant admin.

Explore

Agent Hub Connector

What to check before you choose

Connector question

What does an MCP connector actually do for your team?

Pulse Agent Hub Connector exposes Pulse-governed workflow context to Model Context Protocol clients (Claude, Cursor, agentic IDEs) without giving them broader access to your source systems or destination of record.

Scoped surface

Each MCP tool maps to one Pulse-curated workflow: read a brief, summarize handoffs, or fetch redacted examples.

Named source

Tools quote the source boundary configured for the workflow; clients see provenance, not a raw connection.

Human in the loop

Write paths require the same review rule employees see in the Agent Hub card; nothing leaks past the destination of record.

Trust posture

Connector trust is the same trust an employee sees in the card.

If a Pulse workflow already names the allowed task, source, owner, and escalation, the connector should not widen that surface for any client.

Tools must declare the source they read.
Tools must respect the workflow review rule before any outbound action.
Tools must not expose raw system credentials or full source access to the client.
Tools must log every call for the workflow owner.

Examples to review together

Pre-launch, scoped pilots only

Pulse Agent Hub Connector is in scoped pilot. We publish the protocol surface and example workflows; we do not publish customer logos, anecdotes, or unverified case studies.

Scoped pilot tenants only
Documented tool catalog
Reviewed example workflows only

What stays reviewed

Connector access is gated per workflow, per tenant. Workflow owners approve catalog changes, source-boundary updates, and any new tool surfaces before MCP clients see them.

Catalog changes

New tools require a workflow-owner review and a versioned manifest bump.

Source boundary updates

Source changes are explicit; clients see the new boundary on the next tool list.

Write actions

Write paths inherit the workflow review rule; no client bypass.

Token rotation

Workflow owners can revoke client tokens without disturbing other workflows.

Where to start

Find the right workflow

Pulse Business AIReturn to the Pulse Business AI family hub.

Business OperationsSee the Agent Hub card model the connector exposes.

GovernanceRead the governance posture the connector inherits.

IntegrationsMap source boundaries before any connector wiring.

Next steps

Choose the next action

Read the docsMCP endpoint, tool catalog, and token model.

Review security posturePer-workflow scoping, audit, and revocation.

Compare connector pricingPilot vs. production tier scoping.

Next step

Wire one workflow to MCP. Keep the governance the workflow already has.

Bring the workflow you want to expose, the MCP client you plan to wire, and the workflow owner who can approve the catalog. Pulse will help turn that example into a scoped workflow, review rules, and practical next step.

Read the docs