revloop
Recognizes HubSpot CRM CSV column names and imports HubSpot deal data into revloop's fact store, including normalized stages and other CRM fields used for account context and playbook triggers.
Recognizes Salesforce CRM CSV column names and imports Salesforce opportunity data into revloop's fact store, including normalized stages and other CRM fields used for account context and playbook triggers.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@revloop show me the latest context on Northwind Robotics"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
revloop
A shared context store for GTM teams and their AI agents, with outcome measurement built in.
Your CRM says the deal is in negotiation. The call from Tuesday says it is dead. Your agent just wrote a follow-up based on the CRM.
What a team knows about a deal sits in calls, emails, and the CRM, and it changes every week. An agent drafting from last month's context writes the wrong email. Separately, teams are adding agents that propose follow-ups without checking whether those follow-ups changed anything.
revloop handles both halves: one current view of each account where every fact carries its source, and a comparison that shows whether approved actions moved pipeline.
See it
Three sources disagree about Northwind Robotics. revloop keeps the newest and records the rest:
$ revloop context "Northwind Robotics" --history
next_step Send security questionnaire responses by Friday
emails/2026-09-15-northwind-robotics.eml:12 2026-09-15
superseded Legal review of the MSA
crm/salesforce-opportunities.csv:3 2026-09-10
superseded Loop in their CISO for the security review
calls/2026-09-08-northwind-robotics.txt:24 2026-09-08
stage negotiation crm/salesforce-opportunities.csv:3
competitor Vantage calls/2026-09-08-northwind-robotics.txt:18
pain Manual reconciliation eats two days a month
objection Procurement needs SOC 2 before signingEvery fact carries the file and line it came from, so an agent reading this can cite its source.
Later, once the deals have had time to move:
$ revloop report
Share of matched accounts that advanced stage within 30 days of the match
stalled-deal
approved action : 1/1 advanced (100%)
holdout : 0/1 advanced (0%)
uplift : not enough data (need >= 10 accounts per group)
Not a randomised test: a human chose which actions to approve, so selection bias is likely.Related MCP server: Volterra Knowledge Engine
Who this is for
You are wiring agents into a GTM stack and want them reading something better than a stale CRM field.
You have agents proposing follow-ups and no way to tell whether they help.
You want the context layer on your own machine, in SQLite, in files you can read.
Not for you if you want lead enrichment or an outbound sender. revloop does neither.
What it does
Extract | Call transcripts, |
Remember | SQLite. A newer |
Propose | YAML playbooks match conditions over the store and fill templates from real facts. Actions are only proposed. A person approves them, and revloop does not send anything. |
Measure | Import later CRM stage snapshots. Per playbook, accounts with an approved action are compared against accounts that matched the same trigger and got none. |
Serve | An MCP server exposes the store to Claude Code, Cursor, or any MCP client through five tools. |
Quickstart
Needs uv and Python 3.12. The --now flags pin the date so the fictional sample data gives the same answer whenever you run it.
uv sync
uv run revloop init
uv run revloop ingest examples/artifacts
uv run revloop context "Northwind Robotics" --history
uv run revloop run stalled-deal --now 2026-09-30
uv run revloop run competitor-mentioned --now 2026-09-30
uv run revloop actions
uv run revloop approve 1 # re-engagement email for Acme Freight
uv run revloop reject 2 # Harbor Health has no call or email facts, so the draft is empty
uv run revloop approve 3 # CRM note about the competitor at Northwind Robotics
uv run revloop outcomes import examples/outcomes.csv
uv run revloop report --now 2026-11-01Every command takes --db PATH (default ./revloop.db). Tests: uv run pytest.
Use it from an agent
claude mcp add revloop -- uv run --directory /path/to/revloop revloop --db /path/to/revloop/revloop.db mcpOr in a project .mcp.json:
{
"mcpServers": {
"revloop": {
"command": "uv",
"args": ["run", "--directory", "/path/to/revloop", "revloop", "--db", "/path/to/revloop/revloop.db", "mcp"]
}
}
}Tools: get_account_context, search_facts, propose_action, list_pending_actions, outcome_report.
propose_action records a proposal with status proposed. A person still runs revloop approve <id>, so an agent cannot approve its own work.
Architecture
flowchart LR
T[Call transcripts .txt] --> X
E[Emails .eml] --> X
C[CRM export .csv] --> M
X{Extractor<br/>rules or LLM} --> M[(SQLite store<br/>accounts, facts,<br/>actions, outcomes)]
M --> P[Playbooks YAML]
P -->|proposed actions| H[Human: approve / reject]
H --> M
S[Later CRM stage snapshots] --> M
M --> R[Outcome report<br/>approved vs holdout]
M <--> MCP[MCP server] <--> A[Agents: Claude Code, Cursor]Module | Role |
| Fact model, kinds, stage normalisation |
| Transcript, email, and CRM parsing; rule-based extractor |
| Optional Claude extractor with JSON schema output |
| SQLite schema, supersede and dedupe logic |
| YAML loading, trigger evaluation, template rendering |
| Snapshot import, approved vs holdout comparison |
| MCP tools |
|
|
894 lines of source, 36 tests, two dependencies. It runs locally and there is no service to sign up for.
Writing a playbook
name: stalled-deal
description: A late-stage deal has gone quiet.
trigger:
stage_in: [proposal, negotiation] # current stage is one of these
no_new_facts_days: 21 # no fact of any kind in the last 21 days
# has_kind: [competitor] # every listed kind has at least one current fact
actions:
- type: email_draft
template: |
Hi {stakeholder}, you mentioned "{pain}" and raised "{objection}".All trigger conditions must hold. Templates take {account} and any fact kind. Each placeholder gets the most recent current value, or (none recorded) if there is none, so a reviewer sees the gap rather than an invented detail. A playbook handles each account once.
Stages normalise to prospecting, qualification, discovery, demo, proposal, negotiation, closed_won, with common HubSpot and Salesforce names mapped on (contractsent and Negotiation/Review both become negotiation).
How the measurement works
When a playbook matches an account, revloop records the match time and the stage at that moment.
An account advanced if any imported snapshot within the window (default 30 days,
--window) shows a later stage.closed_lostnever counts.Approved group: matches where at least one action was approved. Holdout group: matches where nothing was approved, whether rejected or never reviewed.
Matches whose window is still open, or whose starting stage is unknown, are excluded and counted separately.
With at least 10 accounts per group it prints the uplift and a pooled two-proportion z-test. Below that it says there is not enough data.
Limits
This is not a controlled experiment. People choose what to approve, and they tend to approve actions for deals that already look healthy. Treat uplift as a signal to investigate, not proof. A proper test randomly holds out some matches before review.
The rule extractor is keyword matching. It is predictable and testable, but it misses paraphrases and produces false positives: any capitalised name after "evaluating" is read as a competitor. The LLM extractor reads text better and is not deterministic.
A playbook handles each account once, so an account that stalls a second time is not proposed again.
No enrichment and no sending. revloop does not find leads, enrich records, or deliver messages. Pair it with whatever you use to start conversations.
Timestamps are taken on trust. If your CRM dates are wrong, the report is wrong.
License
MIT. See LICENSE.
Available Tools
5 toolsget_account_contextB
Current facts (stage, amount, pains, objections, competitors, ...) for one account, with sources.
Inputs: account (required).
list_pending_actionsB
Actions waiting for human approval.
Inputs: no named parameters. Returns: result
outcome_reportC
Per playbook: share of accounts that advanced stage with an approved action vs a holdout.
Inputs: window_days. Returns: result
propose_actionB
Propose an action (e.g. kind 'email_draft', 'crm_note', 'task'). Nothing is sent; a human approves.
Inputs: body (required), kind (required), account (required).
search_factsA
Search current facts by text across all accounts. Optional kind filter, e.g. 'competitor'.
Inputs: query (required), kind. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
list_pending_actions, propose_action, and outcome_report are clearly separated by purpose. get_account_context and search_facts both retrieve facts, but one is account-scoped and the other is cross-account text search, so the overlap is minor and descriptions help.
All names use snake_case and most follow a verb_noun pattern (list_pending_actions, get_account_context, search_facts, propose_action). outcome_report breaks the pattern as a noun phrase, but the overall convention is still readable and mostly consistent.
Five tools is well-scoped for a focused approval-loop server. Each tool covers a distinct part of the workflow: context lookup, fact search, action proposal, pending-action listing, and outcome reporting.
The set covers context retrieval, fact search, proposal, pending listing, and outcome reporting, but lacks approve/reject or action-detail operations. This leaves a notable gap in the approval lifecycle, even if human approval happens outside the MCP surface.
Maintenance
Related MCP Connectors
Customer-context and ops layer for AI agents
The context layer for your company's AI: your team's decisions, meetings and plans, with sources.
A shared, governed brain for AI agents: versioned context with approvals, local or hosted.
The HubSpot MCP Server acts as a bridge that enables AI assistants and Large Language Models to securely interact with HubSpot CRM data through natural conversation, without requiring users to understand complex API structures. It provides read-only access to standard CRM objects (contacts, companies, deals, tickets, products, invoices, and more) and their associations, secured via OAuth 2.0, allowing AI agents to perform tasks like summarizing deals, fetching company updates, and looking up record changes.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides database interaction capabilities through SQLite, enabling users to run SQL queries, analyze business data, and automatically generate business insight memos.19MIT
- AlicenseNot gradedqualityDmaintenanceA read-only Model Context Protocol server that exposes a semantic knowledge base to AI agents via 27 tools. It enables querying of documents and data integrated from sources like Notion, SharePoint, HubSpot, and Slack.MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server providing tools for DB queries, API calls, file I/O, and text transformations, enabling AI agents like Claude to perform real-world actions.10MIT
- FlicenseBqualityDmaintenanceA Model Context Protocol server that provides database interaction and business intelligence capabilities through SQLite, enabling SQL queries, data analysis, and automatic generation of business insight memos.6-