Skip to main content
REX builds a continuously updated understanding of every deal from your calls, your CRM, and room activity. Over MCP, that understanding becomes queryable: Claude can pull a deal’s signals, scores, and the specific evidence behind them, and write new signals back. Everything REX exposes here reads from the room’s Knowledge Graph. Nothing is a separate or simplified copy — a score you fetch over MCP is the score on the room’s Overview tab.
All REX data is read-only except signals. upsert_signals is the only tool that writes. Scores, insight cards, contacts, and findings are computed by REX and can’t be set from outside.

​
What you can read

Signals

The worklist for a deal — dated, actionable observations, each with an urgency level and recommended next steps.

Knowledge graph

One call for the whole picture: Deal Score, MEDDPICC, insight cards, and the quote-backed findings behind them.

Room contacts

Everyone on the room, including people added but never engaged.

​
Signals

A signal is one specific observation REX has made about a deal, with an urgency level, a justification, and one or more recommended actions. Signals are the most useful REX data to pull over MCP, because they’re already scoped to “things worth doing something about.”

​
Query and triage

Leaving the room out is deliberate: query_signals and aggregate_signals both work across every room you have access to when no roomId is given, which is what makes a morning pipeline sweep a single call.
Ask for counts before details. aggregate_signals returns just the urgency breakdown (for example 4 low, 2 medium, 1 high), so Claude can tell you where to look without pulling every signal body first.

​
Signal properties

​
Writing signals

upsert_signals lets an external agent or workflow add its own signals to a room’s feed, or update ones it created earlier. A signal you write appears in the room’s feed and in the org-wide REX’s signals view exactly like a REX-generated one.
Updating requires the signal id you got back when you created it. There’s no dedupe on title, so calling upsert_signals twice without an id creates two signals rather than replacing the first.

​
Knowledge graph

get_knowledge_graph returns a room’s whole picture in one call: its Deal Score, the eight MEDDPICC dimensions, the four insight cards, and the quote-backed findings behind all of them. There’s no separate call per view, so a question that spans several of them costs the same as a question about one.
The eight MEDDPICC dimensions are metrics, economic_buyer, decision_criteria, decision_process, paper_process, identify_pain, champion, and competition. The four insight card categories are:
A room without enough activity yet returns notScored rather than a 0. Those are different things — notScored means REX doesn’t have the evidence to judge, while 0 is a judgment. Don’t let a summary flatten one into the other.

​
Findings

Findings are the quote-backed moments REX has picked up from meetings — the raw material every score and card is built from. Each one carries a type, a description, the exact quote, and the meeting and contact it came from, which is what lets you answer questions no summary view covers.
The knowledge graph and signals answer different questions. The graph gives you the narrative and the evidence for a deal review; signals give you the worklist. Pull the graph when you want to understand a deal, signals when you want to act on it.

​
Room contacts

get_contacts returns everyone associated with a room (pass roomIds), enriched with view counts and company associations — not just people who’ve shown up. Omit roomIds to get every contact in the organization instead of one room.

​
Putting it together

REX tools compose well with the room tools. A few things worth asking for in one go:
REX’s scores and statuses are AI assessments graded from evidence, not facts. Hard data like a close date or a CRM field value is captured as-is, but severity, urgency, and sentiment are judgments. Anything you pull over MCP carries its justification and source for exactly that reason — check the evidence before acting on the number.

​
Full parameter reference

See the REX signals, Contacts, and REX knowledge graph sections of the tool reference.