ctx10/index
indexed The Context Layer as MCP. Resolve refs, find usages, compute blast radius, diff the instance over time.
Every entity, field, lookup, page, and business process in your Creatio instance, indexed into a snapshot. Browse it visually in the Explorer. Mount it as MCP in your coding agent and ask anything in plain English.
Read-only by default. Sandbox or production. Scopes are explicit per environment.
ctx10 runs an indexer over your Creatio instance and produces a snapshot: every entity, lookup, page, business process, business rule, role, and dashboard — and the edges between them. Re-run whenever you need a fresh snapshot.
The Explorer is the web app for humans. Walk the schema tree, click an entity to see every field, every BP that touches it, every dashboard that depends on it — without writing a query.
Plain-English Q&A lives in your coding agent. Mount ctx10/index in Claude, Cursor, or Continue and ask anything — find_usages, blast_radius, explain_bp, all grounded in the actual schema.
ctx10/live streams Creatio process execution and correlates each step against the index. Incidents become explanations, not log dives.
BP_OpportunityScoring. What depends on it?12 surfaces depend on it. The ones to watch:
I can draft the modified BP — say the word.
A snapshot graph of your Creatio instance. Browse it visually in the Explorer, or mount it as MCP in your coding agent and ask anything in plain English. Re-run on demand. The foundation every other agent stands on.
Where a field is read, written, filtered, or referenced. Across BPs, pages, dashboards.
Before you modify a business process, rule, or lookup, see every page, BP, and dashboard that depends on it.
Diff two snapshots — last sprint vs. this sprint, pre-migration vs. post — narrated in plain English.
Static analysis explains BP behavior — and proposes a tighter version as a diff.
Two hosted MCP servers — one indexed, one live. Mount them in Claude, Cursor, or anything that speaks MCP.
# resolve field usage across the entire instance › @ctx10/index find_usages(field="Opportunity.Amount", depth=2) read BP_OpportunityScoring line 142 read BP_RevenueForecast line 88 · sum() write UI_OpportunityForm NumberEdit filter Dashboard_PipelineByOwner 3 widgets read BP_DealStageGate guard ⚠ BP_RevenueForecast reads all 38 columns of Opportunity + Suggested fix: project (Id, Amount, OwnerId) → −11ms/row
The Context Layer as MCP. Resolve refs, find usages, compute blast radius, diff the instance over time.
Live process traces, correlated against the index. Explain incidents in seconds — not log dives.
Mount the MCP in Claude or Cursor. Your agent grounds every answer in your actual schema — no more invented field names.
3am incident? You want an explanation, not a log viewer. ctx10/live correlates traces against the index in seconds.
Compute blast radius before you modify a business process, rule, or lookup. Every page, BP, and dashboard that depends on it — listed up front.
Walk the snapshot in the Explorer to learn the shape of the instance. Ask the MCP what you cannot find. No wikis required.
ctx10/index in Claude Code, Cursor, Continue, or any MCP client and ask anything in plain English. Tools: find_usages, blast_radius, resolve_ref, diff_index, explain_bp.tail_bp, correlate, propose_fix, recent_errors, latency_anomalies. The result: incidents become explanations, not log dives.30-minute walkthrough on your own sandbox. We index it live. You ask the questions you've been wishing you could.