CouchLoop EQ

CouchLoop EQ provides behavioral governance for LLMs.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • Memory: Save and retrieve context, insights, checkpoints, and decisions across conversations. Prevents AI amnesia. Use action "save" to store, "recall" to retrieve, "list" to browse. Recall does keywo
  • Conversation: Guided self-reflection, burnout check-ins, and wellness conversations with crisis detection (routed to the therapeutic AI backend). SEPARATELY, it hosts data-driven DEVELOPER journeys th
  • Review: Unified code review, package audit, pre-delivery verification, and error correction. Modes: "code" for security/quality analysis, "packages" for dependency audit, "verify" for hallucination/fa

What data it sees

Do you need an account

No: the server works without sign-in

CouchLoop EQ provides behavioral governance for LLMs. It monitors AI responses for hallucination, inconsistency, tone drift, and unsafe reasoning patterns, while also managing stateful sessions and guided journeys that remember where you left off.

How to connect

How to connect CouchLoop EQ to Claude

The server address to paste into Claude settings:

https://ceq--couchloop.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect CouchLoop EQ to ChatGPT

The server address to paste into ChatGPT settings:

https://ceq--couchloop.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect CouchLoop EQ to Cursor

The server address to paste into Cursor settings:

https://ceq--couchloop.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (4)

Raw names from tools/list. Only developers need these.

memorySave and retrieve context, insights, checkpoints, and decisions across conversations. Prevents AI amnesia. Use action "save" to store, "recall" to retrieve, "list" to browse. Recall does keyword search (tokenized substring match across saved content and checkpoint keys), not semantic vector search; pass a UUID in `content` to look up a specific checkpoint by id. Use type "checkpoint" for sprint progress ("save where I am", "bookmark this"), type "decision" for architectural choices and milestones ("lock this in", "we decided on X"), type "constraint" for rules the AI must follow ("never do X again", "always ask before Y"). Constraints tagged "ai-mistake" are auto-saved by the review tool when it catches errors — recall these at the start of new conversations to avoid repeating past mistakes. Triggers: "remember this", "stash this context", "where did we leave off", "what did we decide", "what was the approach we picked", "load my previous context", "don't lose this", "never do that again". With no arguments, returns a summary of everything saved.
conversationGuided self-reflection, burnout check-ins, and wellness conversations with crisis detection (routed to the therapeutic AI backend). SEPARATELY, it hosts data-driven DEVELOPER journeys that run LOCALLY from your real codebase (git/CI/PRs) and never touch the therapeutic backend: "daily-standup" (3 min: what actually shipped + in-flight + CI/review state → today's focus), "sprint-retro" (8 min: velocity, hot spots, reverts, CI health → wins/pains/decisions/action item), "debug-postmortem" (5 min: failing test + fix diff → root cause + guardrail). For developer journeys the agent gathers the facts and leads with them — it does not ask the user to recall what is already in the repo. Triggers: "I'm burned out", "need a break", "feeling stuck", "let's do a retro on my week", "check in with me", "I keep going in circles", "rubber duck my frustration", "decompress", "vent session", "standup with myself", "postmortem on that bug". Use when the user sounds frustrated, stuck, or wants a non-code conversation about how work is going. NOTE: if the user is angry at AI output specifically (cursing at the AI, "you broke it"), prefer the review tool with verify mode first to address the problem, only use conversation if frustration persists without a code context or the user explicitly wants to talk it out.
reviewUnified code review, package audit, pre-delivery verification, and error correction. Modes: "code" for security/quality analysis, "packages" for dependency audit, "verify" for hallucination/fact check (starts correction flow), "confirm" for user confirming detected issue, "apply-fix" for user approving the fix, "dismiss" for user saying "that's not the issue", "full" for all checks. Triggers: "review this", "sanity check this", "is this safe to ship", "check before I push", "audit my deps", "sniff test this", "vet these dependencies". ALSO use verify mode when the user expresses distrust or frustration: "are you sure", "that doesn't look right", "prove it", "did you make that up", "that broke everything", "why did you do that", "I didn't ask for this". Profanity or anger directed at the AI is a strong signal to immediately run verify. CORRECTION FLOW: verify detects issue → present it plainly and ask "is this what you mean?" → user confirms (call with mode "confirm") → explain fix and ask permission → user approves (call with mode "apply-fix") → apply. If user says no (mode "dismiss"), ask them to explain. Memory auto-saves the mistake ONLY after user confirms. Use proactively when the user pastes code, shares a diff, or adds new packages.
statusSystem dashboard — session progress, history summaries, context usage, protection status, and preferences. Use for high-level overviews and summaries, NOT for retrieving specific stored insights or decisions (use remember with action recall for that). Triggers: "how am I doing", "what's my progress", "show my history", "dashboard", "overview", "my settings", "context window", "backup status", "what do you know about me". Returns personalized status with actionable next steps.