> ## Documentation Index
> Fetch the complete documentation index at: https://docs.openpulse.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP: your AI assistant reads the workspace

> Openpulse is a Model Context Protocol server, so Claude, ChatGPT, Grok and the Claude Code CLI can read your workspace directly once connected.

Openpulse is a Model Context Protocol server, so **Claude, ChatGPT, Grok and the Claude Code CLI** can read your workspace directly once connected. **Connect AI** at the bottom of the sidebar gives you the server URL and per-client setup steps, including which vendor plans support custom connectors.

A good first prompt is *"List my Openpulse workspaces"* — an assistant that has not asked cannot guess which workspace you mean. See [Tools](/mcp/tools) for what it can do once it knows.

## Authentication

The MCP server uses OAuth 2.1, not a shared secret: Clerk is the authorization server, Openpulse is only a resource server that verifies the token and serves data. Connecting an assistant walks you through the standard OAuth consent screen — there is no API key to paste in.

This is deliberately different from the [API reference](/api-reference), which authenticates with a static bearer token. A workspace API key is built for a script you write once and run unattended; OAuth is built for a client acting on your behalf in real time, where a human is present to grant and later revoke consent.

## What it cannot do, on purpose

There is deliberately **no create, update or delete** for listeners over MCP. An agent that can create listeners can commit you to recurring spend on every schedule tick — a mistake this shape of interface makes uncorrectable at conversation speed. The one exception, `trigger_run`, spends money on a single run rather than creating a standing spend, and is restricted to admins for that reason.

An assistant connected over MCP also cannot see what a run costs Openpulse to produce — that is operational data, not workspace data, and the two are kept apart everywhere in the product, not just here.


## Related topics

- [What Openpulse does not do](/guides/what-it-doesnt-do.md)
- [What Openpulse does](/index.md)
- [Listeners: what you are watching for](/guides/listeners.md)