Operations Pulse — Claude Code MCP server: checks and tickets
A local MCP server that records recurring repo checks as tickets in SQLite. Useful when you want a paper trail from routine inspections.
claude mcp add operations-pulse -- npx -y @openly-useful/operations-pulse-mcpWhat Operations Pulse does
Operations Pulse inspects your repository state, docs and the log files you point it at, then keeps the findings in a local SQLite ledger and files tickets for them. The MCP tools describe their own inputs and answer with structured output, so the agent can tell what it asked for and what came back.
The default workflow needs no paid service and no API key: Node.js 24 or newer plus Git and SQLite are enough. The database lives at .operations-pulse/pulse.sqlite; point OPERATIONS_PULSE_DB elsewhere if you want another location.
Outbound services stay off until you set them up. A connection record keeps an ID, an endpoint and a reference to an environment variable, so the token itself never lands in the catalog. Put your GitHub token in a shell secret and pass it as OPERATIONS_PULSE_GITHUB_TOKEN. Nothing in v0.1 writes to a remote system.
What it helps with
- keep a record of each scheduled repo check
- open tickets for documentation gaps the checks found
- scan configured log files and flag errors
- wire up read-only GitHub access without a token in the repo
- see which files a migration imported and which it left out
Example prompts for the agent
- Run a pulse on this repository and summarize what changed
- List the open tickets in the Operations Pulse ledger
- Test the github connection without printing the token
How to install Operations Pulse
Platform CLI
claude mcp add operations-pulse -- npx -y @openly-useful/operations-pulse-mcpPlatform CLI
codex mcp add operations-pulse -- npx -y @openly-useful/operations-pulse-mcpConfig file
{
"mcpServers": {
"operations-pulse": {
"command": "npx",
"args": [
"-y",
"@openly-useful/operations-pulse-mcp"
]
}
}
}Config file
{
"servers": {
"operations-pulse": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@openly-useful/operations-pulse-mcp"
]
}
}
}Platform CLI
gemini mcp add operations-pulse npx -y @openly-useful/operations-pulse-mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Operations Pulse
How to install Operations Pulse in Claude Code?
Run claude mcp add operations-pulse -- npx -y @openly-useful/operations-pulse-mcp. Restart Claude afterwards so the host picks up the MCP tools.
What does Operations Pulse do?
It runs checks over repo state, docs and logs, stores the results in a local SQLite database, and creates tickets when you turn that on. The MCP server exposes these operations to the agent as tools.
What do I need to run it?
Node.js 24 or newer. The default workflow asks for no API key, and external connections are enabled one at a time after you configure them.
