Deployment Overview

Where ContextWorks is deployed — read live from the org, verified by traffic. Overview is the Deploy tab’s opening page: eight tiles, each a live probe, and the observed traffic that proves what the probes can’t see. There is nothing to register and nothing to maintain — every tile asks the org a question when the page loads.

The tiles

TileWhat it checksReady means
MCPNothing — the runtime tools ship in the core packageAlways ready after install
AgentforceThe extension package’s functions exist in the org’s GenAI function registryThe extension package is installed
Custom CodeUnpackaged Apex classes exposing @InvocableMethodSomeone has built custom tools on the Entity API
Custom EnrichmentsUnpackaged classes implementing the provider SPISomeone has plugged code into payloads
DomainsThe domain rosterOne or more configured; zero warns
End UsersActive users holding Context UserMore than zero; zero warns
Domain ManagersActive users holding Context Domain ManagerMore than zero; zero warns
StatusThe package license — Active, Trial, or Expired, with its expiration dateActive; Trial or an expiration inside 30 days warns

A Development status means the org has no package license row — a scratch or source-deployed org. In a subscriber org the tile always shows the real license.

Observed traffic

The bottom of the page is the empirical answer: loads by surface over the last 30 days, as a ranked chart and a table — surface, loads, tokens, errors, last activity.

This section exists because one thing is genuinely undetectable: MCP servers live outside the org. A claude.ai connector or a Claude Code registration leaves no record in Salesforce — so for MCP, what has actually called is the ground truth. The same logic catches custom code that’s written but wired to nothing: the Custom Code tile says it exists; the traffic table says whether it runs.

What’s next