MCP Integration
How Pulse AI exposes a toolset agents can use to inspect board state, dispatch work, and return evidence through the Pulse AI workflow.
What is MCP?
The Model Context Protocol is a standard way for AI systems to call tools. In Pulse AI, the important product concept is the Pulse AI toolset: agents can use Pulse AI-provided tools to inspect project state, coordinate board movement, dispatch work, and return evidence through supported workflows.
Pulse AI is not documented here as a generic MCP server host. The user-facing point is that Pulse AI gives agents controlled operational access to Pulse AI surfaces when the workspace and permissions allow it.
How agents use Pulse AI tools
Agents use the Pulse AI toolset for operational work such as:
- Reading board and Workday state.
- Starting or queuing work.
- Updating review status.
- Finalizing knowledge artifacts.
- Checking operational health.
The exact tool list depends on the installed Pulse AI version and the workspace runtime. Use the app shell, command palette, and board surfaces for normal operation; agents use the toolset to carry out approved workflow actions with evidence.
Why it matters
Pulse AI tool access lets agents do more than write suggestions. It lets them act on the board, produce evidence, and return work to review with context intact.
The important boundary is review: tool access may move work forward, but human approval still controls what becomes done.
External tool boundaries
External tool integrations can still matter for a workflow, but they are separate from Pulse AI's own operational toolset. Keep permissions narrow. Only connect tools that match the work you want agents to perform, and avoid granting broad access to systems that contain secrets or customer data.
Next: Dispatch & Sprints, Security & Privacy, and Rules & Behavior.