The Context Layer for Your Agents
Agents see code but not business context. Tensient gives every agent a shared, queryable world model so decisions, constraints, and learnings compound instead of resetting each run.
Why This Matters
- Agents stop starting from zero on every task.
- Session outcomes become durable signals and synthesized knowledge.
- Orchestrators can build better prompts from real historical context.
Two Entry Points
Simple
Cursor or Claude Code session: call start_session, work, then call end_session.
Power
Orchestrator or agent swarm: query synthesis docs, open signals, and semantic search before spawning coding agents.
MCP Config
{
"mcpServers": {
"tensient": {
"url": "https://tensient.com/api/mcp",
"headers": {
"Authorization": "Bearer tns_YOUR_KEY_HERE"
}
}
}
}Cursor Rule Template
# Session Protocol (Tensient) At session start, call `start_session` via Tensient MCP. At session end, call `end_session` with: - summary - filesChanged - decisions - debtAdded - debtResolved - observations