loopsense — bash
[ CONNECT WITH GITHUB ][ HOW IT WORKS ]

[loopsense@cloud ~]$ clients --supported

Works withClaude CodeCursorCodexVS Code CopilotAny MCP Client

[loopsense@cloud ~]$ demo --play

// Watch an AI agent use LoopSense to close a CI feedback loop in real time.

loopsense — demo

[loopsense@cloud ~]$ diagnose --agent-blindness

loopsense — bash
[loopsense@cloud ~]$ describe --problem

AI agents are great at writing code.
They are terrible at knowing what happens next.

> Push to GitHub     → did CI pass?        ← agent has no idea
> Run npm build      → did it compile?     ← agent has no idea
> Deploy to Railway  → is it healthy?      ← agent has no idea
> Run a migration    → did it succeed?     ← agent has no idea

So they wait. Or they guess. Or they ask you.
loopsense — bash
[loopsense@cloud ~]$ describe --solution

LoopSense is an MCP server that gives your
agent a real-time event feed.

It watches CI, processes, files, URLs, and
webhooks — and fires structured events the
moment something happens.

Your agent stops guessing. It knows.

[loopsense@cloud ~]$ explain --loop

How the loop closes

// LoopSense closes the feedback loop so your agent never has to block and wait.

01
Agent starts a task
// deploy, build, test, codegen — anything with a side effect
02
Calls a watch_* tool with an action_id
// one logical ID can group multiple watchers across CI, files, and URLs
03
LoopSense monitors in the background
// events fire as stdout streams, files change, deploys finish, or webhooks arrive
04
Events fire when something happens
// structured payloads delivered over MCP — no polling, no long-running threads
05
Agent calls check_consequences(action_id)
// all correlated events for that task, in one call
06
Agent reacts, fixes, continues
// retries a failed build, rolls back a deploy, reads generated output — the loop is closed
$ mcp call check_consequences
# After your deploy, build, and health-check all finish:
$ mcp call check_consequences \
    --action-id deploy-prod-2847

# Returns all correlated events across every watcher
{
  "action_id": "deploy-prod-2847",
  "events": [ci.success, process.exit_0, url.200_ok]
}

[loopsense@cloud ~]$ ls --watches

5 watchers. Every async side effect, covered.

// CI runs, processes, files, HTTP endpoints, webhooks — all reporting back to your agent.

mcp — watch_ciCI / Build
$ mcp call watch_ci --owner anthropics --repo claude-code
● watching CI · run #1247 · in progress

watch_ci

Subscribe to GitHub Actions, GitLab CI, CircleCI, and Bitbucket Pipelines. Fast-polls at 5s, backs off to 30s. Auto-closes on completion. Your agent gets the result the moment it lands.

GitHub Actions
GitLab
CircleCI
Bitbucket
mcp — watch_processAny Command
$ mcp call watch_process "npm run build"
● streaming · stdout: compiled 847 modules

watch_process

Spawn any command — npm build, pytest, cargo test. Stream stdout/stderr live as events. Get the exit code when it finishes.

mcp — watch_fileFiles & Dirs
$ mcp call watch_file ./dist/
● watching · 3 files changed

watch_file

Watch files or directories for changes. Detect when codegen writes output, migrations land, or builds finish writing to disk.

mcp — watch_urlHTTP Polling
$ mcp call watch_url https://api.myapp.com/health
● polling · 200 OK · last checked 30s ago

watch_url

Poll any HTTP endpoint on a schedule. Verify your deploy is healthy after going live. Alert on downtime or unexpected status codes.

mcp — watch_webhookWebhooks
$ mcp call watch_webhook --port 8090
● listening · event received: push

watch_webhook

Receive real-time GitHub push, PR, and deployment webhooks — or hook in Vercel, Stripe, and any service. HMAC signature verification included. No exposed ports needed.

GitHub⚡ Real-time
Vercel

[loopsense@cloud ~]$ ls --integrations

Connects to everything in your stack

// GitHub webhooks deliver push, PR, and deployment events in real-time — no polling needed.

// CI & Build
GitHub Actions
GitLab CI
CircleCI
Bitbucket
// Deployments
Vercel
Railway
Render
Fly.io
// Notifications
Slack
Discord
PagerDuty
// Webhooks
GitHub⚡ Real-time
Vercel

[loopsense@cloud ~]$ cat features.json

Works with any MCP client

--action-id

action_id grouping

Tag multiple watchers to one logical task, then query all consequences at once with check_consequences(action_id).

--client

Any MCP client

Works with Claude Code, Cursor, Codex, VS Code Copilot — any client that speaks the Model Context Protocol.

--tenant

Multi-tenant

Teams share one server with full data isolation per API key. No cross-tenant event leakage, ever.

--fallback

poll_events fallback

Agents that don't support push can call poll_events at any time to pull new events without missing anything.

--connect

One command to connect

claude mcp add loopsense-cloud --transport http --url https://mcp.loopsense.dev/mcp --header "Authorization: Bearer $LOOPSENSE_KEY"

[loopsense@cloud ~]$ cat pricing.md

Simple, usage-based pricing

// Start free, scale when you need to.

┌─── FREE ───
$0
/month
  • > 100 events/mo
  • > 5 active watches
  • > 1 user
  • > All 5 watch types
  • > MCP-native API
└────────────────
[ GET STARTED FREE ]
// MOST POPULAR
┌─── INDIE ───
$29
/month
  • > 50,000 events/mo
  • > 25 active watches
  • > 1 user
  • > All 5 watch types
  • > MCP-native API
└────────────────
[ UPGRADE TO INDIE ]
┌─── TEAM ───
$99
/month
  • > 500,000 events/mo
  • > 100 active watches
  • > Up to 10 users
  • > All 5 watch types
  • > MCP-native API
└────────────────
[ UPGRADE TO TEAM ]

[loopsense@cloud ~]$ quickstart --steps

Get started in 4 steps

01
Sign in with GitHub
No forms, no email verification. One click and you're in.
02
Grab your API key
Generate a key from the dashboard and store it in your environment.
03
Connect your MCP client
Run the one-liner to wire up Claude Code, Cursor, or any MCP client.
04
Start a watch
Tell your agent which CI runs, processes, files, URLs, or webhooks to monitor.
$ claude mcp add loopsense-cloud
# Connect Claude Code in one command
$ claude mcp add loopsense-cloud \
    --transport http \
    --url https://mcp.loopsense.dev/mcp \
    --header "Authorization: Bearer $LOOPSENSE_KEY"