Operations Pulse MCP server

Operations Pulse

A local-first loop orchestrator for useful, explainable operations.

Operations Pulse turns recurring checks into evidence, evidence into durable tickets, and tickets into a reviewable operating memory. It runs without a paid service by default: Node.js, SQLite, Git, local files, and local logs are enough to get a useful pulse.

It is an Openly Useful project: useful things, openly made.

Use the live, credential-safe setup guide at operations-pulse-five.vercel.app.

What launches in v0.1

log files.

• A SQLite ticket and pulse ledger.
• Read-only local checks for repository state, documentation, and configured

integrations.

• An MCP server with self-describing tools and structured results.
• A portable operations-pulse skill for Codex and compatible agents.
• Optional role definitions for operations, signal review, triage, and

subscription, host OAuth, self-hosted, and bring-your-own-credential paths.

• A connection catalog and guided setup that distinguish free/local,

• A complete migration ledger: imported, rewritten, referenced, or excluded.

Free-first quick start

Requirements: Node.js 24 or newer. No API key is required for the default workflow.

npm install
npm run build
node packages/core/dist/cli.js init
node packages/core/dist/cli.js pulse run --root .
node packages/core/dist/cli.js tickets list

Configure an optional read-only adapter without placing a credential in the repository, SQLite database, MCP argument, or chat transcript:

export OPERATIONS_PULSE_GITHUB_TOKEN='stored by your shell or secret manager'
node packages/core/dist/cli.js connections configure \
  --id github --mode env-token \
  --credential-env OPERATIONS_PULSE_GITHUB_TOKEN
node packages/core/dist/cli.js connections test --id github
node packages/core/dist/cli.js pulse run --root . --connections github

On a local machine already authenticated with the GitHub CLI, the zero-copy alternative uses that session only for the read-only check; its token is never stored or printed:

gh auth login
node packages/core/dist/cli.js connections configure --id github --mode github-cli
node packages/core/dist/cli.js connections test --id github

The browser-based picker at apps/site generates these safe setup steps. It never collects credentials. Host OAuth remains in the host's own consent UI.

Run the MCP server over stdio:

npm run mcp

The database defaults to .operations-pulse/pulse.sqlite. Override it with OPERATIONSPULSEDB.

Safety model

Operations Pulse is read-only unless a tool or command clearly says it writes. Pulse runs do not create tickets unless --create-tickets (or the equivalent MCP argument) is explicitly enabled. Connections are disabled until configured, credentials are never stored in the catalog, and externally visible or paid actions require a separate human approval boundary.

Connection records retain only an ID, non-secret settings, an endpoint, and an environment-variable reference. connections disconnect removes that reference from the local ledger. The initial adapters are read-only: IMAP unread-count metadata, GitHub identity, Linear viewer identity, Sentry project access, and PostHog project access. No remote mutation adapter ships in v0.1.

Optional heartbeat

Run a bounded foreground heartbeat anywhere Node can run:

node packages/core/dist/cli.js heartbeat serve --interval-minutes 30 --root .

On macOS, inspect then explicitly install a user-level LaunchAgent:

node packages/core/dist/cli.js schedule plan --interval-minutes 30 --root .
node packages/core/dist/cli.js schedule install --confirm-install --interval-minutes 30 --root .

The scheduler is never installed by an MCP tool, a model response, or a page load. Removal requires schedule uninstall --confirm-uninstall.

Repository map

Shortened. The full README is on GitHub.