MCP · For agents

Your agents, on the team.

Agents work at full speed with none of the team's memory. Terum connects to them over MCP and closes that gap.

01 · the request

The map answers first

At the start of a task, the agent asks Terum what the team already knows: the standing decisions in scope, what shipped, what's in flight.

02 · the retrieval

Scored, not dumped

The same scoring that decides what reaches you decides what reaches the agent. It gets the three items that matter, not the whole wiki.

03 · the work

Informed from line one

No rebuilding what Priya shipped Tuesday. No re-arguing ADR-014. The agent starts where the team is, not where its context window begins.

claude · billing
add usage-based pricing to the billing page
· asking terum for team context…
⟿ terum · context for this task
decision ADR-014 "Postgres for billing storage" · @marcus · standing
shipped CSV export landed Tuesday · PR #482 · priya
in flight Billing rewrite in review · TER-204 · you
11 items held back below relevance
· planning with 3 items of team context…
· pricing tiers reuse the module priya consolidated in PR #482

what your agent gets

Context in, a gate on the way out, credit after.

01 · context

Before it builds

The decisions, changes, and open work relevant to the task, injected over MCP at the moment the agent needs them, with the owner and rationale attached, so it can reason about them, not just read them.

02 · the gate

Before it acts

If a planned step would reverse a standing decision, the run pauses and routes to the decision's owner for the call. Nothing destructive runs in the meantime.

See the gate, annotated ↓

03 · the net

After it ships

What your agents produce is caught like any teammate's work: typed onto the map, credited in the brief, visible to the people it affects. Agent work stops being invisible work.

from today's brief: 2 conversations · Cursor, Claude · high confidence

the gate, annotated

Before anything destructive runs.

The same conflict detection that guards your team's plans and docs meets the agent mid-run. When a planned step would reverse a standing decision, the run holds in the terminal with the decision, its owner, and its why in view.

claude · billing
migrate billing storage to mongo
· reading repo · planning the migration…
⟿ terum · decision check before execution
⚠ This action reverses a standing team decision.
Decision in scope
ADR-014: "Postgres for billing storage" · decided 3 days ago · owned by @marcus
Rationale: billing needs multi-row transactions, and finance's reporting runs on SQL views. Mongo was evaluated for this exact workload and rejected.
What your change touches
• 2 services read the Postgres billing schema: invoices, dunning
• 3 migrations and 1 finance reporting view depend on those tables
• the planned step drops those tables, not reversible without a restore
Why it's flagged, not silently blocked
impact · high: billing is revenue-critical; a bad migration risks dropped invoices
urgency · act now: the agent runs destructive migrations on the next step
proximity · your branch: your current task; no one else has touched it yet
Reversing ADR-014 needs @marcus's sign-off before anything destructive runs.
⏸ paused: the agent will not run migrations until this is resolved
01 · the decision

Named, owned, dated

Terum lifted ADR-014 off the map it built from your team's signal. Nobody wrote a wiki page: the decision, its owner, and when it was made were captured where it happened.

02 · the rationale

The "why," resurfaced

The reason lived in a thread nobody would have remembered. The gate replays it at the exact moment it matters, so the call is re-made with the context, not without it.

03 · the pause

Routed to the owner

The run stops before the destructive step and routes to the decision's owner. Their call, made once, unblocks it, or reverses the decision properly, on the record.

works with

Any agent that speaks MCP.

Connect over MCP from any client your team already runs.

Claude Code Cursor ChatGPT

Put your agents on the team.

Request a demo